Helpwise MCP by usefulapi
Server Details
Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
21 toolshelpwise_add_noteAdd noteDestructiveInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The note text. | |
| inbox_id | Yes | Inbox (mailbox) id of the conversation. | |
| conversation_id | Yes | Conversation (thread) id. |
helpwise_apply_tagsApply tagsDestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_ids | Yes | Tag ids to apply (1-10). | |
| conversation_ids | Yes | Conversation (thread) ids (1-25). |
helpwise_assign_conversationAssign conversationDestructiveIdempotentInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | Inbox (mailbox) id of the conversation. | |
| assigned_to | Yes | User id to assign to, or 0 to unassign. | |
| conversation_id | Yes | Conversation (thread) id. |
helpwise_close_conversationsClose conversationsDestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| conversation_ids | Yes | Conversation (thread) ids to close (1-25). |
helpwise_create_contactCreate contactDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| emails | No | Email addresses (1-10). | |
| phones | No | Phone numbers (up to 10). | |
| company | No | Company name. | |
| lastname | No | Last name. | |
| firstname | Yes | First name. | |
| job_title | No | Job title. | |
| custom_fields | No | Custom field values. |
helpwise_get_contactGet contactRead-onlyInspect
One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| contact_id | Yes | Helpwise contact id. |
helpwise_get_conversationGet conversationRead-onlyInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Results per page, 1-100 (default 25). | |
| folder | No | Folder context (optional). | |
| inbox_id | Yes | Inbox (mailbox) id the conversation lives in. | |
| page_token | No | Page token from the previous reply, for older messages. | |
| conversation_id | Yes | Conversation (thread) id. |
helpwise_get_current_userGet current userRead-onlyInspect
The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
helpwise_get_reportOverall reportRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). | |
| start | Yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). | |
| tag_ids | No | Only conversations with these tag ids. | |
| inbox_id | No | Only this inbox (default: all inboxes). | |
| business_hours_only | No | Count business hours only (default false). |
helpwise_get_tagGet tagRead-onlyInspect
One tag by id. GET /tags/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_id | Yes | Helpwise tag id. |
helpwise_get_tags_reportTags reportRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | End, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 23:59:59). | |
| start | Yes | Start, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss (a date alone means 00:00:00). | |
| tag_ids | No | Only these tag ids. | |
| inbox_id | Yes | Inbox (mailbox) id. | |
| business_hours_only | No | Count business hours only (default false). |
helpwise_list_contactsList contactsRead-onlyInspect
List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Results per page, 1-100 (default 25). | |
| offset | No | How many results to skip (default 0). Pass the previous reply's next_offset. |
helpwise_list_conversationsList conversationsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Results per page, 1-100 (default 25). | |
| folder | No | Folder: all, assigned, unassigned, starred, snoozed, draft, sent, closed, spam, trash, scheduled. | |
| inbox_ids | Yes | Inbox (mailbox) ids to list (1-20). | |
| page_token | No | The previous reply's next_page_token. |
helpwise_list_inboxesList inboxesRead-onlyInspect
List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, from 1 (default 1). | |
| limit | No | Results per page, 1-100 (default 25). |
helpwise_list_tagsList tagsRead-onlyInspect
All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
helpwise_list_usersList usersRead-onlyInspect
List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | Inbox (mailbox) id. |
helpwise_remove_tagsRemove tags from conversationsDestructiveIdempotentInspect
WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_ids | Yes | Tag ids to remove from them (1-10). | |
| conversation_ids | Yes | Conversation (thread) ids (1-25). |
helpwise_reopen_conversationsReopen conversationsDestructiveIdempotentInspect
WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.
| Name | Required | Description | Default |
|---|---|---|---|
| conversation_ids | Yes | Conversation (thread) ids to reopen (1-25). |
helpwise_search_contactsSearch contactsRead-onlyInspect
Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Search term (name, email or phone). | |
| limit | No | Results per page, 1-100 (default 25). | |
| offset | No | How many results to skip (default 0). Pass the previous reply's next_offset. |
helpwise_send_emailSend emailDestructiveInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Cc addresses. | |
| to | Yes | Recipient addresses (1-10 with cc together). | |
| body | Yes | Plain-text message body. | |
| subject | Yes | Subject line. | |
| inbox_id | Yes | Inbox (mailbox) id to send from (see helpwise_list_inboxes). | |
| reply_to | No | Reply-to address (optional). |
helpwise_update_contactUpdate contactDestructiveIdempotentInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| emails | No | The full list of email addresses (replaces the current list). | |
| phones | No | The full list of phone numbers (replaces the current list). | |
| company | No | New company. | |
| lastname | No | New last name. | |
| firstname | No | New first name. | |
| job_title | No | New job title. | |
| contact_id | Yes | Helpwise contact id. | |
| custom_fields | No | Custom field values to set (replaces the current list). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
21 tool updates
- First observed
helpwise_add_note - First observed
helpwise_apply_tags - First observed
helpwise_assign_conversation - First observed
helpwise_close_conversations - First observed
helpwise_create_contact - First observed
helpwise_get_contact - First observed
helpwise_get_conversation - First observed
helpwise_get_current_user - First observed
helpwise_get_report - First observed
helpwise_get_tag - First observed
helpwise_get_tags_report - First observed
helpwise_list_contacts - First observed
helpwise_list_conversations - First observed
helpwise_list_inboxes - First observed
helpwise_list_tags - First observed
helpwise_list_users - First observed
helpwise_remove_tags - First observed
helpwise_reopen_conversations - First observed
helpwise_search_contacts - First observed
helpwise_send_email - First observed
helpwise_update_contact
Related MCP Connectors
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
1Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.
Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.
231
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables reading customer-support conversations, inboxes, and service performance from the Help Scout Inbox API.20 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables to search, view, and interact with Intercom contacts and conversations, including sending customer-visible replies and internal notes.MIT
- AlicenseBqualityCmaintenanceMCP server for Gmail shared inboxes and WhatsApp — read, reply, search, and organize your team's email from Claude, ChatGPT, or Cursor. 47 tools covering email threads, WhatsApp messaging, boards, contacts, knowledge base, analytics, and automations.4763 npm1MIT
- AlicenseAqualityBmaintenanceManages email accounts via IMAP/SMTP, enabling reading, searching, sending, replying, forwarding, and folder management with multi-user and OAuth support.22MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.