Plain
Plain is a collaborative support platform for B2B support teams, offering a modern, AI-powered interface to consolidate support channels and assist customers efficiently.
Verdict
Common use cases
- Triage support tickets from Slack threads
- Create customer records during onboarding calls
- Group high-value customers for targeted outreach
- Link Jira issues to support threads
- Pull customer history before sales demos
Integration
- Vendor
- Plain
- Category
- other
- Auth
- API_KEY
- Tools
- 23
- Composio slug
plain
Tools
- Add Customer To Group
Tool to add a customer to one or more customer groups. use when you have a customer and groups ready.
- Create Customer
Tool to create a customer. use after gathering email and full name to provision a new customer in plain.
- Create Customer Group
Tool to create a new customer group. use when needing to group customers for segmentation. creates a new customer group with specified name, key, color, and optional externalid.
- Create Thread
Tool to create a new thread. use after obtaining valid customer identifier.
- Delete Customerdestructive
Tool to delete a customer from the system. use when you need to remove a customer by their id.
- Delete Userdestructive
Tool to delete a user from the system. use when you need to remove a user by their id after confirming existence.
- 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.
- Fetch Issues
Tool to fetch external issue links for a customer. use when you need to list all issues across a customer's threads.
- 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".
- Get Customer By Email
Tool to fetch customer details by email. use after confirming the email exists to retrieve detailed customer information.
- 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.
- Get Customers
Tool to fetch a list of customers. use when retrieving multiple customer records with pagination, filtering, or sorting.
- Get Thread By ID
Tool to fetch details of a specific thread using its unique identifier. use after confirming the thread id is correct.
- Get User By ID
Tool to fetch user by id. use when you have a valid user id to retrieve detailed user information.
- List Customer Groups
Tool to list all customer groups. use when you need to retrieve group metadata with optional pagination or filters.
- List Threads
Tool to list all threads. use when you need to retrieve thread summaries with optional pagination.
- List Threads
Tool to retrieve a paginated list of threads. use when you need to list threads with optional status filtering.
- 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'.
- Remove Customer From Groupdestructive
Tool to remove a customer from one or more customer groups. use when you need to revoke memberships.
- Send Message
Tool to send a new message within a thread. use after identifying the thread and preparing message content.
- Update Company
Tool to update an existing company's details. use when modifying a company's name or domain.
- Update Thread
Tool to update a thread's title. use when renaming a thread after confirming its id.
- Upsert Customer
Tool to upsert (create or update) a customer. use when syncing or ensuring a customer record exists before subsequent actions.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Plain from the list. 3. In a separate tab, log into your Plain workspace and go to Settings > API Keys. 4. Generate a new API key with permissions for customers, threads, and groups (read and write). 5. Copy the key and paste it into the Switchy connection dialog, then click Connect. 6. Switchy will verify the key and confirm the connection. 7. To test, open any Space and type '@Plain fetch company [company-id]' — if you see company details returned, the integration is live. 8. From now on, @mention Plain in any message to invoke its tools (create threads, add customers to groups, fetch issues).
What teammates see: by default, memories from Plain are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Support Thread
@Plain create a new thread for customer with email support@acmecorp.com titled 'API rate limit questions' and add the message 'Customer reports 429 errors on /v2/orders endpoint since this morning.'Open in a Space →
Add Customer to VIP Group
@Plain add customer ID cus_abc123 to the customer group 'Enterprise' so they receive priority support routing.Open in a Space →
Fetch Customer Issues
@Plain fetch all issues for customer ID cus_xyz789 and summarize the open bugs and feature requests.Open in a Space →
Create New Customer Record
@Plain create a new customer with email jane.doe@startup.io and full name 'Jane Doe' so we can track her support history.Open in a Space →
Look Up Company Details
@Plain fetch company details for company ID comp_456def and tell me the contract value and account owner.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Plain show me all open threads for customer emma.chen@acme.com and summarize the common themes across her support requests
Found 4 open threads for Emma Chen: 1. "Billing discrepancy" (3 days old) - Questions about invoice #4521 2. "Feature request: bulk export" (1 week old) - Wants CSV export for reports 3. "Integration not syncing" (2 weeks old) - Slack notifications stopped 4. "Onboarding question" (3 weeks old) - Clarification on user roles Common themes: Emma is a power user hitting product limits (export, integrations) and has ongoing billing confusion. Two threads mention her team size growing from 5 to 15 users. Consider flagging for account expansion conversation.
This example shows Plain's thread-fetching combined with AI synthesis. Requires read access to customer data and threads. The MCP returns structured thread metadata (title, age, status); the AI layer adds the thematic analysis. Useful for account health checks before renewal calls.
@Plain create a new customer group called "Enterprise Trial" with key enterprise_trial and assign customers from Acme Corp and Globex Inc to it
Created customer group "Enterprise Trial" (ID: cg_abc123, key: enterprise_trial, color: blue). Added 3 customers from Acme Corp: - Emma Chen (emma.chen@acme.com) - David Park (d.park@acme.com) - Sarah Johnson (sjohnson@acme.com) Added 2 customers from Globex Inc: - Michael Torres (m.torres@globex.com) - Lisa Wang (lwang@globex.com) All 5 customers now tagged with "Enterprise Trial" for segmented workflows.
Demonstrates Plain's customer segmentation workflow: create group, then batch-assign customers. This is a write operation that modifies your Plain workspace state. Useful for organizing trial cohorts or support tiers. The MCP handles the multi-step orchestration (group creation + multiple add-to-group calls) in one prompt.
@Plain fetch the company profile for Acme Corp and check if any of their customers have open issues linked in external trackers like Jira or Linear
Company: Acme Corp (ID: co_xyz789) - Domain: acme.com - Annual contract value: $48,000 - Account owner: Sarah Kim (Support Team) - Created: 2023-11-12 External issues found across 3 Acme customers: - Emma Chen: 2 Jira tickets (PROD-445, PROD-502) linked to billing thread - David Park: 1 Linear issue (ENG-89) linked to API integration thread - Sarah Johnson: No external issues Total: 3 external tracker links active. PROD-502 marked "High Priority" in Jira, opened 5 days ago.
Combines company lookup with cross-customer issue scanning. Shows how Plain tracks external issue references (Jira, Linear, GitHub) alongside support threads. Requires API access to both company and customer data. The external issue count helps surface whether engineering is actively working on blockers for this account.
Use-case deep-dives
When Plain wins for support ops at 5-15 person scale
A 12-person support team handling 400 tickets a week needs to route enterprise customers to senior reps and trial users to onboarding specialists. Plain's group management tools (Create Customer Group, Add Customer To Group) let you segment by contract value or lifecycle stage without leaving the AI workspace. The MCP exposes 23 tools, so your team can create threads, fetch company details, and link external issues in one conversation. This works best when your support load is predictable and your segmentation rules are stable—if you're constantly redefining groups or handling 2,000+ tickets a week, you'll hit rate limits on the API key auth. For teams under 500 tickets weekly, Plain keeps routing logic in Switchy instead of scattered across Slack and your helpdesk.
Plain MCP for onboarding-to-CS transitions at SaaS startups
A 6-person SaaS startup moves customers from onboarding to account management after their first 30 days. The CS lead uses Plain's Fetch Company and Fetch Issues tools to pull contract value, thread history, and linked bugs before the handoff call. The MCP's Create Thread tool lets the CS rep start a new conversation thread directly from Switchy, tagging the customer's group and referencing past issues without switching to Plain's UI. This scenario breaks down if your handoff involves more than three systems—Plain handles customer identity and thread context, but if you also need to sync Salesforce stages and trigger Intercom campaigns, you're better off with a Zapier workflow. For startups where handoff is mostly about context transfer and one new thread, Plain's MCP keeps the process in a single AI session.
When Plain's issue tracking finds doc holes in customer threads
A 4-person support team at a dev tools company notices the same setup question appearing in 20 threads over two weeks. The team lead uses Plain's Fetch Issues tool to pull all external issue links across customer threads, then groups them by topic to spot patterns. The MCP's thread and customer lookup tools let you cross-reference which customer segments hit the same blockers, surfacing whether it's an enterprise-only problem or a universal onboarding gap. This works when your issue volume is under 100 per week and your team already tags issues consistently—Plain's MCP doesn't do semantic clustering, so if your tagging is messy, you'll spend more time cleaning data than finding gaps. For small teams with disciplined tagging, Plain turns thread history into a lightweight gap-analysis tool without exporting CSVs.
Frequently asked
What does the Plain MCP let me do in Switchy?
The Plain MCP connects Switchy to your Plain customer support workspace. You can create and manage customers, threads, and customer groups, fetch company details, and link external issues — all from Switchy's chat interface. It's useful for support teams who want AI to handle routine customer data tasks without switching between tools.
Do I need admin access to connect Plain to Switchy?
You need a Plain API key with permissions matching the actions you want Switchy to perform. Plain uses API key auth, not OAuth, so whoever generates the key controls what Switchy can access. Check your Plain workspace settings to create a key with appropriate scopes for customer and thread management.
Can the Plain MCP send replies to customer threads?
The MCP can create new threads but doesn't expose a tool to post replies within existing threads. If you need to send messages, you'll either use Plain's UI directly or build a custom workflow that calls Plain's API separately. The MCP focuses on customer and group management, not real-time conversation handling.
Why use this instead of just opening Plain in another tab?
Use the MCP when you want AI to automate repetitive tasks like creating customers, assigning groups, or fetching company data based on conversation context. If you're triaging one-off support requests or need Plain's full UI features, open the app. The MCP saves time on bulk operations and data lookups your team does repeatedly.
Who on my team should connect the Plain integration?
Whoever manages your Plain workspace and understands which API permissions your support workflows need. That person generates the API key and adds it to Switchy. Once connected, any Switchy user in your workspace can invoke Plain tools, so ensure your key's scope matches your team's access policies.