Integration

SupportBee integration

SupportBee is a shared inbox for customer support e-mail. List, search and read tickets, create tickets, reply, comment and keep reply drafts, archive, trash, mark as spam or answered, assign tickets to agents or teams, add and remove labels, read a ticket's audit trail, manage users, customer groups, snippets and forwarding addresses, create filter rules, and read ticket, reply and first-response-time reports. Uploading attachments (multipart) is not exposed. Authentication is the API token from your SupportBee desk (profile picture > API Token), sent as a Bearer token; the company field is your desk subdomain (acme for acme.supportbee.com).

Connect SupportBee How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SupportBee.Built from the 49 SupportBee tools below, on the connection you add once.

What you can do with SupportBee

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Draft, 4 operations

create_ticket_draftCreate ticket draftPOSTSaves a reply draft on a ticket without sending it. Returns the draft.
delete_ticket_draftDelete ticket draftDELETEDeletes the reply draft of a ticket.
get_ticket_draftGet ticket draftGETReturns the reply draft of a ticket. When none exists, returns a new draft quoting the last message.
update_ticket_draftUpdate ticket draftPUTUpdates the reply draft of a ticket without sending it. Returns the draft.

Snippet, 4 operations

create_snippetCreate snippetPOSTCreates a snippet (canned reply). Returns the snippet.
delete_snippetDelete snippetDELETEDeletes a snippet.
list_snippetsList snippetsGETLists the snippets (canned replies) of the desk, each with id, name, tags and content.
update_snippetUpdate snippetPUTUpdates a snippet. Returns the snippet.

Ticket, 4 operations

create_ticketCreate ticketPOSTCreates a ticket in your desk from a requester and content. With notify_requester true, a copy is e-mailed to the requester, CC and BCC. Returns the ticket (id, subject, counts).
delete_ticketDelete ticketDELETEPermanently deletes a ticket that is already in the trash (trash_ticket first). Only admins can do this.
get_ticketGet ticketGETReturns one ticket: subject, requester, content, labels, assignees, reply and comment counts, and dates.
list_ticketsList ticketsGETLists tickets, 15 per page by default, by last activity. Archived, spam and trashed tickets are left out unless asked. Filter by assignee, team, label, requester or date. Use total_only for a count.

User, 4 operations

create_userCreate userPOSTCreates a user (customer by default, or collaborator, agent or admin by role) or a customer group (type customer_group). Returns the user.
get_userGet userGETReturns one user or customer group, with their most recent tickets.
list_usersList usersGETLists the users of the desk (admins, agents and collaborators by default), or customer groups with type=customer_group.
update_userUpdate userPUTUpdates a user or customer group; only the fields sent change. Cannot update the user whose token makes the call.

Label, 3 operations

add_ticket_labelAdd ticket labelPOSTAdds a label to a ticket. The label must already exist in the desk (see list_labels). Returns the label.
list_labelsList labelsGETLists the custom labels of the desk. Use a label name with add_ticket_label or the label filter of list_tickets.
remove_ticket_labelRemove ticket labelDELETERemoves a label from a ticket.

Reply, 3 operations

create_replyCreate replyPOSTPosts a reply on a ticket; the reply is e-mailed to the requester. Admins can reply on behalf of another agent. Returns the reply.
get_replyGet replyGETReturns one reply of a ticket: content, replier, cc, bcc and dates.
list_ticket_repliesList ticket repliesGETLists the replies on a ticket, each with id, replier, content (text, html, attachments), cc and bcc.

Answered, 2 operations

mark_ticket_answeredMark ticket answeredPOSTMarks a ticket as answered.
mark_ticket_unansweredMark ticket unansweredDELETEMarks a ticket as not answered.

Archive, 2 operations

archive_ticketArchive ticketPOSTArchives a ticket. unarchive_ticket reverses it.
unarchive_ticketUnarchive ticketDELETEMoves an archived ticket back to the inbox.

Comment, 2 operations

create_commentCreate commentPOSTAdds an internal comment (not sent to the customer) on a ticket. Returns the comment.
list_ticket_commentsList ticket commentsGETLists the internal comments on a ticket, each with id, commenter and content (text, html, attachments).

Email, 2 operations

create_forwarding_addressCreate forwarding addressPOSTAdds a forwarding address to the desk. Returns the forwarding address.
list_forwarding_addressesList forwarding addressesGETLists the forwarding addresses of the desk. Use an id as forwarding_address_id in create_ticket.

Member, 2 operations

add_group_memberAdd group memberPOSTAdds a user to a customer group. Returns the user.
list_group_membersList group membersGETLists the members of a customer group.

Spam, 2 operations

mark_ticket_spamMark ticket spamPOSTMarks a ticket as spam. unmark_ticket_spam reverses it.
unmark_ticket_spamUnmark ticket spamDELETEMarks a ticket as not spam.

Team assignment, 2 operations

assign_ticket_to_teamAssign ticket to teamPOSTAssigns a ticket to a team. Returns the assignment and the assignee.
unassign_ticket_teamUnassign ticket teamDELETERemoves the team assigned to a ticket.

Trash, 2 operations

trash_ticketTrash ticketPOSTMoves a ticket to the trash. untrash_ticket restores it; delete_ticket removes it for good.
untrash_ticketUntrash ticketDELETERestores a ticket from the trash.

User assignment, 2 operations

assign_ticket_to_userAssign ticket to userPOSTAssigns a ticket to a user (agent). Returns the assignment and the assignee.
unassign_ticket_userUnassign ticket userDELETERemoves the user assigned to a ticket.

Audit, 1 operation

get_ticket_auditGet ticket auditGETReturns the audit trail of a ticket: who did what and when.

Avg first response time, 1 operation

get_first_response_time_reportGet first response time reportGETReturns data points of the average first response time, optionally for one agent, team or label since a date.

Consequence, 1 operation

create_consequenceCreate consequencePOSTCreates a filter consequence: archive, spam, trash, apply a label, or assign a user or a team (not both). Combine it with a rule through create_filter.

Filter, 1 operation

create_filterCreate filterPOSTCreates a filter that applies a consequence (create_consequence) to tickets matching a rule (create_rule).

Replies count, 1 operation

get_replies_count_reportGet replies count reportGETReturns data points of the number of replies, optionally for one agent, team or label since a date.

Rule, 1 operation

create_ruleCreate rulePOSTCreates a filter rule matching incoming tickets by requester email, delivered-to address, subject or body. Combine it with a consequence through create_filter.

Search, 1 operation

search_ticketsSearch ticketsGETSearches tickets by keywords, 15 per page by default, by last activity. Each ticket has id, subject, requester, labels and counts.

Team, 1 operation

list_teamsList teamsGETLists the teams of the desk. Use a team id with assign_ticket_to_team.

Tickets count, 1 operation

get_tickets_count_reportGet tickets count reportGETReturns data points of the number of tickets, optionally for one agent, team or label since a date.

Use SupportBee from Claude Code, Cursor or Codex

Connect SupportBee in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SupportBee operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SupportBee

Create your workspace
Sign up free. Nothing to install.
Connect SupportBee once
Add your SupportBee connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.