Let Claude, ChatGPT or another assistant that speaks MCP (the Model Context Protocol) look things up in Plum and, if you allow it, add and update records for you.
Anyone in the workspace can connect by signing in. Owners and admins create API keys for assistants that use one.
Connect by signing in (claude.ai, ChatGPT)
- In your assistant, add a custom connector (in claude.ai: Settings → Connectors → Add custom connector; in ChatGPT: Settings → Connectors) with the address https://runonplum.com/api/mcp (or your own Plum site's address followed by /api/mcp). Leave any client ID or secret blank.
- Your assistant sends you to Plum. Sign in if you aren't already.
- Choose the workspace it may use, and whether it may only read or also change records. Then select Allow.
- The assistant works as you: it sees only what you can see in that workspace, and changes only what your role permits. Read and change is offered only if your role can change records.
- If your role changes, the connection follows it at once. If you leave the workspace, it stops working.
- Your connections are listed under Workspace → Integrations, and every connection in the workspace under Settings → API & webhooks for owners and admins. Revoke one there and it stops at once.
- A connection can make up to 600 calls a minute. It stays signed in for 30 days after it was last used; after that, connect again.
Connect with an API key
For assistants that send a header instead of signing in, such as Claude Code.
What you need
- Plum's MCP address: https://runonplum.com/api/mcp (or your own Plum site's address followed by /api/mcp).
- A workspace API key, made in Settings → API & webhooks. It starts with plum_ and is shown once, so copy it straight into your assistant.
Your assistant sends the key with every request, in a header: Authorization: Bearer plum_… followed by the rest of your key.
Claude Code
Run this in a terminal, with your own key in place of plum_…:
claude mcp add --transport http plum https://runonplum.com/api/mcp --header "Authorization: Bearer plum_…"
Claude Desktop and other assistants
- Open your assistant's settings for MCP servers, connectors or tools.
- Add a server that uses HTTP (sometimes called Streamable HTTP), with the address https://runonplum.com/api/mcp.
- Add a header named Authorization with the value Bearer followed by a space and your key.
- Save, then ask something like "Which renewals are coming up in the next 60 days?" to check it works.
If your assistant can only connect by signing in and has no place for a header, use Connect by signing in above.
What your assistant can do
- search_accounts, get_account
- Find companies, and see one with its contacts, deals, what it owns, live ARR and next renewal.
- search_contacts, search_deals
- Find people and deals.
- upcoming_renewals
- Licenses ending soon with no renewal on file, and the ARR at stake.
- revenue_summary
- Live ARR, retention, weighted pipeline and ARR at risk, from the same numbers as Plum's reports.
- list_pipeline_stages
- Your deal stages, so the assistant picks a real one.
- list_object_types, search_object_records, get_object_record
- Your own kinds of record, such as vendors or sites, and their records with every field. Read only.
- create_account, create_contact, create_deal
- Add a company, a person or a deal. Needs a write key.
- move_deal
- Move a deal to another stage, including won or lost. Needs a write key.
- log_activity, create_task
- Record a note, call, meeting or email, or add a to-do. Needs a write key.
Money is always in your workspace's currency.
Read keys and write keys
- A read key lets the assistant look things up and nothing else. If it tries to change something, Plum says the key is read-only and changes nothing.
- A read and write key also lets it add accounts, contacts, deals, activity and tasks, and move deals. Activity it logs, and fields it fills in on accounts and contacts, are marked as coming from the API. It never overwrites a field a person typed.
- No key can record or change licenses, what customers own, or other revenue. Those are changed only inside Plum, by owners, admins and revops.
Keeping it safe
- Each key works in one workspace only, and only while the person who made it is still an owner or admin there.
- A key can make up to 600 calls a minute.
- Your assistant may ask before it changes anything; many let you require that. Start with a read key if you only want answers.
- If a key may have leaked, revoke it in Settings → API & webhooks. It stops working at once.