DocumentationAgents and APIDeveloper APIData coverage by countrySDKMCP

Camella · MCP

Remote MCP for company warehouse reads

Streamable HTTP at /api/mcp on this same host — not a second product. Auth is Authorization: Bearer cam_live_… (any signed-in key; same keys as /api/v1). No website cookie session. No baked key.

One-click install

Free to sign up. Free to create an API key. Paid plans unlock higher limits and financials.

Cursor has an official install deeplink. Claude Code and Codex have no install protocol — copy the official add command, then export CAMELLA_API_KEY. Reads only: no writes in v1.

Install in CursorInstall in Claude CodeInstall in Codex

Try it after install: get_company EC 1790016919001 (Corporación Favorita).

Endpoint and auth

Sign up free, mint a cam_live_ key in the developer console (any signed-in account), export it as CAMELLA_API_KEY, and send it on every MCP request. Never put a real cam_live_ key in a URL or install deeplink.

export CAMELLA_API_KEY='cam_live_YOUR_KEY'
# https://www.camella.app/api/mcp
Authorization: Bearer $CAMELLA_API_KEY

Tools (reads only)

These three tools call the existing /api/v1 search, entity, and financials handlers. There are no write tools, no contacts tool, and no geo/search_area.

ToolArgumentsMaps to
search_companiesq, country?, limit?GET /api/v1/search
get_companycountry, identifierGET /api/v1/entities/…
get_financialscountry, identifierGET /api/v1/entities/…/financials

get_financials uses the same plan gate as the REST route: 403 if the plan cannot see numbers. Demo lock: Corporación Favorita EC 1790016919001.

Cursor

Official Cursor install deeplink. The config is base64 of { url, headers } and interpolates CAMELLA_API_KEY from your environment — never a live key in the URL. /docs/mcp/cursor 307s to the HTTPS wrapper so a browser click opens Cursor.

Install in Cursor/en/docs/mcp/cursor

{
  "url": "https://www.camella.app/api/mcp",
  "headers": {
    "Authorization": "Bearer ${env:CAMELLA_API_KEY}"
  }
}

cursor.com/en/install-mcp?name=camella&config=… · cursor://anysphere.cursor-deeplink/mcp/install?name=camella&config=…

Claude Code

No official install deeplink. Official CLI: claude mcp add --transport http. The header reads CAMELLA_API_KEY from your shell — do not paste a cam_live_ secret into the command.

Claude install steps

claude mcp add --transport http camella https://www.camella.app/api/mcp --header "Authorization: Bearer ${CAMELLA_API_KEY}"

Equivalent add-json form (same Bearer env interpolation):

claude mcp add-json camella '{"type":"http","url":"https://www.camella.app/api/mcp","headers":{"Authorization":"Bearer ${CAMELLA_API_KEY}"}}'

Codex

No official install deeplink. Official CLI writes ~/.codex/config.toml. --bearer-token-env-var names CAMELLA_API_KEY — Codex sends Authorization: Bearer from that env var. Same Bearer model as /api/v1.

Codex install steps

codex mcp add camella --url https://www.camella.app/api/mcp --bearer-token-env-var CAMELLA_API_KEY
[mcp_servers.camella]
url = "https://www.camella.app/api/mcp"
bearer_token_env_var = "CAMELLA_API_KEY"

/mcp is not this server

/en/mcp stays the in-product agent route (unauthenticated visitors get a login redirect). This install page is /en/docs/mcp. The MCP HTTP endpoint is only /api/mcp.

Developer API docs · SDK · Agent docs · Create an API key