Corebee Customer Support

What Corebee Customer Support does

The Corebee Customer Support MCP server gives an AI client access to a Corebee workspace’s hosted support inbox. It covers conversations from web chat, WhatsApp, email, and SMS, along with contacts, indexed knowledge, and support metrics.

The server supports both read and write operations. An agent can review recent conversations, retrieve message history, draft or send replies, add internal notes, assign owners, change priorities, apply labels, resolve or reopen conversations, and perform selected bulk actions. Contact tools support lookup, creation, updates, notes, and destructive deletion. Knowledge tools can inspect indexed sources, search their text, and add or update web pages for background indexing.

This listing belongs to the 🎧 Support & Service Management category. The Corebee Customer Support MCP server is a fit for teams that want an agent to help triage an inbox, prepare customer responses, maintain customer records, or produce operational reports.

How it works

Corebee hosts the MCP endpoint at https://corebee.ai/api/v1/mcp/stream. Clients connect using streamable HTTP and authenticate through OAuth 2.1 with PKCE and Dynamic Client Registration. The user signs in through a browser and approves the requested access before tools run; no API key is entered into the client.

The connection acts in the Corebee workspace selected during sign-in. Corebee evaluates the user’s role and membership as requests arrive. Owners can receive all available scopes, agents receive read and write access for conversations, contacts, and knowledge plus metrics and settings read access, and viewers receive read-only access. Existing connections reflect role reductions within about 30 seconds, while a promotion requires reconnecting to gain additional access.

Conversation and contact lists return up to 50 records per page. Conversation messages also use pages of up to 50, with a continuation value for older messages. Bulk conversation and contact operations are limited to 25 records.

Setup and configuration

Install the plugin for a supported client, connect the hosted server, and complete the browser sign-in. The repository documents installation through Cursor and Claude Code, as well as Grok Bot and Grok Build. For Claude Code, the server can be added with the streamable HTTP URL and then authenticated through /mcp or claude mcp login corebee.

Other MCP clients can connect if they support streamable HTTP and OAuth with an HTTPS callback or a loopback HTTP callback. The plugin configuration contains only the remote server URL. The plugin stores no credentials; the client manages OAuth tokens. Access tokens last one hour, while rotating refresh tokens last 30 days.

Tools and capabilities

The Corebee Customer Support MCP server exposes tools for:

• Listing, reading, exporting, replying to, assigning, resolving, reopening, snoozing, labeling, and prioritizing conversations.
• Adding internal notes and applying bulk notes, closures, snoozes, or sentiment tags.
• Searching, reading, creating, updating, annotating, and deleting contacts.
• Listing, inspecting, searching, adding, updating, and deleting knowledge sources.
• Reading conversation, contact, message, and knowledge counts, CSAT, first-response time, agent performance, and channel analytics.

Limitations and notes

Knowledge search is text matching over indexed content, not semantic search. Adding a knowledge URL starts indexing in the background. Adding a label requires its label ID because no tool lists labels.

Deletion is destructive. Removing a contact deletes the contact and its notes but keeps linked conversations, messages, CSAT responses, call records, and other records without that contact. Deleting a knowledge source removes its indexed content while leaving related knowledge gaps unlinked. Review proposed changes before allowing an agent to perform them.

The Corebee Customer Support MCP server includes no hooks, scripts, binaries, or telemetry loaded by a host. Permissions remain subject to the signed-in user’s Corebee role and consented scopes.