Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"supportbee": {
"url": "https://supportbee.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"supportbee": {
"type": "http",
"url": "https://supportbee.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your SupportBee company and SupportBee API token.
The company is the first part of your desk address (acme for acme.supportbee.com). Find the API token in SupportBee under your profile menu → API Token; it acts with that user's permissions, so a dedicated agent makes its activity easy to track. A reply you send through this server is e-mailed to the customer. Your token is used only to call the SupportBee API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your SupportBee company and SupportBee API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
supportbee_list_tickets | read | List tickets 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, archived and the first message text (cut). With total_only=true only the number of matching tickets comes back. GET /tickets. |
supportbee_search_tickets | read | Search tickets 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_get_ticket | read | Get a ticket One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}. |
supportbee_list_replies | read | List the replies of a ticket The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies. |
supportbee_get_reply | read | Get one reply of a ticket One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}. |
supportbee_list_comments | read | List the internal comments of a ticket The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments. |
supportbee_get_ticket_audit | read | Get the audit trail of a ticket What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit. |
supportbee_list_labels | read | List labels 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_teams | read | List teams 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_users | read | List users 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_get_user | read | Get a user One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}. |
supportbee_list_snippets | read | List snippets The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets. |
supportbee_list_forwarding_addresses | read | List forwarding addresses The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails. |
supportbee_get_report | read | Get a report 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_reply_to_ticket | write | Reply to a ticket (sends an e-mail) 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 supportbee_add_comment. POST /tickets/{id}/replies. |
supportbee_add_comment | write | Add an internal comment to a ticket 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 | write | Add a label to a ticket 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_remove_label | write | Remove a label from a ticket 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_assign_ticket | write | Assign a ticket to a user or a team 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_assignment or /team_assignment. |
supportbee_unassign_ticket | write | Remove the user or team assignment of a ticket WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment. |
supportbee_set_ticket_archived | write | Archive or un-archive a ticket 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_set_ticket_answered | write | Mark a ticket answered or unanswered WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered. |
supportbee_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
supportbee_request_feature | Request a missing feature Tell usefulapi that the user needs something the SupportBee tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
supportbee_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED SupportBee tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
supportbee_cancel_subscription | Cancel the Pro subscription Cancel the caller's SupportBee Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run supportbee_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper company | $9/mo · $90/yr | Unlimited |
Pro covers this SupportBee server only. Subscribe with supportbee_upgrade (it returns a Stripe Checkout link). Cancel any time with supportbee_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running supportbee_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by SupportBee. The server calls the SupportBee API with your own SupportBee access, so it sees only the data that your account can see.
The login page asks for your SupportBee company and SupportBee API token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your SupportBee company and SupportBee API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the SupportBee API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in SupportBee.
Yes, if you approve it. 8 of the 22 SupportBee tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this SupportBee server only. Run supportbee_usage_status to see how many calls you used.
Ask the AI to run supportbee_upgrade: it returns a Stripe Checkout link. To cancel, run supportbee_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with supportbee_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.