Helpwise MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.

Deletes · 9

Compare Registry entry

21 tools: 9 can delete or cancel things and 12 only read.

Scanned Oct 21, 2026

Deletes or cancels9Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads12Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http helpwise https://helpwise.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

21 tools

Deletes or cancels 9Removes, cancels or revokes something.Claude Code: deny

helpwise_add_noteWRITE: add an internal note to a conversation.No findings
Why it is in this group
- The name "helpwise_add_note" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: add an internal note to a conversation. Visible to your Helpwise team only; it is not sent to the customer. Notes cannot be deleted through this API. POST /notes/add (V0).
Annotations the server declares
- title: Add note
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
helpwise_apply_tagsWRITE: apply existing tags (ids from helpwise_list_tags) to up to 25 conversations.No findings
Why it is in this group
- The name "helpwise_apply_tags" says "apply": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: apply existing tags (ids from helpwise_list_tags) to up to 25 conversations. Tags can drive Helpwise automations. Applying a tag already present changes nothing. POST /tags/apply.
Annotations the server declares
- title: Apply tags
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
helpwise_assign_conversationWRITE: assign a conversation to a team member (user id from helpwise_list_users), or pass assigned_to 0 to unassign it.No findings
Why it is in this group
- The name "helpwise_assign_conversation" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: assign a conversation to a team member (user id from helpwise_list_users), or pass assigned_to 0 to unassign it. The assignee may be notified by Helpwise. POST /threads/assign (V0).
Annotations the server declares
- title: Assign conversation
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
helpwise_close_conversationsWRITE: close up to 25 conversations (mark them done).No findings
Why it is in this group
- The name "helpwise_close_conversations" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: close up to 25 conversations (mark them done). They can be reopened with helpwise_reopen_conversations. Nothing is sent to customers. PUT /conversations/action/close.
Annotations the server declares
- title: Close conversations
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
helpwise_create_contactWRITE: create a new contact in Helpwise (name, company, job title, emails, phones, custom fields).No findings
Why it is in this group
- The name "helpwise_create_contact" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: create a new contact in Helpwise (name, company, job title, emails, phones, custom fields). Nothing is sent to the person. Creating the same email twice may create a duplicate. POST /contacts.
Annotations the server declares
- title: Create contact
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
helpwise_remove_tagsWRITE: take tags off up to 25 conversations.No findings
Why it is in this group
- The name "helpwise_remove_tags" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.
Annotations the server declares
- title: Remove tags from conversations
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
helpwise_reopen_conversationsWRITE: move up to 25 conversations back to the inbox (reopen closed ones).No findings
Why it is in this group
- The name "helpwise_reopen_conversations" says "reopen": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.
Annotations the server declares
- title: Reopen conversations
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
helpwise_send_emailWRITE: SEND A REAL EMAIL from a Helpwise inbox to the given customer address(es).No findings
Why it is in this group
- The name "helpwise_send_email" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "Irreversible".
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: SEND A REAL EMAIL from a Helpwise inbox to the given customer address(es). Irreversible; once sent it cannot be recalled. At most 10 recipients in total (to + cc), one message per call; never use it for lists or campaigns. This starts a new message (it is not a reply on an existing conversation). The body is plain text (blank line = new paragraph); it is sent as HTML. POST /emails/send_mail (V0).
Annotations the server declares
- title: Send email
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
helpwise_update_contactWRITE: change a contact's name, company, job title, emails, phones or custom fields.No findings
Why it is in this group
- The name "helpwise_update_contact" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: change a contact's name, company, job title, emails, phones or custom fields. Helpwise updates with PUT, so this tool first reads the contact and sends the current values together with your changes; a list you pass (emails, phones, custom_fields) REPLACES the old list. Nothing is sent to the person. PUT /contacts/{id}.
Annotations the server declares
- title: Update contact
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true

Only reads 12Looks things up and changes nothing.Claude Code: allow

helpwise_get_contactOne contact with emails, phones, company, custom fields and recent conversations.No findings
Why it is in this group
- The name "helpwise_get_contact" says "get": a word for reading.
Description, as the server wrote it
One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.
Annotations the server declares
- title: Get contact
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_get_conversationOne conversation with its messages, notes, drafts, assignment and contacts.No findings
Why it is in this group
- The name "helpwise_get_conversation" says "get": a word for reading.
Description, as the server wrote it
One conversation with its messages, notes, drafts, assignment and contacts. Page long conversations with `page_token` from the previous reply. GET /inboxes/{inbox_id}/conversations/{conversation_id}.
Annotations the server declares
- title: Get conversation
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_get_current_userThe Helpwise user the API key belongs to (name, email, id).No findings
Why it is in this group
- The name "helpwise_get_current_user" says "get": a word for reading.
Description, as the server wrote it
The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).
Annotations the server declares
- title: Get current user
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_get_reportOverall and team-performance report for a date range: new/closed/assigned conversations (with change vs the previous period), inbound/outbound messages per day, busiest hour/day, a…No findings
Why it is in this group
- The name "helpwise_get_report" says "get": a word for reading.
Description, as the server wrote it
Overall and team-performance report for a date range: new/closed/assigned conversations (with change vs the previous period), inbound/outbound messages per day, busiest hour/day, average first response, response and resolution time, CSAT and per-agent performance. Optional inbox and tag filters. GET /reports.
Annotations the server declares
- title: Overall report
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_get_tagOne tag by id.No findings
Why it is in this group
- The name "helpwise_get_tag" says "get": a word for reading.
Description, as the server wrote it
One tag by id. GET /tags/{id}.
Annotations the server declares
- title: Get tag
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_get_tags_reportPer-tag report for one inbox and a date range: conversations per tag (and share), open conversations, average response, first-response and resolution time.No findings
Why it is in this group
- The name "helpwise_get_tags_report" says "get": a word for reading.
Description, as the server wrote it
Per-tag report for one inbox and a date range: conversations per tag (and share), open conversations, average response, first-response and resolution time. GET /inboxes/{inbox_id}/reports/tags.
Annotations the server declares
- title: Tags report
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_list_contactsList contacts (name, company, job title, emails, phones, id).No findings
Why it is in this group
- The name "helpwise_list_contacts" says "list": a word for reading.
Description, as the server wrote it
List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.
Annotations the server declares
- title: List contacts
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_list_conversationsList conversations (threads) of one or more inboxes, newest first, with subject, snippet, tags, assignee, read/starred/closed flags and contact.No findings
Why it is in this group
- The name "helpwise_list_conversations" says "list": a word for reading.
Description, as the server wrote it
List conversations (threads) of one or more inboxes, newest first, with subject, snippet, tags, assignee, read/starred/closed flags and contact. Pick the folder with `folder` (default: all). Page with `next_page_token`. Inbox ids come from helpwise_list_inboxes. GET /conversations.
Annotations the server declares
- title: List conversations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_list_inboxesList the account's inboxes (mailboxes) with id, name, address and type.No findings
Why it is in this group
- The name "helpwise_list_inboxes" says "list": a word for reading.
Description, as the server wrote it
List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).
Annotations the server declares
- title: List inboxes
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_list_tagsAll tags (id, name, colour, parent, inbox).No findings
Why it is in this group
- The name "helpwise_list_tags" says "list": a word for reading.
Description, as the server wrote it
All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.
Annotations the server declares
- title: List tags
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_list_usersList the team members (agents) with access to an inbox: id, name, email.No findings
Why it is in this group
- The name "helpwise_list_users" says "list": a word for reading.
Description, as the server wrote it
List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).
Annotations the server declares
- title: List users
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
helpwise_search_contactsSearch contacts by a name, email or phone term.No findings
Why it is in this group
- The name "helpwise_search_contacts" says "search": a word for reading.
Description, as the server wrote it
Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.
Annotations the server declares
- title: Search contacts
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http helpwise https://helpwise.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__helpwise__helpwise_list_conversations",
      "mcp__helpwise__helpwise_get_conversation",
      "mcp__helpwise__helpwise_list_contacts",
      "mcp__helpwise__helpwise_search_contacts",
      "mcp__helpwise__helpwise_get_contact",
      "mcp__helpwise__helpwise_list_tags",
      "mcp__helpwise__helpwise_get_tag",
      "mcp__helpwise__helpwise_get_report",
      "mcp__helpwise__helpwise_get_tags_report",
      "mcp__helpwise__helpwise_list_inboxes",
      "mcp__helpwise__helpwise_list_users",
      "mcp__helpwise__helpwise_get_current_user"
    ],
    "ask": [],
    "deny": [
      "mcp__helpwise__helpwise_create_contact",
      "mcp__helpwise__helpwise_update_contact",
      "mcp__helpwise__helpwise_add_note",
      "mcp__helpwise__helpwise_assign_conversation",
      "mcp__helpwise__helpwise_close_conversations",
      "mcp__helpwise__helpwise_reopen_conversations",
      "mcp__helpwise__helpwise_apply_tags",
      "mcp__helpwise__helpwise_remove_tags",
      "mcp__helpwise__helpwise_send_email"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as helpwise. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/helpwise/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing