io.usefulapi/supportbee

up checked 2026-11-11T10:37:48.849Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

SupportBee MCP by usefulapi

Publisher-provided description

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

Summary by lookupd

Read, search and triage SupportBee helpdesk tickets, replies, comments and reports; can send replies, label, assign and archive.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add supportbee --url https://supportbee.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (22 tools)

Publisher-provided text

• 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
• 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 /
• 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
• 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
• 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/{
• 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
• 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}/arch
• supportbee_set_ticket_answered WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.

Details

• Version: 1.24.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 517 ms
• First indexed: 2026-11-01T10:06:26.429Z
• Last seen in registry: 2026-11-11T00:17:35.104Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/supportbee/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/supportbee.svg)](https://lookupd.com/servers/io.usefulapi/supportbee)

• 62071 servers
• Last crawl: 2026-11-11T16:39:06.253Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp