How to Connect Cursor, Claude Code & Codex to Abloomify (MCP Guide)

June 1, 2026

Walter Write

4 min read

Abloomify connected to AI coding tools (Cursor, Claude Code, Codex) through a secure MCP key, showing a knowledge base search flow

Quick Setup

Abloomify exposes your knowledge base to external AI tools through a hosted MCP (Model Context Protocol) server. Any MCP-capable tool, like Cursor, Claude Code, Claude Desktop, or Codex, can search your company knowledge with a scoped API key you create in Abloomify.
The short version is:
  1. Create an API key in Abloomify and choose what it can access.
  2. Add the connection (a URL and your key) to your AI tool.
  3. Ask your AI tool to search Abloomify.
You do not need the Abloomify device agent installed. The MCP server is hosted, so a key plus a URL is all any tool needs.

Step 1: Create An API Key

In Abloomify, go to Configs → External AI Access and click Create API key.
  1. Give the key a name you will recognize, for example Cursor on my MacBook.
  2. 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.
  3. Choose the knowledge scopes the key may search: Personal, Team, Department, or Company. You can only grant scopes you already have access to.
  4. Optionally set an expiry.
Click Create key and copy the key now. For security it is shown only once and cannot be retrieved later. The key looks like abk_xxxxxxxx_xxxxxxxxxxxxxxxx.

Step 2: Connect Your AI Tool

Use the connection URL shown on the External AI Access page (it looks like https://mcp.abloomify.com/mcp) and the key you just copied.

Cursor

On the External AI Access page, click Add to Cursor for a one-click install, or add this to ~/.cursor/mcp.json:
{
  "mcpServers": {
    "abloomify": {
      "url": "https://mcp.abloomify.com/mcp",
      "headers": { "Authorization": "Bearer abk_your_key_here" }
    }
  }
}

Claude Code

Run this in your terminal:
claude mcp add --transport http abloomify https://mcp.abloomify.com/mcp --header "Authorization: Bearer abk_your_key_here"

Claude Desktop

Add the same mcpServers block to ~/Library/Application Support/Claude/claude_desktop_config.json, then restart Claude Desktop:
{
  "mcpServers": {
    "abloomify": {
      "url": "https://mcp.abloomify.com/mcp",
      "headers": { "Authorization": "Bearer abk_your_key_here" }
    }
  }
}

Codex

Add this to ~/.codex/config.toml:
[mcp_servers.abloomify]
url = "https://mcp.abloomify.com/mcp"
http_headers = { Authorization = "Bearer abk_your_key_here" }
If your Codex version does not yet support remote MCP servers, use the Abloomify bridge instead:
npx @abloomify/mcp-bridge
Set 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

Ask your AI tool to search Abloomify, for example:
  • "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."
Your tool will call the Abloomify MCP tools you granted and bring the results into its context.

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-bridge fallback described above.
Share this article
← Back to Blog
Walter Write
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.