mcpbeat Sign in

Tools MCP Server

by streamkap Your server? Claim it
answering

Tools is answering right now. Last checked 1 min ago. 140 installs a week from npm.

Streamkap CLI & MCP server - manage CDC pipelines, sources, destinations, and transforms

Installs per day peak 149 · avg 30 · -5% w/w
a month agotoday
Uptime history 31 days of history · worst day 93%
31 days agonow
98.9%
Uptime 24h
91 of 92 checks
Tools
hidden behind auth
517 ms
Response time
average over 24h
140
Installs / week
npm and PyPI

Tools does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add tools --transport http https://mcp.streamkap.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.streamkap.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.tools]
url = "https://mcp.streamkap.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.streamkap.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.streamkap.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: STREAMKAP_PROJECT_KEY (Project Key from Settings > Project Keys. Bundles API, Kafka and Schema Registry credentials plus tool scoping.), STREAMKAP_CLIENT_ID (Streamkap API client ID, if not using a Project Key.), STREAMKAP_CLIENT_SECRET (Streamkap API client secret, if not using a Project Key.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.streamkap.com/mcp streamable-http sign-in 236 ms 1 min ago

Alternatives to Tools

same job, measured the same way
Coalesce Transform
by jessemarshall

MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

local only
Coalesce Transform
by coalesce-software-inc

MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

local only
I
Sling CLI
by flarco

Sling CLI MCP server for data pipeline and replication management

local only
I
Sling CLI
by slingdata

Sling CLI MCP server for querying any database, running data pipelines and managing replications

37 655 installs/wk local only
Jitsu
by jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

answering
Fivetran MCP
by yimingyan

MCP server for Fivetran API - manage syncs, check status, and control data pipelines

236 installs/wk local only
MCP Cloudflare
by crunchtools

Secure MCP server for Cloudflare DNS, Transform Rules, and Page Rules

72 installs/wk local only
Sonenta
by sonenta

MCP server for Sonenta translation management: keys, translations, a11y, and source-health tools.

239 installs/wk local only

Tools — questions

Answers built from our own checks of this server.

Why is there no tool list for Tools?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 517 ms. The bar chart above shows every period we have measured.
How do I connect Tools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Tools?
No API key is involved. Tools answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Tools?
It answers our handshake in 517 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Tools?
The npm package @streamkap/tools was installed 140 times in the last week. Week over week that is -5%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.