The Streamkap MCP Server lets AI agents interact with your Streamkap infrastructure using natural language. It wraps the Streamkap REST API as Model Context Protocol (MCP) tools that agents can call to monitor pipeline health and metrics, inspect sources, destinations, topics, transforms, and schemas, manage the full lifecycle of your resources, and troubleshoot issues through logs and consumer group analysis.
Prerequisites
- A Streamkap account
- An API token (Client ID and Client Secret) — see API Tokens for how to create one
Setup
Connect your AI client to the hosted Streamkap MCP server at https://mcp.streamkap.com/mcp. Each client passes credentials via HTTP headers — no local installation required.
Claude Code (CLI)
Claude Code (.mcp.json)
Cursor
Run this command in your terminal: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
Add to .mcp.json in your project root:{
"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"
}
}
}
}
Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):{
"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"
}
}
}
}
For other MCP-compatible clients, use the server URL https://mcp.streamkap.com/mcp with the X-Streamkap-Client-ID and X-Streamkap-Client-Secret headers.
How Authentication Works
Your Client ID and Client Secret are passed as HTTP headers with each session. The MCP server exchanges them for a short-lived JWT token and handles automatic refresh — no manual token management required. Sensitive fields (passwords, keys) are never exposed in tool responses.
See API Tokens for a step-by-step guide on creating your Client ID and Client Secret.
Keep your Client Secret safe. If compromised, delete the token from the API Tokens page and create a new one. 
