MCP server

SupportBee MCP by usefulapi

io.usefulapi/supportbee

Checked 25 Oct 2026, 20:29 UTC · Connected to it and listed its tools

Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.

Website Source

At a glance

Type

MCP server

Publisher

usefulapi.io (verified by the MCP Registry)

Status

Working at last check

Tools

22

Token cost

About 4,659 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

25 Oct 2026, 20:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.supportbee]
url = "https://supportbee.usefulapi.io/mcp"

Gemini CLI

{"mcpServers":{"supportbee":{"httpUrl":"https://supportbee.usefulapi.io/mcp"}}}

Cursor

{"mcpServers":{"supportbee":{"url":"https://supportbee.usefulapi.io/mcp"}}}

VS Code

{"servers":{"supportbee":{"type":"http","url":"https://supportbee.usefulapi.io/mcp"}}}

Antigravity

agy mcp add supportbee https://supportbee.usefulapi.io/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"supportbee","server_url":"https://supportbee.usefulapi.io/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"supportbee","server_url":"https://supportbee.usefulapi.io/mcp"}

Tools

• supportbee_add_comment ~189 tokens
  WRITE: adds an internal comment to a ticket. Comments are visible to your agents only and are never e-mailed to the customer. POST /tickets/{id}/comments.
• supportbee_add_label ~189 tokens
  WRITE: adds an existing label to a ticket (404 if the label does not exist; names come from supportbee_list_labels). Safe to repeat. POST /tickets/{id}/labels/{label}.
• supportbee_assign_ticket ~274 tokens
  WRITE: assigns a ticket to ONE agent (user_id) or ONE team (team_id), not both. A ticket that belongs to a team can only go to a member of that team; assigning to another team removes the user assignee. The customer is not e-mailed (SupportBee may notify the assigned agent). POST /tickets/{id}/user_
• supportbee_get_reply ~170 tokens
  One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.
• supportbee_get_report ~298 tokens
  A report as time-series data points (value, timestamp): tickets_count, replies_count or avg_first_response_time, optionally for one agent, team or label. Needs an admin token. GET /reports/{report}.
• supportbee_get_ticket ~146 tokens
  One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.
• supportbee_get_ticket_audit ~143 tokens
  What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.
• supportbee_get_user ~156 tokens
  One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.
• supportbee_list_comments ~140 tokens
  The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.
• supportbee_list_forwarding_addresses ~89 tokens
  The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.
• supportbee_list_labels ~81 tokens
  All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.
• supportbee_list_replies ~138 tokens
  The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.
• supportbee_list_snippets ~75 tokens
  The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.
• supportbee_list_teams ~150 tokens
  The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.
• supportbee_list_tickets ~850 tokens
  List tickets of the shared inbox, newest activity first, with filters (assignee, team, label, requester, dates, spam/trash/archived). By default archived, spam and trashed tickets are left out. Each ticket has id, subject, labels, requester, assignee, replies_count, comments_count, unanswered, archi
• supportbee_list_users ~212 tokens
  The agents, admins and collaborators of the desk (id, name, e-mail, role, teams), or customer groups. Use the id as assigned_user or user_id. GET /users.
• supportbee_remove_label ~170 tokens
  WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.
• supportbee_reply_to_ticket Sends messages · ~408 tokens
  WRITE: SENDS AN E-MAIL to the customer. Posts a public reply on ONE ticket; SupportBee e-mails it to the ticket's requester and to the cc/bcc addresses you list (at most 10 addresses in total). It cannot be recalled. The reply comes from the token's user. For a note only your team sees, use supportb
• supportbee_search_tickets ~252 tokens
  Full-text search over tickets (subject, body, requester) with SupportBee's search syntax, newest activity first. Spam and trash are excluded unless asked. GET /tickets/search.
• supportbee_set_ticket_answered ~176 tokens
  WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.
• supportbee_set_ticket_archived ~183 tokens
  WRITE: archives a ticket (archived=true, it leaves the open inbox) or moves it back (archived=false). Nothing is deleted or sent. POST/DELETE /tickets/{id}/archive.
• supportbee_unassign_ticket ~170 tokens
  WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.

Browse

• Email

Related MCP servers

• Zendesk MCP by usefulapi
  Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
• Trengo MCP by usefulapi
  Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
• Atera MCP by usefulapi
  Check devices, alerts and tickets in Atera, and open tickets, comment or resolve alerts.
• Enchant MCP by usefulapi
  Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
• Deskpro MCP by usefulapi
  Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
• Freshdesk MCP by usefulapi
  Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
• ProductClank
  Boost posts and launch community growth campaigns from your AI assistant. OAuth, credit-billed.
• OfficeRnD MCP by usefulapi
  Browse OfficeRnD members, bookings, memberships, invoices and tickets, with optional write access.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.usefulapi/supportbee.svg)](https://aptlynx.net/servers/io.usefulapi/supportbee)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents