MCP Server

Connect Claude, VS Code Copilot, and other MCP clients to Streamkap with OAuth sign-in or API tokens to manage CDC pipelines via natural language.

The Streamkap MCP Server lets AI agents interact with your Streamkap Change Data Capture (CDC) infrastructure using natural language. It wraps the Streamkap REST API as Model Context Protocol (MCP) tools that agents can call to monitor pipeline health, inspect sources, destinations, topics, and transforms, manage the full lifecycle of your resources, and troubleshoot issues through logs and metrics.

Prerequisites

• A Streamkap account. The hosted server supports browser-based OAuth sign-in — no API keys to create.
• For header-credential or local setups: an API token (Client ID and Client Secret — see API Tokens) or a Project Key.
• Local mode only: Node.js 20+

Check your Node.js version:

node -v   # should be v20.x or higher

If you need to install or update Node.js, visit nodejs.org or use nvm.

Setup Modes

You can connect in three ways:

• Remote — OAuth sign-in (recommended): Connect to the hosted server at https://mcp.streamkap.com/mcp and authorize with your Streamkap account in the browser. No local install, no API keys to create or store. See Sign in with OAuth.
• Remote — header credentials: Connect to the same hosted URL and pass an API token as HTTP headers (X-Streamkap-Client-ID / X-Streamkap-Client-Secret). Best for headless and CI clients that can set headers but can’t complete a browser sign-in.
• Local (via npx): Run the server locally as a child process with npx -y @streamkap/tools. Credentials are passed as environment variables. Requires Node.js 20+.

Real-time topic streaming is available on the hosted server.

Sign in with OAuth (remote)

The hosted server is an OAuth 2.1 provider, so most MCP clients can connect with a browser sign-in instead of API keys. Point your client at https://mcp.streamkap.com/mcp with no credentials; on first connect it opens a browser where you sign in to Streamkap and authorize access. Your client stores and refreshes the tokens automatically.

claude mcp add --scope user --transport http streamkap https://mcp.streamkap.com/mcp

{
  "servers": {
    "streamkap": {
      "type": "http",
      "url": "https://mcp.streamkap.com/mcp"
    }
  }
}

Setup

The tabs below cover the header-credential (remote) and local (npx) setups. To connect with a browser sign-in instead, see Sign in with OAuth.

claude mcp add --scope user \
  --header "X-Streamkap-Client-ID: your-client-id" \
  --header "X-Streamkap-Client-Secret: your-client-secret" \
  --transport http \
  streamkap https://mcp.streamkap.com/mcp

claude mcp add --scope user streamkap \
  -e STREAMKAP_CLIENT_ID=your-client-id \
  -e STREAMKAP_CLIENT_SECRET=your-client-secret \
  -- npx -y @streamkap/tools

claude mcp list

{
  "mcpServers": {
    "streamkap": {
      "type": "http",
      "url": "https://mcp.streamkap.com/mcp",
      "headers": {
        "X-Streamkap-Client-ID": "your-client-id",
        "X-Streamkap-Client-Secret": "your-client-secret"
      }
    }
  }
}

{
  "mcpServers": {
    "streamkap": {
      "command": "npx",
      "args": ["-y", "@streamkap/tools"],
      "env": {
        "PATH": "/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin",
        "STREAMKAP_CLIENT_ID": "your-client-id",
        "STREAMKAP_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

{
  "mcpServers": {
    "streamkap": {
      "command": "/Users/<you>/.nvm/versions/node/v22.22.0/bin/npx",
      "args": ["-y", "@streamkap/tools"],
      "env": {
        "PATH": "/Users/<you>/.nvm/versions/node/v22.22.0/bin:/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin",
        "STREAMKAP_CLIENT_ID": "your-client-id",
        "STREAMKAP_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

echo "$HOME/.nvm/versions/node/$(node -v)/bin/npx"

{
  "mcpServers": {
    "streamkap": {
      "command": "/opt/homebrew/bin/npx",
      "args": ["-y", "@streamkap/tools"],
      "env": {
        "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin",
        "STREAMKAP_CLIENT_ID": "your-client-id",
        "STREAMKAP_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

{
  "mcpServers": {
    "streamkap": {
      "command": "C:\\Program Files\\nodejs\\npx.cmd",
      "args": ["-y", "@streamkap/tools"],
      "env": {
        "STREAMKAP_CLIENT_ID": "your-client-id",
        "STREAMKAP_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

{
  "servers": {
    "streamkap": {
      "type": "http",
      "url": "https://mcp.streamkap.com/mcp",
      "headers": {
        "X-Streamkap-Client-ID": "your-client-id",
        "X-Streamkap-Client-Secret": "your-client-secret"
      }
    }
  }
}

{
  "servers": {
    "streamkap": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@streamkap/tools"],
      "env": {
        "PATH": "/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin",
        "STREAMKAP_CLIENT_ID": "your-client-id",
        "STREAMKAP_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Verify Your Setup (Optional)

If things aren’t working, the fastest way to check whether it’s your credentials or your client config is to test the same credentials from the terminal using the Streamkap CLI:

npm install -g @streamkap/tools
export STREAMKAP_CLIENT_ID="your-client-id"
export STREAMKAP_CLIENT_SECRET="your-client-secret"
streamkap doctor

If doctor passes the credentials and API authentication checks, the same values will work in your MCP client. This step is optional but the fastest way to catch a bad credential before debugging your client config.

Available Tools

Once connected, your agent has access to tools covering the full Streamkap API surface:

For the full list of API operations, see the API Reference.

Optional: Direct Kafka Tools

Two additional tools — streamkap_consume_messages and streamkap_produce_message — let agents interact with Kafka directly. They require Kafka credentials (bootstrap servers, username, password — all three together) from the Kafka Access page. In local mode, set KAFKA_BOOTSTRAP_SERVERS, KAFKA_API_KEY, and KAFKA_API_SECRET as environment variables. Without Kafka credentials, agents can still read topic data via the REST-based streamkap_get_topic_messages tool.

Workflow Prompts

The MCP server registers seven workflow prompts that surface as slash commands or prompt picks in most clients. Each prompt walks an agent through a structured operational task:

These prompts appear in your client’s prompt picker UI (or as slash commands in clients that support them — the exact format varies between clients).

Real-Time Streaming (Remote Mode Only)

The hosted server exposes an SSE endpoint for real-time topic streaming at https://mcp.streamkap.com/subscribe/<topic>. Supports single topics, comma-separated lists, and regex patterns (?pattern=source_.*). Uses the same X-Streamkap-Client-ID / X-Streamkap-Client-Secret headers as MCP tool calls. Connect with any SSE client, curl, or from your application code.

Not available in local mode. For terminal-based real-time consumption, use streamkap kafka subscribe.

Authentication

The MCP server accepts three credentials:

• OAuth sign-in (hosted server) — authorize with your Streamkap account in the browser; no keys to manage. See Sign in with OAuth.
• API token — a Client ID and Client Secret, passed as headers in remote mode or environment variables in local mode. See API Tokens.
• Project Key — a single bundled credential that also carries tool scoping. See Project Keys.

For API tokens and Project Keys, Streamkap handles token exchange and refresh automatically.

Restricting which tools an agent can use

By default an agent can call every tool its credential is allowed. To narrow that surface:

• Project Key (recommended): set a tool profile and allow/block lists when you create the key — scoping is enforced server-side and can’t be tampered with client-side. See MCP scoping.
• Headers (remote) or environment variables (local): set X-Streamkap-Tool-Profile / MCP_TOOL_PROFILE, X-Streamkap-Allow-Tools / MCP_ALLOW_TOOLS, or X-Streamkap-Block-Tools / MCP_BLOCK_TOOLS. Allow lists win over block lists, which win over the profile.
• OAuth sign-in: uses a fixed curated profile that blocks destructive actions — see Sign in with OAuth.

Optional Environment Variables (Local Mode)

For Kafka and Schema Registry credentials, see Direct Kafka Tools and Kafka Access.

Troubleshooting

Log file locations

Claude Desktop (log file name matches the key in your mcpServers config):

• macOS: ~/Library/Logs/Claude/mcp-server-streamkap.log
• Windows: %APPDATA%\Claude\logs\mcp-server-streamkap.log

macOS: nvm users — npx not found or wrong version

Claude Desktop does not source your shell profile, so it cannot find nvm-managed Node.js. Find your absolute npx path:

echo "$HOME/.nvm/versions/node/$(node -v)/bin/npx"

Then use it as the command in your config. See the Claude Desktop tab above for the full JSON example. Homebrew users (no nvm): use /opt/homebrew/bin/npx (Apple Silicon) or /usr/local/bin/npx (Intel).

Common errors

Documentation MCP

The Streamkap docs site runs its own MCP server at https://docs.streamkap.com/mcp. It is separate from the API server above and carries no credentials — it lets an agent search and read the Streamkap documentation (connector configs, how-tos, API reference) while it works. Add it alongside the streamkap server so your agent can look something up and act on it in the same session.

claude mcp add --scope user --transport http streamkap-docs https://docs.streamkap.com/mcp

{
  "servers": {
    "streamkap-docs": {
      "type": "http",
      "url": "https://docs.streamkap.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "streamkap-docs": {
      "type": "http",
      "url": "https://docs.streamkap.com/mcp"
    }
  }
}

Related

• Agents — overview of all agent integration paths
• CLI — command-line tool with agent-friendly JSON output and scripting support
• API Reference — full REST API documentation