Skip to content

Install MCP

Kifas ships a thin proxy CLI on npm — @kifas/mcp — that bridges your MCP client’s stdio transport to our hosted Streamable HTTP server.

Terminal window
# Global (one-time)
npm install -g @kifas/mcp
# Per-project
bun add @kifas/mcp
# or: pnpm add @kifas/mcp / npm install @kifas/mcp

In app.kifas.io → Settings → API keys, click Create key. The value (begins with kifas_live_) is shown exactly once — copy it now.

Edit .cursor/mcp.json in your project root (create if absent):

{
"mcpServers": {
"kifas": {
"command": "npx",
"args": ["-y", "@kifas/mcp"],
"env": { "KIFAS_API_KEY": "kifas_live_..." }
}
}
}

Restart Cursor. The kifas.* tools appear in the agent’s tool list.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the platform equivalent:

{
"mcpServers": {
"kifas": {
"command": "npx",
"args": ["-y", "@kifas/mcp"],
"env": { "KIFAS_API_KEY": "kifas_live_..." }
}
}
}

Add the same mcpServers block to your ~/.continue/config.json.

Speak Streamable HTTP directly to https://mcp.kifas.io/. Send Authorization: Bearer kifas_live_... on every request. The first frame must be initialize; we return an Mcp-Session-Id header you echo on every subsequent request.

  • unauthorized on every call — your KIFAS_API_KEY env var is unset, expired, or revoked. Mint a new one.
  • Cursor doesn’t show kifas tools — restart Cursor after editing .cursor/mcp.json; Cursor reads MCP config only at startup.
  • runner_saturated — our server is at capacity. Retry with backoff; the @kifas/mcp CLI does this automatically.

See the errors reference for the full error code catalog.