# Supportbee — MCP server on 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.

By: mcp.ai · official
Page: https://mcp.ai/supportbee

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_supportbee?ms=1787293740000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/supportbee/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/supportbee/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/supportbee/skill.md
Postman collection (v2.1): https://mcp.ai/supportbee/postman.json

## Tools
- supportbee_add_label_to_ticket(ticket_id: integer, label_name: string) — 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.
- supportbee_archive_ticket(id: string) — Tool to archive a SupportBee ticket by its ID. Use when you want to move resolved tickets to the archive.
- supportbee_assign_ticket_to_team(team_id: integer, ticket_id: integer) — 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
- supportbee_create_comment(content: object, ticket_id: string) — 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
- supportbee_create_consequence(spam?: boolean, label?: string, archive?: boolean, assign_team?: string, assign_user?: string) — 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).
- supportbee_create_email(name?: string, email: string, filter_spam?: boolean, use_agent_name?: boolean) — 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.
- supportbee_create_filter(rule_id: string, consequence_id: string) — 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).
- supportbee_create_rule(name: string, active?: boolean, actions: object[], conditions: object[], sort_order?: integer, description?: string) — 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
- supportbee_create_snippet(html?: string, name: string, tags?: string, text: string) — 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 
- supportbee_create_ticket(cc?: string[], spam?: boolean, tags?: string[], labels?: string[], content: string, subject: string, team_id?: integer, agent_id?: integer, requester: object) — 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
- supportbee_create_ticket_reply(content: string, user_id?: integer, ticket_id: string) — 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
- supportbee_create_user_or_customer_group(name?: string, role?: string, email: string) — 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
- supportbee_delete_snippet(id: integer) — 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
- supportbee_delete_ticket(id: integer) — 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.
- 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.
- supportbee_fetch_labels() — Tool to retrieve all custom labels. Use when you need to list labels for ticket categorization.
- supportbee_fetch_snippets(page?: integer, per_page?: integer) — 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
- 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.
- supportbee_get_avg_first_response_time_report(team?: integer, user?: integer, label?: string, since?: string, until?: string) — 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
- 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
- supportbee_get_ticket(id: string) — 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
- supportbee_get_tickets_count_report(label?: string, team_id?: integer, to_date: string, agent_id?: integer, from_date: string) — 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.
- supportbee_list_ticket_comments(ticket_id: string) — 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
- supportbee_list_ticket_replies(page?: integer, per_page?: integer, ticket_id: string) — 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
- supportbee_list_tickets(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) — 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
- supportbee_list_users(type?: string, with_roles?: boolean, with_invited?: boolean) — 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
- supportbee_mark_ticket_as_answered(id: integer|string) — 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
- supportbee_mark_ticket_as_spam(id: string) — Tool to mark a SupportBee ticket as spam. Use when you need to flag unwanted or malicious ticket submissions after obtaining the ticket ID.
- supportbee_mark_ticket_as_unanswered(id: integer|string) — 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
- supportbee_remove_label_from_ticket(ticket_id: integer, label_name: string) — Tool to remove a label from a ticket. Use when you need to unlabel or uncategorize a ticket by removing an existing label.
- supportbee_search_tickets(page?: integer, spam?: boolean, query?: string, trash?: boolean, replies?: boolean, archived?: string, per_page?: integer) — Tool to search SupportBee tickets. Use when you need to find tickets by query with pagination.
- supportbee_show_ticket_reply(reply_id: integer, ticket_id: string) — Tool to fetch a specific reply for a SupportBee ticket. Use when you need details of a single reply by ticket and reply IDs.
- supportbee_show_user_or_customer_group(id: integer) — 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
- supportbee_trash_ticket(id: integer) — Tool to trash a SupportBee ticket by its ID. Use when you need to remove a ticket into the trash folder.
- supportbee_unarchive_ticket(id: integer) — Tool to unarchive a SupportBee ticket by its ID. Use when you need to restore an archived ticket back to active status.
- supportbee_unassign_ticket_from_team(ticket_id: integer) — 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.
- supportbee_unassign_ticket_from_user(ticket_id: integer) — 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.
- supportbee_unmark_ticket_as_spam(id: string) — Tool to unmark a SupportBee ticket as spam. Use when a ticket was incorrectly flagged as spam.
- supportbee_untrash_ticket(id: integer) — Restores a trashed SupportBee ticket back to active status. Use when you need to recover a ticket that was previously moved to trash.
- supportbee_update_snippet(id: string, name: string, tags?: string, content: object) — 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.
- supportbee_update_user(id: integer, name?: string, role?: string, email?: string, signature?: string, avatar_url?: string) — 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

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

## Links
Docs: https://mcp.ai/docs/mcps/supportbee
Website: https://mcp.ai/mcps/supportbee