mcp-plain
This server lets you manage Plain customer support threads, attachments, and help center articles via MCP.
Thread operations: list, get by ID or reference, create, reply, mark done, add internal notes, update priority, and manage labels.
Custom fields: get, upsert, or batch-update thread custom fields (e.g. impact level, tenant, GitHub PR, PostHog/Sentry sessions).
Thread links: link threads to other Plain threads, Linear/Jira issues, or generic sources; list and remove links.
Attachments: fetch attachment content as text or base64, and get temporary download URLs.
Help centers: list help centers, browse structure, read articles (by ID/slug), create/update articles, and manage article groups.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-plain list my open threads with high priority"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@orbitlogistics/mcp-plain
MCP server for the Plain customer support platform. Provides tools for managing threads, help center articles, and more via the Model Context Protocol.
Setup
With Claude Code
Add to your project's .claude/settings.json:
{
"mcpServers": {
"plain": {
"command": "npx",
"args": ["-y", "@orbitlogistics/mcp-plain@latest"],
"env": {
"PLAIN_API_KEY": "${PLAIN_API_KEY}"
}
}
}
}Then set PLAIN_API_KEY in your shell environment (e.g. .zshrc, .envrc, or a secrets manager).
With other MCP clients
Run the server directly:
PLAIN_API_KEY=plainApiKey_xxx npx @orbitlogistics/mcp-plain@latestRelated MCP server: plane-mcp-server
Tools
Note: This server does not cover the full Plain API — only the endpoints we actively use. If you need additional methods, PRs are welcome!
Threads
list_threads- List threads with filters (status, priority, labels, customer, tenant)get_thread- Get full thread details by ID (includes timeline)get_thread_by_ref- Get thread by reference number (e.g. T-510)get_thread_fields- Get custom field values for a threadcreate_thread- Create a new thread (auto-creates customer by email if needed)reply_to_thread- Send a reply through the original channelmark_thread_as_done- Mark a thread as resolvedupsert_thread_field- Set/update custom field valuesadd_internal_note- Post an internal note (not visible to customer)add_labels- Add category labels to a threadget_label_types- List available label types
Thread links
link_threads- Link a thread to another Plain thread, a Linear issue, a Jira issue, or a generic sourceget_thread_links- List the links on a threadunlink_thread- Remove a link by its link ID
get_thread and get_thread_by_ref also return the first 25 links of a thread in a links array.
Attachments
get_attachment_download_url- Get a temporary download URLget_attachment_content- Fetch attachment content (text or base64)
Help Center
list_help_centers- List all help centersget_help_center- Get help center structure (groups and articles)list_help_center_articles- List articles with full contentget_help_center_article- Get article by IDget_help_center_article_by_slug- Get article by URL slugupsert_help_center_article- Create or update an article (new articles default to DRAFT; updates keep the article's current status, group and slug unless you pass them, and always keep its icon and labels)create_help_center_article_group- Create an article groupdelete_help_center_article_group- Delete an empty article group
Development
pnpm install
pnpm test
pnpm buildLicense
MIT
Available Tools
24 toolsadd_internal_noteA
Post an internal note on a thread. Internal notes are visible to the support team only and are NOT sent to the customer. Use this to post investigation summaries, findings, and recommendations.
Inputs: markdown (required), threadId (required), text, customerId.
add_labelsA
Add category labels to a thread. Use get_label_types first to discover available label type IDs for bug, support, feature-request, sales categories. (Prefer update_thread_labels for combined add/remove.)
Inputs: threadId (required), labelTypeIds (required).
create_help_center_article_groupB
Create a new article group (category/folder) in a help center. Groups organize articles and can be nested.
Inputs: name (required), helpCenterId (required), parentHelpCenterArticleGroupId.
create_threadA
Create a new support thread for a customer. Provide exactly one customer identifier (email, ID, or external ID) and markdown content for the initial message. When using customerEmail, the customer is automatically created in Plain if they don't exist. Optionally set title, description, priority, labels, custom fields, and external ID.
Inputs: markdown (required), app, stage, title, +16 more.
delete_help_center_article_groupA
Delete an article group from a help center. The group must be empty (no articles or child groups).
Inputs: helpCenterArticleGroupId (required).
get_attachment_contentA
Fetch the content of an attachment. Returns the content as text for text-based files (text/*, JSON, XML, etc.) or as base64-encoded string for binary files (images, PDFs, etc.). The response includes the encoding type ('text' or 'base64') and MIME type.
Inputs: attachmentId (required).
get_attachment_download_urlA
Get a temporary download URL for an attachment. Use this to download attachment content when needed. The URL expires after a short time.
Inputs: attachmentId (required).
get_help_centerA
Get a help center by ID with an overview of its article groups and articles (titles, slugs, statuses). Use this to browse the structure of a help center.
Inputs: helpCenterId (required).
get_help_center_articleA
Get a single help center article by ID including its full HTML content, metadata, and group assignment.
Inputs: helpCenterArticleId (required).
get_help_center_article_by_slugA
Get a single help center article by its URL slug. Useful when you know the slug from a URL but not the article ID.
Inputs: slug (required), helpCenterId (required).
get_label_typesA
List available label types in the Plain workspace. Returns label type IDs and names. Call this once to discover the IDs for category labels (bug, support, feature-request, sales) before using add_labels.
Inputs: first.
get_threadA
Get full details of a specific thread including basic info, customer, labels, custom fields, and timeline entries. Timeline entries that carry files (notes, chats, emails, Slack/Teams/Discord messages, custom entries) include an attachments array; pass an attachment's id to get_attachment_content or get_attachment_download_url to retrieve the file.
Inputs: threadId (required).
get_thread_by_refA
Get full details of a thread by its reference number (e.g., T-510). Returns the same details as get_thread.
Inputs: ref (required).
get_thread_fieldsA
Get just the custom field values for a thread. Returns fields like impactLevel, posthogSession, sentrySession, tenant, etc.
Inputs: threadId (required).
list_help_center_articlesA
List articles in a help center with full content (contentHtml). Use this to read all articles at once for review or analysis.
Inputs: helpCenterId (required), first.
list_help_centersA
List all help centers in the Plain workspace. Returns help center IDs, names, descriptions, and types. Use this to discover help center IDs before using other help center tools.
Inputs: no named parameters.
list_threadsA
List support threads from Plain with optional filters. Returns thread summaries including id, title, status, priority, customer info, labels, and timestamps.
Inputs: after, first, priority, statuses, +3 more.
mark_thread_as_doneA
Mark a thread as done/resolved. Use this after replying to a thread when the issue has been resolved.
Inputs: threadId (required).
reply_to_threadA
Send a reply to a customer thread. The reply is sent through the original channel (email, Slack, chat). Provide textContent (required) and optionally markdownContent for rich formatting.
Inputs: threadId (required), textContent (required), markdownContent.
update_thread_fieldsA
Set or update multiple custom fields on a thread in one call. Each field key must be an allowlisted snake_case key (e.g. impact_level, agent_readiness, request_feature, app, stage, tenant_id, notion_ticket, github_pr, posthog_session, sentry_session, reported_from); unknown keys are rejected. Field type (BOOL/ENUM/STRING) is auto-detected per key.
Inputs: fields (required), threadId (required).
update_thread_labelsA
Add and/or remove category labels on a thread in one call. Both 'add' and 'remove' take label TYPE IDs (from get_label_types); removal resolves each type to the applied label automatically. Type IDs not currently on the thread are ignored.
Inputs: threadId (required), add, remove.
update_thread_priorityA
Set a thread's priority. Plain priority is an integer: 0 = Urgent, 1 = High, 2 = Normal, 3 = Low.
Inputs: priority (required), threadId (required).
upsert_help_center_articleA
Create or update a help center article. Articles are always saved as DRAFT status. To update an existing article, provide helpCenterArticleId. Content must be HTML (not markdown). Returns the article data and a link to edit it in the Plain UI.
IMPORTANT: When updating an existing article, you MUST preserve the original HTML formatting exactly. Copy the existing contentHtml verbatim and only modify the specific parts that need changing. Do NOT reformat, re-indent, restructure tags, collapse whitespace, change tag styles, or rewrite any HTML that isn't part of your intended edit. Treat the HTML as a surgical edit, not a rewrite.
Inputs: title (required), contentHtml (required), description (required), helpCenterId (required), +3 more.
upsert_thread_fieldB
Set or update a custom field value on a thread. Use this to write investigation results back to the ticket (e.g., impact_level, app, stage). Field keys use Plain's snake_case format.
Inputs: key (required), value (required), threadId (required), type.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is some overlap: get_thread and get_thread_by_ref both retrieve thread details, and add_labels is less preferred than update_thread_labels, which could cause confusion.
Tools generally follow verb_noun pattern with consistent snake_case, but minor inconsistencies exist like upsert_thread_field (singular) vs update_thread_fields (plural) and add_labels vs update_thread_labels.
With 24 tools covering threads and help centers, the count is appropriate. Each domain has around 12 tools, which is reasonable and not overwhelming.
The tool set covers core CRUD for threads and help centers, but lacks an explicit tool to update thread title/description and tools to update or list article groups.
Maintenance
Related MCP Connectors
The official Planning Center MCP server for interacting with your ministry's data.
MCP server for interacting with the Supabase platform
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for the Plane project management platform that enables users to manage workspaces, projects, and work items. It supports full CRUD operations for issues while providing access to cycles, modules, labels, and workflow states.MIT
- AlicenseCqualityDmaintenanceMCP server for Plane integration, enabling AI agents to interact with Plane APIs and services for project management tasks.100MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating AI agents with the Plane project management platform, providing tools to manage projects, work items, cycles, modules, and more.MIT
- AlicenseBqualityAmaintenanceUnofficial MCP server for self-hosted Plane Community Edition, enabling project management tasks like managing work items, cycles, modules, and initiatives via natural language.1002MIT