An MCP server with a key. Claude never sees it.
My MCP server wants a bearer token. I don't want that key pasted into every AI app I use.
In Kin, connect the server by its address and put the key in a header. Kin keeps it encrypted. Then add Kin to Claude as a custom connector. Claude signs in to Kin with OAuth and never holds the key.
Steps checked in Kin on .
Free for 5 connections and 2 AI apps. No card needed.
Set it up
Connect the server by its address
In Kin, connect an MCP server and paste its address. Choose It uses an API key or token, keep the header name
Authorizationunless the server names another, and paste the key. Leave Send it as a bearer token on if the server expects Bearer. Connect an MCP serverChoose a level
Kin lists the server's tools, sorted into reads and changes. Pick a level, or set single tools. Allow, ask or block each tool
Add Kin to Claude
Add a custom connector with Kin's address and sign in. Claude setup
https://app.kinlab.ai/mcp
The key stays in Kin.
Kin sends the key to the server on each call and keeps it encrypted. AI apps never hold it. When we ran this with a GitHub token, Claude's calls worked and the token never appeared in anything Claude received.
Tools that ask the AI app to type in a password or key are left out, so a key can't pass through a chat.
Change it once. Every app keeps working.
Rotate the key in Kin and every AI app keeps working. Nothing to update in Claude, ChatGPT or Cursor.
Questions
Visit the help centerDoes this work with ChatGPT and Cursor too?
Yes. Every AI app you add to Kin reaches the server under the same rules, and none of them holds the key. Add Kin to your AI apps
What if the server uses OAuth instead?
Paste its address, and Kin starts the server's own sign-in. Connect an MCP server
Do I need a paid plan?
No. Connecting a remote MCP server by its address is on every plan. Compare plans