@kifas/mcp

The Kifas Model Context Protocol bridge. Lets agents (Cursor, Claude Code, Continue, custom) talk to Kifas's hosted MCP server at mcp.kifas.io over stdio.

Install

You don't have to. Use it via npx.

Cursor (.cursor/mcp.json)

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

Claude Code / Claude Desktop (claude_desktop_config.json)

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

Continue / custom hosts

Any MCP host that supports stdio servers can use npx -y @kifas/mcp@latest as the command. The bridge speaks the November 2025 MCP Streamable HTTP protocol over a newline-delimited JSON pipe.

Generate an API key

Sign in at https://app.kifas.io, then go to Settings -> API keys. Free-tier keys are issued instantly. The key starts with kifas_test_ (sandbox) or kifas_live_ (production).

Environment variables

| Var | Required | Default | Description | |---|---|---|---| | KIFAS_API_KEY | yes | - | Bearer token, starts with kifas_live_ or kifas_test_ | | KIFAS_MCP_URL | no | https://mcp.kifas.io/ | Override for self-hosted MCP servers |

You can also pass the key via --api-key <value> if your MCP host doesn't support env.

Tools

The full tool catalog lives at https://docs.kifas.io/tools. The catalog is generated from the same Zod schemas the server uses, so it's always in sync.

License

MIT