MCP server
SupportBee MCP by usefulapi
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive…
- Runs
- Remotely
- Version
- 1.27.0
- Listing updated
- 4 days ago
About SupportBee MCP by usefulapi
SupportBee MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
Install
Run in a terminal
claude mcp add --transport http supportbee https://supportbee.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://supportbee.usefulapi.io/mcpInstall in CursorOpens Cursor, which asks you to confirm. Or add it by hand:
Add to ~/.cursor/mcp.json
{
"mcpServers": {
"supportbee": {
"url": "https://supportbee.usefulapi.io/mcp"
}
}
}Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:
Add to .vscode/mcp.json
{
"servers": {
"supportbee": {
"type": "http",
"url": "https://supportbee.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"supportbee": {
"serverUrl": "https://supportbee.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"supportbee": {
"type": "http",
"url": "https://supportbee.usefulapi.io/mcp"
}
}
}Tools this server provides (22)
Read directly from the server.
- supportbee_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
- supportbee_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
- 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
- The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.
- supportbee_get_reply
- One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.
- supportbee_list_comments
- 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
- What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.
- supportbee_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
- 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
- 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
- One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.
- supportbee_list_snippets
- The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.
- supportbee_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
- 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: 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: 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: 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: 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: 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: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.
- supportbee_set_ticket_archived
- 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: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.
SupportBee MCP by usefulapi FAQ
How do I add SupportBee MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http supportbee https://supportbee.usefulapi.io/mcp