Connect a client

You can connect an MCP client by signing in to PMKIN, which is the recommended way, or with a management token. Both connect to the same server, which has the same tools either way. In the app, the MCP page of each project shows these setups with your URLs filled in.

Sign in with PMKIN (recommended)#

Add the server URL below to your client. The first time it connects, it opens PMKIN in your browser: sign in, approve the app, and you’re done. One connection reaches every project you have access to, and the agent asks you which one to work in.

https://mcp.pmkin.io/mcp

claude mcp add --transport http pmkin https://mcp.pmkin.io/mcp

• Claude Code: Run in your terminal.
• Claude Desktop: claude_desktop_config.json.
• Cursor: ~/.cursor/mcp.json.

ChatGPT#

ChatGPT can’t send a key, so it always signs in with the server URL https://mcp.pmkin.io/mcp.

1. Open Settings and go to Connectors.
2. Choose Add custom connector.
3. Paste the MCP server URL above.
4. Sign in with your PMKIN account to authorize access.

Connect with a token#

For agents that run unattended, like a scheduled job or a CI step, or clients that can’t open a browser, send a management token in the Authorization header instead. The connection then reaches the token’s project only.

1. Create a token

   On the project’s MCP page, choose Use an API key instead, then Create a key for this agent. You can also create one on the API page. Copy it right away: it’s shown only once.

2. Add the server with the token

   Replace YOUR_PMKIN_KEY with your token, which starts with pmk_mgmt_.

claude mcp add --transport http pmkin https://api.pmkin.io/mcp --header "Authorization: Bearer YOUR_PMKIN_KEY"

Other clients#

Any client that supports the Streamable HTTP transport and OAuth works with https://mcp.pmkin.io/mcp: it finds the sign-in on its own through the server’s discovery documents. Clients that only support stdio can use mcp-remote as a bridge, the way the Claude Desktop setup does. The exact config differs per client, but it usually looks like this:

{
  "url": "https://mcp.pmkin.io/mcp",
  "transport": "streamable-http"
}

Building a client yourself? OAuth describes the sign-in flow step by step.

Try it#

Once connected, ask your assistant something like:

• “Which PMKIN projects can you see?”
• “What’s in review in my blog project, and what’s due this week?”
• “Pick a ready brief, write a first draft and submit it for review.”

Troubleshooting#

• The browser never opens: the client may not support OAuth. Connect with a token instead.
• “This app was disconnected from PMKIN”: someone disconnected it on the project’s MCP page. Connect it again.
• A project is missing: you only see projects in teams you belong to. Ask a team owner to invite you.
• 401 with a token: check that the header is Authorization: Bearer pmk_mgmt_…, that the token wasn’t revoked, and that it belongs to the project you expect.