# How to integrate Plain MCP with Claude Code ```json { "title": "How to integrate Plain MCP with Claude Code", "toolkit": "Plain", "toolkit_slug": "plain", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/plain/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/plain/framework/claude-code.md", "updated_at": "2026-05-12T10:22:13.990Z" } ``` ## Introduction Manage your Plain directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Plain with - [OpenAI Agents SDK](https://composio.dev/toolkits/plain/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/plain/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/plain/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/plain/framework/codex) - [OpenClaw](https://composio.dev/toolkits/plain/framework/openclaw) - [Hermes](https://composio.dev/toolkits/plain/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/plain/framework/cli) - [Google ADK](https://composio.dev/toolkits/plain/framework/google-adk) - [LangChain](https://composio.dev/toolkits/plain/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/plain/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/plain/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/plain/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/plain/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Plain to Claude Code ### Connecting Plain to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Plain MCP server, and what's possible with it? The Plain MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Plain account. It provides structured and secure access to your B2B support workspace, so your agent can perform actions like managing customers, creating support threads, fetching company details, handling issues, and organizing customer groups on your behalf. - Customer management and onboarding: Automatically create new customer records, fetch customer information by email or ID, and add customers to specific support groups for better organization. - Support thread creation: Let your agent create new support threads tied to customers, making it easy to kick off or escalate conversations without manual intervention. - Issue tracking and retrieval: Fetch all external issue links associated with a customer, helping your team stay on top of ongoing problems and resolutions. - Company and tier information access: Retrieve detailed company profiles and tier metadata, including contract value, owner details, and more, to personalize support interactions. - User and customer cleanup: Safely delete customers or users from the system when offboarding or data hygiene is needed, all through agent-driven actions. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `PLAIN_ADD_CUSTOMER_TO_GROUP` | Add Customer To Group | Tool to add a customer to one or more customer groups. Use when you have a customer and groups ready. | | `PLAIN_CREATE_CUSTOMER_GROUP` | Create Customer Group | Creates a new customer group in Plain for organizing and segmenting customers. Customer groups allow you to categorize customers (e.g., by pricing tier, feature access, or support level) and manage them more effectively in your support workflow. Each group has a unique key, display name, and visual color for easy identification. Use this when you need to create a new customer segment for organization or filtering purposes. | | `PLAIN_CREATE_THREAD` | Create Thread | Tool to create a new thread. Use after obtaining valid customer identifier. | | `PLAIN_DELETE_CUSTOMER` | Delete Customer | Tool to delete a customer from the system. Use when you need to remove a customer by their ID. | | `PLAIN_DELETE_USER` | Delete User | Tool to delete a user from the system. Use when you need to remove a user by their ID after confirming existence. | | `PLAIN_FETCH_COMPANY` | Fetch Company | Tool to fetch company details by ID. Use when you need the full profile of a company, including name, domain, contract value, owner info, and timestamps. | | `PLAIN_FETCH_ISSUES` | Fetch Issues | Fetches external issue tracker links (Jira, Linear, GitHub, etc.) associated with a customer's threads. Returns a flattened list of all issue links across the customer's threads, including the thread context for each issue. Useful for getting a complete view of all external issues related to a customer. With defaults, returns up to threadFirst×linkFirst (2,500) total issue links; results are truncated if limits are exceeded, so reduce threadFirst or linkFirst for large datasets. | | `PLAIN_FETCH_TIER` | Fetch Tier | Tool to fetch a tier by its ID. Use when you have a tier ID and need its metadata before proceeding. Example: "Fetch tier with ID tier_123". | | `PLAIN_GET_CUSTOMER_BY_EMAIL` | Get Customer By Email | Fetch customer details by email address. Returns customer information if found, or null if no customer exists with that email. | | `PLAIN_GET_CUSTOMER_BY_ID` | Get Customer By ID | Tool to retrieve details of a specific customer by their unique ID. Use after obtaining the customer's ID to fetch their complete record. | | `PLAIN_GET_CUSTOMERS` | Get Customers | Tool to fetch a list of customers. Use when retrieving multiple customer records with pagination, filtering, or sorting. | | `PLAIN_GET_THREAD_BY_ID` | Get Thread By ID | Fetches comprehensive details of a specific thread by ID, including customer info, status, priority, labels, and assignments. Returns null if thread not found. | | `PLAIN_GET_USER_BY_ID` | Get User By ID | Fetch workspace user/team member by ID. Returns detailed information about a workspace team member including their name, email, status, and avatar. Note: This fetches workspace users (team members), not customers. Use GET_CUSTOMER_BY_ID for customer data. | | `PLAIN_LIST_CUSTOMER_GROUPS` | List Customer Groups | Tool to list all customer groups. Use when you need to retrieve group metadata with optional pagination or filters. | | `PLAIN_LIST_TIERS` | List Tiers | Tool to retrieve a list of tiers with pagination. Use when you need to browse available tiers after determining pagination cursors. Example: 'List tiers with first=25'. | | `PLAIN_QUERY_THREADS` | List Threads | Tool to retrieve a paginated list of threads. Use when you need to list threads with optional status filtering. | | `PLAIN_REMOVE_CUSTOMER_FROM_GROUP` | Remove Customer From Group | Removes a customer from one or more customer groups in Plain. Use this action to revoke customer group memberships. The customer must be a member of the specified group(s) - attempting to remove a customer from a group they're not in will result in an error. Groups can be identified by either their Plain internal ID (customerGroupId) or their unique key (customerGroupKey). Common use cases: - Downgrade customer tier (e.g., remove from premium_tier group) - Remove customer from beta access groups - Clean up group memberships after customer status changes | | `PLAIN_RUN_GRAPHQL_QUERY` | Run GraphQL Query | Execute any GraphQL query or mutation against Plain API. Use when no specific action exists or for complex operations like thread timelines, advanced filtering, and custom data retrieval. Supports queries, mutations, fragments, and variables. | | `PLAIN_SEND_MESSAGE` | Send Message | Tool to send a new message within a thread. Use after identifying the thread and preparing message content. | | `PLAIN_UPDATE_COMPANY` | Update Company | Upserts (creates or updates) a company in Plain. Provide either companyId (for updating an existing company by ID) or companyDomainName (for upserting by domain). Use this to create new companies, update existing company details (name, domain, contract value), or assign account owners. | | `PLAIN_UPDATE_THREAD` | Update Thread | Tool to update a thread's title. Use when renaming a thread after confirming its ID. | | `PLAIN_UPSERT_CUSTOMER` | Upsert Customer | Tool to upsert (create or update) a customer. Use when syncing or ensuring a customer record exists before subsequent actions. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Plain MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Plain account. It provides structured and secure access so Claude can perform Plain operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Plain account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["plain"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http plain-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['plain'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http plain-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Plain MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (plain-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http plain-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Plain MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your plain-composio entry in the list - This confirms that Claude Code can now access Plain tools If everything is wired up, you should see your plain-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Plain The first time you try to use Plain tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Plain - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Plain authorization flow - Return to the terminal and start using Plain through Claude Code Once authenticated, you can ask Claude Code to perform Plain operations in natural language. For example: - "Add a customer to the enterprise group" - "Fetch company details for Acme Corp" - "List all issues linked to this customer" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["plain"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http plain-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['plain'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http plain-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Plain with Claude Code using Composio's MCP server. Now you can interact with Plain directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Plain operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Plain operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Plain MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/plain/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/plain/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/plain/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/plain/framework/codex) - [OpenClaw](https://composio.dev/toolkits/plain/framework/openclaw) - [Hermes](https://composio.dev/toolkits/plain/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/plain/framework/cli) - [Google ADK](https://composio.dev/toolkits/plain/framework/google-adk) - [LangChain](https://composio.dev/toolkits/plain/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/plain/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/plain/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/plain/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/plain/framework/crew-ai) ## Related Toolkits - [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools. - [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations. - [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates. - [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates. - [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations. - [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code. - [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding. - [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls. - [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources. - [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates. - [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster. - [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment. - [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support. - [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach. - [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback. - [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Plain MCP? With a standalone Plain MCP server, the agents and LLMs can only access a fixed set of Plain tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Plain and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Plain tools. ### Can I manage the permissions and scopes for Plain while using Tool Router? Yes, absolutely. You can configure which Plain scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Plain data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)