Connect your AI
How to add Baffin to Claude Code, Claude, ChatGPT, Codex, Cursor or another tool, or let your AI do it, and what to choose on the approval page.
Every tool connects with the same address. Open AI tools in the sidebar and copy the MCP server URL. MCP is the standard way AI tools connect to outside services. Then follow the steps for your tool.
Let your AI set it up
Your AI can do this for you. Open AI tools, copy the line under Or let your AI do it, and paste it into your AI:
Set up Baffin for me by following https://baffin.ai/setup.md
It works out which app it's running in. Where it can, it adds Baffin itself, asking before it runs any command. Where it can't, such as in Claude or ChatGPT, it tells you what to click. You always sign in to Baffin yourself, in your browser: never give your AI a password. The same steps are at baffin.ai/setup.
Claude Code
- In your terminal, run the command shown on the page. It looks like
claude mcp add --transport http baffin <url>, with your URL in place of<url>. - In Claude Code, run
/mcp, choose baffin, and sign in.
Claude.ai and Claude Desktop
- In Claude, open Settings, then Connectors, then Add custom connector, and paste the URL.
- Choose Connect and sign in to Baffin when asked.
ChatGPT
ChatGPT's menu names vary by plan and change often.
- In ChatGPT on the web, open Plugins, choose the plus button, then Add custom MCP server. On some plans it is under Settings, then Apps & Connectors, and Developer mode has to be turned on there first. On a company plan, an admin may have to allow it.
- Paste the URL, pick OAuth for authentication, and create it.
- Install it, and sign in to Baffin when asked.
- Start a new conversation, type @ and choose Baffin. ChatGPT can also pick Baffin on its own, but choosing it with @ is the sure way the first time.
- If ChatGPT shows no Baffin tools, refresh Baffin in ChatGPT's settings and start a new conversation.
Codex
- In your terminal, run
codex mcp add baffin --url <url>. - Then run
codex mcp login baffinto sign in.
Cursor
- Add
{"mcpServers":{"baffin":{"url":"<url>"}}}to~/.cursor/mcp.json, or to.cursor/mcp.jsonin your project. The page gives you this line with your URL filled in. - When Cursor asks you to sign in to baffin, follow the prompt.
Other tools
For tools that can't sign in over MCP, such as the Grok API or your own scripts, open Settings, then Developer, and use Create an access token. Give it a Name, check the knowledge bases it may use, choose its access, and choose Create token. Copy the token right away, because you won't see it again. The tool sends it with every request as Authorization: Bearer followed by the token. Treat it like a password.
The approval page
When your tool asks you to sign in, Baffin opens a page titled "Connect [tool name] to Baffin". The name is what the tool calls itself, and Baffin hasn't verified it. Continue only if you just started connecting this tool. Then choose:
- Knowledge bases: every knowledge base this tool may use. The ones you own are checked, and ones shared with you are not. A knowledge base the tool is already connected to shows Already connected and stays as it is; change it under AI tools.
- What it can do: Read and write lets it read, search and save. Read only lets it read and search but change nothing.
- Let this tool read your uploaded files: lets it open files you can see, so it can quote and cite them.
- When it writes: Follow this knowledge base's write policy publishes changes as your rules allow, and protected changes still wait in Review. Always ask me to review sends every change to Review. For a member's connection there is no choice: every change waits for an owner.
- Access ends after: 30, 60 or 90 days.
Choose Approve, or Deny to refuse. Baffin then sends you back to your tool.
Your choices apply to every knowledge base you check. Where writing isn't set up, that knowledge base is connected read only and its row says so. If Read and write can't be chosen at all, the page says why. Usually it says "Writing isn't set up for this knowledge base yet". An owner opens Settings, then AI instructions, and chooses Set up AI writing. Then start connecting again from your tool. If you're a member, ask an owner to do this. See Troubleshooting.
Reconnecting
If a tool's access has expired, you can renew it from the list of connected tools without reconnecting. See Manage connected tools. An access token can't be renewed: create a new one. If you disconnected a tool, or the approval page says "This request has ended", start connecting again from the tool.
To use a connected tool in another of your knowledge bases, open that knowledge base, go to AI tools, and choose Add this knowledge base under Your tools not connected here. See Multiple knowledge bases.