killbottleneck-mcp
OfficialRelated Servers
Alternatives to killbottleneck-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to build and update flowcharts, workflow maps, project plans, and research maps in a shared self-hosted workspace, with notes, sources, revision history, conflict detection, and JSON import/export.1MIT

Beever Atlasofficial
AlicenseAqualityDmaintenanceTurns team chat (Slack, Discord, MS Teams, Mattermost) into a living knowledge base - a typed knowledge graph plus auto-generated wiki - exposed to AI agents through a 28-tool MCP server with semantic search, expert finding, and decision tracing.28451Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnd-to-end agent-managed company brain. Humans and any MCP agent co-author living docs (Markdown + extensions), 40+ visual diagrams (Mermaid, BPMN, D2, PlantUML, ELK, Excalidraw), plans, and a self-learning Knowledge Graph. 163 tools across 16 categories. Auth: OAuth 2.1 or API key. Lean, secure, affordable — from individuals to enterprise.MIT
- AlicenseBqualityDmaintenanceMCP server for Claude, ChatGPT, coding agents (cursor, claude code etc), windsurf, etc— generate visual AI automation workflows. Describe a business process, get an interactive flow map you can edit and share.178 npmMIT
- AlicenseCqualityBmaintenanceA living map of all your work: projects, tasks, decisions and what waits on whom, kept by you and your agents through the same tools, with every change logged.105 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and work on self-hosted project canvases, retrieving projects as JSON, Markdown outlines, Mermaid flowcharts or PNG images of the board, and, with a write-enabled token, adding sub-tasks and checking off work while the user watches. Access is scoped by tokens that are read-only by default and can be limited to particular projects.27 npm1MIT
TDQS
Scored across 35 tools
Tools generally target distinct resources and actions across maps, nodes, rules, calendars, events, pages and images. Minor friction exists between create_event and create_events, and between create_rule/save_rule_template, but descriptions make the boundaries readable.
Most tools follow a clear verb_noun pattern (list_maps, create_map, update_node, delete_rule, list_pages). Exceptions like who_is_away and some plural forms (create_events) are minor and do not impede predictability.
35 tools is heavy for one MCP server and spans many largely independent product areas: goal maps, automations, org data, calendars, pages and image generation. A tighter surface or domain-splitting would reduce cognitive load and misselection risk.
Core map, node, rule and page workflows have solid coverage, but there are notable lifecycle gaps: calendars cannot be updated, reminders can be created but not listed/deleted/updated, and whole-map deletion is explicitly unavailable. These create some dead ends for agents.