How to Connect Cursor, Claude Code & Codex to Abloomify (MCP Guide)
June 1, 2026
Walter Write
4 min read

Quick Setup
- Create an API key in Abloomify and choose what it can access.
- Add the connection (a URL and your key) to your AI tool.
- Ask your AI tool to search Abloomify.
Step 1: Create An API Key
- Give the key a name you will recognize, for example
Cursor on my MacBook. - Choose the tools the key may use:
- Search knowledge: natural-language search over your documents.
- List documents: list, count, or check documents by type or metadata.
- Search conversations & coding sessions: search your prior Bloomy chats and AI coding sessions synced from your devices.
- Identity check (whoami): lets a tool confirm what the key can access.
- Choose the knowledge scopes the key may search: Personal, Team, Department, or Company. You can only grant scopes you already have access to.
- Optionally set an expiry.
abk_xxxxxxxx_xxxxxxxxxxxxxxxx.Step 2: Connect Your AI Tool
https://mcp.abloomify.com/mcp; workspaces on our EU (data-residency) environment use https://mcp-eu.abloomify.com/mcp instead. The examples below show the US URL, so substitute yours if it differs. Always copy the exact URL from your External AI Access page.Cursor
~/.cursor/mcp.json:{
"mcpServers": {
"Abloomify": {
"url": "https://mcp.abloomify.com/mcp",
"headers": { "Authorization": "Bearer abk_your_key_here" }
}
}
}
Claude Code
--scope user flag makes Abloomify available in all your projects, not just the current folder:claude mcp add --scope user --transport http Abloomify https://mcp.abloomify.com/mcp --header "Authorization: Bearer abk_your_key_here"
Claude Desktop
mcp-remote bridge, which requires Node.js on the machine. Add this to ~/Library/Application Support/Claude/claude_desktop_config.json, then restart Claude Desktop:{
"mcpServers": {
"Abloomify": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.abloomify.com/mcp",
"--header",
"Authorization: Bearer abk_your_key_here"
]
}
}
}
Codex
~/.codex/config.toml:[mcp_servers.Abloomify]
url = "https://mcp.abloomify.com/mcp"
http_headers = { Authorization = "Bearer abk_your_key_here" }
npx @abloomify/mcp-bridge
ABLOOMIFY_MCP_URL to your connection URL and ABLOOMIFY_API_KEY to your key, and point Codex at the bridge as a local (stdio) MCP server.Step 3: Use It
- "Search Abloomify for our incident response runbook."
- "List the engineering design docs from the last month in Abloomify."
- "Find the Cursor session where we set up the payments webhook."
Security And Scopes
- A key can never access more than you can. Scopes are capped at your own access in Abloomify.
- Keys are tied to your company and employee identity and every call is audited.
- You can revoke a key at any time from Configs β External AI Access. Revocation takes effect immediately.
- Only the hash of your key is stored. The full key is shown once at creation, so store it in your tool's config and treat it like a password.
Troubleshooting
- The tool connects but returns nothing: confirm the key's scopes include where your content lives (for example, Team vs Company), and that the right tools are enabled on the key.
- "Scope not permitted": the key requested a scope it was not granted. Create a new key with the scope you need (if you have access to it).
- Check what a key can do: if you enabled the Identity check tool, ask your AI tool to run
abloomify_whoami. - Codex cannot connect: use the
npx @abloomify/mcp-bridgefallback described above.
Walter Write
Staff Writer
Tech industry analyst and content strategist specializing in AI, productivity management, and workplace innovation. Passionate about helping organizations leverage technology for better team performance.