# Supportbee — how to use (mcp.ai)

Connect your Supportbee account and use 41 tools for customer support straight from your AI agent. Connect with your own API key. SupportBee is a web-based email support tool that helps businesses organize their customer support emails efficiently.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_supportbee?ms=1787291460000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `supportbee_add_label_to_ticket`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/supportbee`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/supportbee/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/supportbee/add/label/to/ticket` — Tool to add a label to a ticket. Use when you need to categorize or tag a ticket with a specific label. The label must already exist in your SupportBee account before adding it to a ticket.
  - body: { ticket_id: integer, label_name: string }
- `POST https://api.mcp.ai/api/supportbee/archive/ticket` — Tool to archive a SupportBee ticket by its ID. Use when you want to move resolved tickets to the archive.
  - body: { id: string }
- `POST https://api.mcp.ai/api/supportbee/assign/ticket/to/team` — Assigns a ticket to a team in SupportBee. Use when you need to route a support ticket to a specific team for handling. Note: If the ticket is already assigned to a team and a user, reassigning to anot
  - body: { team_id: integer, ticket_id: integer }
- `POST https://api.mcp.ai/api/supportbee/create/comment` — Creates an internal comment on a ticket in SupportBee. Comments are private notes visible only to agents, not to customers. Use this to add internal notes, observations, or collaborate with team membe
  - body: { content: object, ticket_id: string }
- `POST https://api.mcp.ai/api/supportbee/create/consequence` — Creates a new consequence for rules automation in SupportBee. Use when setting up automated actions that should be triggered by rules (e.g., auto-assign tickets, archive, or mark as spam).
  - body: { spam?: boolean, label?: string, archive?: boolean, assign_team?: string, assign_user?: string }
- `POST https://api.mcp.ai/api/supportbee/create/email` — Create a new forwarding email address for the company in SupportBee. Use this to add new support email addresses that will forward incoming emails to your SupportBee account as tickets.
  - body: { name?: string, email: string, filter_spam?: boolean, use_agent_name?: boolean }
- `POST https://api.mcp.ai/api/supportbee/create/filter` — Creates a filter in SupportBee by linking a rule with a consequence. Use this after creating both a rule (defining match conditions) and a consequence (defining actions to perform).
  - body: { rule_id: string, consequence_id: string }
- `POST https://api.mcp.ai/api/supportbee/create/rule` — Creates a new automation rule in SupportBee to automatically process tickets based on conditions. Rules allow you to automate ticket workflows by: - Matching tickets based on field conditions (subject
  - body: { name: string, active?: boolean, actions: object[], conditions: object[], sort_order?: integer, description?: string }
- `POST https://api.mcp.ai/api/supportbee/create/snippet` — Create a reusable snippet (canned response) in SupportBee. Snippets are pre-written text templates that agents can quickly insert into ticket replies. Use this to create standard responses for common 
  - body: { html?: string, name: string, tags?: string, text: string }
- `POST https://api.mcp.ai/api/supportbee/create/ticket` — Creates a new support ticket in SupportBee with a subject, content, and requester details. Use this action to: - Create tickets from customer inquiries or issues - Assign tickets to specific agents or
  - body: { cc?: string[], spam?: boolean, tags?: string[], labels?: string[], content: string, subject: string, team_id?: integer, agent_id?: integer, requester: object }
- `POST https://api.mcp.ai/api/supportbee/create/ticket/reply` — Create a reply to a support ticket in SupportBee. Replies are sent to customers via email and are visible to them. Use this when you need to respond to a customer's ticket with information, updates, o
  - body: { content: string, user_id?: integer, ticket_id: string }
- `POST https://api.mcp.ai/api/supportbee/create/user/or/customer/group` — Invites a new user to your SupportBee account. The user will receive an email invitation and can be assigned as an agent (handles tickets), admin (full access), or collaborator (view/comment only). Us
  - body: { name?: string, role?: string, email: string }
- `POST https://api.mcp.ai/api/supportbee/delete/snippet` — Permanently delete a snippet by its ID from SupportBee. Use this action when you need to remove an unwanted or outdated snippet (canned response template). This action is destructive and cannot be und
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/delete/ticket` — Permanently delete a trashed ticket from SupportBee. The ticket must first be moved to trash using the Trash Ticket action before it can be permanently deleted. Only admins can delete trashed tickets.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/fetch/emails` — Retrieve all forwarding email addresses configured for the company. Use this tool to list the support email addresses that forward emails to SupportBee.
- `POST https://api.mcp.ai/api/supportbee/fetch/labels` — Tool to retrieve all custom labels. Use when you need to list labels for ticket categorization.
- `POST https://api.mcp.ai/api/supportbee/fetch/snippets` — Fetches saved response snippets (canned responses/templates) from SupportBee. Snippets are reusable text templates that can be inserted into ticket replies. Use this to list available snippets for qui
  - body: { page?: integer, per_page?: integer }
- `POST https://api.mcp.ai/api/supportbee/fetch/teams` — Retrieves all teams in the SupportBee account. Use this to list available teams before assigning tickets to teams or filtering tickets by team. Returns team IDs, names, descriptions, and timestamps.
- `POST https://api.mcp.ai/api/supportbee/get/avg/first/response/time/report` — Tool to retrieve average first response time data points over time. Use when analyzing first-response performance metrics for support tickets. Returns time-series data with response times in seconds a
  - body: { team?: integer, user?: integer, label?: string, since?: string, until?: string }
- `POST https://api.mcp.ai/api/supportbee/get/replies/count/report` — Retrieves replies count report data for the company. Returns time-series data points showing the number of replies over time. The report provides aggregate metrics for the entire company account and i
- `POST https://api.mcp.ai/api/supportbee/get/ticket` — Tool to retrieve a specific SupportBee ticket by its ID. Returns complete ticket details including subject, content, requester, assignee, labels, and reply/comment counts. Use when you need to fetch f
  - body: { id: string }
- `POST https://api.mcp.ai/api/supportbee/get/tickets/count/report` — Tool to get ticket count data points over time. Use when analyzing ticket volume trends within a specific date range. Supports optional filtering by agent, team, or label.
  - body: { label?: string, team_id?: integer, to_date: string, agent_id?: integer, from_date: string }
- `POST https://api.mcp.ai/api/supportbee/list/ticket/comments` — Retrieves all internal comments (private agent notes) for a specific ticket. Comments are visible only to agents within the helpdesk, not to customers. Use this to review internal discussion history o
  - body: { ticket_id: string }
- `POST https://api.mcp.ai/api/supportbee/list/ticket/replies` — Lists all replies on a specific support ticket in SupportBee. Returns reply content, replier details, timestamps, and attachments. Use this to view the conversation history on a ticket. Returns an emp
  - body: { page?: integer, per_page?: integer, ticket_id: string }
- `POST https://api.mcp.ai/api/supportbee/list/tickets` — Tool to list tickets from SupportBee. Returns a paginated list of tickets with optional filters for spam, trash, archived, assigned user/group, labels, and more. Use when you need to retrieve and brow
  - body: { page?: integer, spam?: boolean, label?: string, trash?: boolean, replies?: boolean, starred?: boolean, archived?: boolean, per_page?: integer, since_id?: integer, assigned_user?: string, assigned_group?: string }
- `POST https://api.mcp.ai/api/supportbee/list/users` — Retrieves all users and customer groups in your SupportBee company. Use this when you need to list team members, filter by user type (agents/admins vs customer groups), or include invited users who ha
  - body: { type?: string, with_roles?: boolean, with_invited?: boolean }
- `POST https://api.mcp.ai/api/supportbee/mark/ticket/as/answered` — Marks a SupportBee ticket as answered by adding the 'answered' status. Use this after sending a response to a customer to indicate the ticket has been addressed. This action is idempotent - calling it
  - body: { id: integer|string }
- `POST https://api.mcp.ai/api/supportbee/mark/ticket/as/spam` — Tool to mark a SupportBee ticket as spam. Use when you need to flag unwanted or malicious ticket submissions after obtaining the ticket ID.
  - body: { id: string }
- `POST https://api.mcp.ai/api/supportbee/mark/ticket/as/unanswered` — Marks a SupportBee ticket as unanswered by removing its 'answered' status. Use this to revert a ticket's status after it was previously marked as answered, typically when additional follow-up is neede
  - body: { id: integer|string }
- `POST https://api.mcp.ai/api/supportbee/remove/label/from/ticket` — Tool to remove a label from a ticket. Use when you need to unlabel or uncategorize a ticket by removing an existing label.
  - body: { ticket_id: integer, label_name: string }
- `POST https://api.mcp.ai/api/supportbee/search/tickets` — Tool to search SupportBee tickets. Use when you need to find tickets by query with pagination.
  - body: { page?: integer, spam?: boolean, query?: string, trash?: boolean, replies?: boolean, archived?: string, per_page?: integer }
- `POST https://api.mcp.ai/api/supportbee/show/ticket/reply` — Tool to fetch a specific reply for a SupportBee ticket. Use when you need details of a single reply by ticket and reply IDs.
  - body: { reply_id: integer, ticket_id: string }
- `POST https://api.mcp.ai/api/supportbee/show/user/or/customer/group` — Retrieves details of a SupportBee user (agent/admin) or customer group by their ID. Use this action when you need to fetch profile information like name, email, role, or timestamps for a specific user
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/trash/ticket` — Tool to trash a SupportBee ticket by its ID. Use when you need to remove a ticket into the trash folder.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/unarchive/ticket` — Tool to unarchive a SupportBee ticket by its ID. Use when you need to restore an archived ticket back to active status.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/unassign/ticket/from/team` — Tool to un-assign a ticket from its assigned team. Use when you need to remove the current team ownership before reassigning or closing the ticket.
  - body: { ticket_id: integer }
- `POST https://api.mcp.ai/api/supportbee/unassign/ticket/from/user` — Tool to un-assign a ticket from its assigned user/agent. Use when you need to remove the current user ownership before reassigning to a different user or closing the ticket.
  - body: { ticket_id: integer }
- `POST https://api.mcp.ai/api/supportbee/unmark/ticket/as/spam` — Tool to unmark a SupportBee ticket as spam. Use when a ticket was incorrectly flagged as spam.
  - body: { id: string }
- `POST https://api.mcp.ai/api/supportbee/untrash/ticket` — Restores a trashed SupportBee ticket back to active status. Use when you need to recover a ticket that was previously moved to trash.
  - body: { id: integer }
- `POST https://api.mcp.ai/api/supportbee/update/snippet` — Update an existing snippet (canned response) in SupportBee. Use this to modify the name, content, or tags of a snippet. To find snippet IDs, use the 'Fetch Snippets' action first.
  - body: { id: string, name: string, tags?: string, content: object }
- `POST https://api.mcp.ai/api/supportbee/update/user` — Update an existing SupportBee user's profile information including name, email, role, avatar, or signature. This action modifies user account details via the SupportBee API. You can update one or mult
  - body: { id: integer, name?: string, role?: string, email?: string, signature?: string, avatar_url?: string }

## Example prompts
- "What can I do in Supportbee?"
- "Show me a summary of my Supportbee account"

## More
- Page: https://mcp.ai/supportbee
- Agent spec (llms.txt): https://mcp.ai/supportbee/llms.txt
- Postman collection: https://mcp.ai/supportbee/postman.json