Other · Local MCP server
Killbottleneck
Goal and process maps for humans and AI agents on your own server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.killbottleneck/killbottleneck- Version
- 0.63.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-20
- Updated
- 2026-09-20
- Publisher
- com.killbottleneck
- Namespace
- Namespace verified by the MCP Registry via the domain killbottleneck.com · how
- Listed under
- Maps MCP servers
- Repository
- github.com/tengolabs/killbottleneck
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | killbottleneck-mcp | 0.63.0 | stdio |
How to connect Killbottleneck
Killbottleneck runs locally from a Node.js package published to the npm registry: killbottleneck-mcp version 0.63.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y killbottleneck-mcp@0.63.0. It reads these environment variables: KB_URL (required) and KB_API_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"killbottleneck": {
"command": "npx",
"args": [
"-y",
"killbottleneck-mcp@0.63.0"
],
"env": {
"KB_URL": "<value>",
"KB_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| KiCad ToolsByte-preserving KiCad automation: 100+ tools for schematics, PCB layout, ERC, DRC, exports. | Local · stdio |
| KicksmashPadel matches for people and agents: create, share one link, join, americano schedules, levels. | Remote · HTTPLive check: ✓ handshake |
| KikaShared memory for client engagements: decisions with reasons, blockers, promises, what was tried. | Remote · HTTPLive check: sign-in required |
| Kilimo MCPMCP server for agriculture coordination in East Africa (kilimo = farming) | Local · stdio |
| KillcordDead-man's switch for Anthropic API spend: kills the key the instant it crosses a limit you set. | Remote · HTTPLive check: ✗ no handshake |
| KilnKiln MCP server for agents: design, slice, print, monitor, and recover physical objects safely. | Local · stdio |
| Kilo IoT PlatformThe IoT platform where AI controls real-world devices: read, provision, automate and command. | Remote · HTTPLive check: sign-in required |
| Kilter Board LogbookRead-only access to your Kilter Board logbook: sessions, sends, projects and grade stats. | Local · stdio |