The Plain connector.
Support threads, timelines and customers. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Plain exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Plain defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Plain tool
5 tools, named as the agent sees them.
- list_threadsread
List support threads (Plain's tickets), newest first. Use it for "what is open right now". Returns thread ids (th_…) that get_thread takes, and customer ids (c_…) that get_customer takes.
- get_threadread
Get one thread with its full timeline — every message, reply and note, rendered as plain text via Plain's own `llmText` field, oldest first. Takes a th_… id from list_threads or search_threads.
- search_threadsread
Full-text search across thread titles, descriptions and message contents, e.g. 'refund', 'SSO login loop'. Use it when you know what the customer said but not which thread. Returns th_… ids for get_thread.
- list_customersread
List customers alphabetically, or search them by name / email / external id when `search` is given. Returns c_… ids that get_customer takes.
- get_customerread
Get one customer by their c_… id (from list_threads or list_customers) or by exact email address. Give exactly one of the two.
Use it from any agent
The same Plain tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Plain API Key in your Plain account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Plain once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.