AI Integration
Wire Celavii's 83 tools into Claude, Cursor, Windsurf, and any MCP-compatible AI client. stdio + Streamable HTTP transports, OAuth 2.1 PKCE, Bearer tokens.
Use Celavii's 83 tools from inside Claude, Cursor, Windsurf, or any MCP-compatible AI client. Same data, same credits, same rate limits as the REST API.
Two-minute version
- Mint a key in Settings → API (Starter plan or higher)
- In Claude Desktop: Connectors → + → paste
https://www.celavii.com/api/mcp/mcp→ sign in - In Claude Code, Cursor, Windsurf: install the toolkit, then
CELAVII_API_KEY=cvii_live_…
Pick your tool
| Tool | Transport | Install | Auth |
|---|---|---|---|
| Claude Code | stdio | npx -y celavii-mcp@latest | Bearer (cvii_live_*) via env var |
| Claude Desktop / Co-work | streamable-http | Connectors → + → URL | OAuth 2.1 (PKCE) via celavii.com |
| Cursor | stdio | mcp.json + npx celavii-mcp | Bearer via env var |
| Windsurf | stdio | mcp_config.json + npx celavii-mcp | Bearer via env var |
What you get
Every integration above is the same MCP server, exposing 83 tools across 12 groups: meta, profiles, campaigns, lists, analytics, content, manage, knowledge, enhance, scrape, refine, jobs.
Browse them all in the MCP Tools Catalog.
You can scope a key's exposed tools with CELAVII_TOOLS=meta,profiles,jobs (stdio installs) or by issuing a key with limited scopes in Settings → API (all installs).
Authentication
stdio · Bearer token
Claude Code, Cursor, Windsurf, and any other stdio MCP client read your cvii_live_* key from the CELAVII_API_KEY environment variable. The key stays on your machine; nothing transits a browser.
streamable-http · OAuth 2.1 (PKCE)
Claude Desktop and claude.ai Co-work register dynamically (RFC 7591), open a browser to our consent page (/oauth/authorize), and exchange the authorization code for a 1h access token + 60d refresh token. The token wraps a workspace key you pick on the consent page; both flow through the same downstream auth pipeline as raw keys.
See troubleshooting for the full error → fix table.