Plain (API key)
Give the Sazabi agent tools to search and manage Plain support threads and customers using a Plain API key instead of OAuth.
About
This is an MCP connector that gives the Sazabi agent tools to search and manage Plain support threads and customers, authenticated with a Plain API key instead of OAuth. Plain's own hosted MCP server only supports OAuth and always acts as the connecting human user, so this connector instead uses a Plain API key that you provide to Sazabi. Sazabi recommends minting the key for a dedicated Plain Machine User, so actions taken in Plain are attributed to a bot identity instead of a person. Write operations are enabled by default and can be restricted with the connection's read-only toggle.
What the agent can do:
- Validate the API key and identify its Plain workspace
- Search and browse support threads by customer, status, or topic
- Retrieve customer profiles and search customers by name or email
- Reply to threads and leave internal notes
- Assign threads and mark them done or todo
- Create or update customer profiles
Prerequisites
- An active Plain workspace
- A Plain API key, ideally scoped to a dedicated Machine User
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Plain (API key) in Settings > MCP connectors.
Add your API key
In Plain, go to Settings > API Keys to create a key. Consider creating a Plain Machine User first (Settings > Machine Users) and minting the key for that user. Paste the generated plainApiKey_... key into Sazabi.
Set up with the CLI
Plain (API key) authenticates with a Plain API key, and sazabi mcp-connectors connect only supports OAuth providers — so set up this connector in the dashboard first (above). Once it's connected, the Sazabi CLI can inspect and manage it (installed and authenticated — see sazabi mcp-connectors reference):
sazabi mcp-connectors list
sazabi mcp-connectors details <connection-id>Find the connection ID with sazabi mcp-connectors list. To rotate the stored key later, pass the new key as the replacement Authorization header:
sazabi mcp-connectors update-credentials <connection-id> \
--headers '[{"id":"auth","name":"Authorization","value":"Bearer plainApiKey_..."}]'Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the key is correct and has not been revoked.
Troubleshooting
No tools discovered — Confirm the API key was copied in full, starting with plainApiKey_.
Connection shows needs attention — The key may have been revoked or the Machine User deleted; mint a new key and reconnect from Settings > MCP connectors.