# Helpwise Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Helpwise

Read and manage customer support conversations, contacts, tags, and team performance reports in Helpwise.

- Record: https://musedirectory.ai/connector/helpwise
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/helpwise/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 27ms, checked 2026-10-29T10:45:49Z
- Endpoint: https://helpwise.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T08:01:37Z)
- Source: Found in the official MCP Registry (io.usefulapi/helpwise) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fhelpwise

Connect to Helpwise, a customer support platform. Read conversations, contacts, tags and performance reports. Add notes, assign conversations, close tickets, apply tags, and send emails from your support inbox.

Example request: "Show me all open support conversations assigned to me and let me add a note to the urgent one."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Helpwise to help me. It is a free service with an MCP server at https://helpwise.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- helpwise_list_conversations: 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 /conversation
- helpwise_get_conversation: 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}.
- helpwise_list_contacts: List contacts (name, company, job title, emails, phones, id). Page with limit and offset. GET /contacts.
- helpwise_search_contacts: Search contacts by a name, email or phone term. Page with limit and offset. GET /contacts/search.
- helpwise_get_contact: One contact with emails, phones, company, custom fields and recent conversations. GET /contacts/{id}.
- helpwise_list_tags: All tags (id, name, colour, parent, inbox). Use the ids with helpwise_apply_tags. GET /tags.
- helpwise_get_tag: One tag by id. GET /tags/{id}.
- helpwise_get_report: 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 
- helpwise_get_tags_report: 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.
- helpwise_list_inboxes: List the account's inboxes (mailboxes) with id, name, address and type. Use the ids in the other tools. POST /mailboxes/list (V0).
- helpwise_list_users: List the team members (agents) with access to an inbox: id, name, email. Use the ids with helpwise_assign_conversation. POST /users/list (V0).
- helpwise_get_current_user: The Helpwise user the API key belongs to (name, email, id). POST /users/me (V0).
- helpwise_create_contact: 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.
- helpwise_update_contact: 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. Not
- helpwise_add_note: 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).
- helpwise_assign_conversation: 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).
- helpwise_close_conversations: 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.
- helpwise_reopen_conversations: WRITE: move up to 25 conversations back to the inbox (reopen closed ones). Nothing is sent to customers. PUT /conversations/action/moveToInbox.
- helpwise_apply_tags: 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.
- helpwise_remove_tags: WRITE: take tags off up to 25 conversations. The tags themselves are not deleted. POST /tags/remove.
- helpwise_send_email: 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

Screening checks:
- MCP handshake: pass (Answered in 7ms)
- Domain against threat feeds (Cloudflare security DNS): pass (helpwise.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (21 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)
