Plain MCP Server
Connect Plain to your AI agents with the Plain MCP server.
Updated
What is Plain MCP?
The Plain MCP server is a Model Context Protocol server that connects Plain to AI agents and assistants as a set of tools. With it connected, an agent can work with Plain (customer support — tickets, threads, conversations, customer timelines) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Plain tools become available to the model.
Connect the Plain MCP server
Connect Plain MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Plain MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Plain tool to confirm the connection is live.
Connect Plain MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Plain
Provide the Plain MCP server URL or command and complete authentication.
- 3
Test
Reference Plain from chat to confirm Cursor can reach the tools.
Sample use cases
An agent triages incoming Plain support threads by reading the message and assigning priority labels
Faster triage with consistent prioritization, freeing support staff for complex issues.
An agent drafts a response to common support questions by searching the knowledge base and composing a reply
Shorter response times for frequently asked questions.
A scheduled agent reviews open threads older than 48 hours and escalates them with a summary to a senior rep
No support tickets silently aging past SLA thresholds.
An agent enriches customer profiles in Plain with data from a CRM or billing system
Support reps see full customer context without switching tools.
An agent categorizes resolved threads by topic and generates a weekly support trends report
Data-driven insights into recurring issues and support volume patterns.
An agent detects negative sentiment in a Plain thread and routes it to a human specialist immediately
Proactive escalation of frustrated customers before the situation worsens.
An agent creates a bug report from a support thread, extracting reproduction steps and attaching screenshots
Seamless handoff from support to engineering with structured bug reports.
Using Plain MCP with Gamut
On Gamut, the Plain MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Plain and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What support operations does the Plain MCP server enable?
The server exposes tools for reading and responding to support threads, managing customer data, assigning labels and priorities, and accessing thread history. Agents can handle triage, drafting, and escalation workflows.
Can agents send replies through the Plain MCP server?
Yes. Agents can compose and send replies to support threads through Plain. This enables workflows like auto-responding to common questions or drafting replies for human review before sending.
Does the Plain MCP server support automated triage?
Yes. Agents can read incoming threads, analyze content and sentiment, assign priority labels, and route threads to the appropriate team or individual based on rules you define.
Can I connect Plain MCP to other tools in a single agent workflow?
Yes. In Gamut, an agent can use the Plain MCP server alongside other MCP servers (CRM, project management, Slack) to build end-to-end workflows like creating a Jira ticket from a support thread or updating a customer record after resolving an issue.