@kotton/ask-kai-mcp

Stdio MCP bridge for Ask K.AI — the ENGIE Italy brand analyst.

This package is a tiny transport adapter for MCP clients that only support stdio (e.g. older Claude Desktop). It forwards every request to the hosted remote MCP endpoint over HTTPS using your personal Bearer key.

Most modern MCP clients (Claude Desktop ≥0.7, Cursor, VS Code, Continue) support remote HTTP directly — you do not need this package in that case. Use the direct remote configuration from your K.AI dashboard at /mcp-access.

Tester install guide (Claude Desktop)

1. Generate your MCP key

• Log into the K.AI dashboard
• Go to Ask K.AI → MCP Access (/mcp-access)
• Click Generate Key
• Copy the key (starts with kai_mcp_)

2. Edit Claude Desktop config

Open claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the ask-kai server block inside mcpServers:

{
  "mcpServers": {
    "ask-kai": {
      "command": "npx",
      "args": ["-y", "@kotton/ask-kai-mcp"],
      "env": {
        "KAI_MCP_KEY": "kai_mcp_YOUR_KEY_HERE"
      }
    }
  }
}

Replace kai_mcp_YOUR_KEY_HERE with your actual key.

3. Restart Claude Desktop

• Fully quit Claude Desktop (not just close the window)
• Re-open it
• Start a new chat
• Click the 🔌 (tools) icon — you should see ask-kai listed with its tools

4. Test it

Type: "Use ask-kai to show me ENGIE's share of search trend."

Troubleshooting

| Symptom | Fix | |---------|-----| | Tools not showing | Check Settings → Developer → MCP Log for ask-kai stderr | | KAI_MCP_KEY missing | Key not set in the env block of the config | | 401 Unauthorized | Key revoked or wrong; regenerate at /mcp-access | | 404 or connection error | Check your internet connection; the endpoint is hosted |

Optional env vars

| Var | Purpose | Default | |-----|---------|---------| | KAI_MCP_KEY | Your personal Bearer key | (required) | | KAI_MCP_URL | Custom endpoint URL | Production K.AI MCP server |

What it does

• Reads JSON-RPC frames from stdin (one per line)
• Adds Authorization: Bearer $KAI_MCP_KEY and Accept: application/json, text/event-stream
• Forwards each request to the remote MCP endpoint
• Writes the upstream JSON response back to stdout

No business logic, no credentials beyond your personal key. All authentication, rate-limiting, and data access lives on the hosted endpoint.

License

UNLICENSED — internal use.