Claude

Claude can work in your MISSIN workspace for you: finding partners, filing posts into campaigns, and starting a capture after it has shown you the cost. It connects with a secret API key, and the key's level decides what Claude can do.

Connect Claude

Each Claude app connects with a secret key from SettingsDevelopers, and the key's level, Read, Write or Admin, decides what Claude can do. Pick the route for the app you use:

• Claude Desktop: install the MISSIN extension, one file with a form for your key.
• Claude.ai: add a custom connector that sends your key as a request header.
• Claude Code: add the server with one command, or install the plugin below.

Claude acts as the member who created the key, and never above that member's role. No key can create or revoke other keys: that stays in the app.

The Claude Code plugin

The plugin adds the MISSIN server and teaches Claude the MISSIN workflows: resolve names first, quote before capturing, and file posts into campaigns.

/plugin marketplace add MISSINCOUK/missin-mcp
/plugin install missin@missin

Claude Code asks for your key when you enable the plugin and keeps it in its own configuration.

Run the server on your computer

Claude Code can also start the server locally instead of calling the hosted one. It needs Node.js, and the key goes in the environment:

claude mcp add --transport stdio --env MISSIN_API_KEY=sk_live_... --scope user missin -- npx -y @missin/cli mcp

Use --scope user, never --scope project: a project-scoped server is written to your repository, and the key goes with it. Every other route, including Claude Desktop's mcp-remote bridge, is in the developer guide: Connect Claude.

What to ask for

Ask for the outcome. Claude finds the right tools, and stops to ask when it needs you.

If two campaigns match "spring", Claude asks which one you meant instead of guessing.