# tengolabs/killbottleneck-mcp

Source: https://glimind.com/server/glama%2Ftengolabs%2Fkillbottleneck-mcp
Registry id: `glama/tengolabs/killbottleneck-mcp`
Status: unknown

## Tools (26)

- `add_nodes`: Add a subtree of nodes to an existing map under parent_id (or under the apex when parent_id is omitted). A node is a goal; a node with an assignee (owner) OR a 
- `create_calendar`
- `create_event`
- `create_map`: Create a new goal map from an outline. The map gets an apex (root goal) from `title`/`apex_text`; `outline` items become nested nodes. Layout is computed automa
- `create_reminder`: Set a timed REMINDER for a map node relative to its deadline: offset_days before the deadline (0 = on the deadline day, 1 = the day before) at time HH:MM, insta
- `create_rule`: Create an automation rule on a map: WHEN trigger fires (and optional AND conditions match) DO the actions in order. Rules run for changes made in the UI, via AP
- `delete_calendar`: Delete a shared calendar by id or name together with ALL its events (admin or manager only). Cannot be undone — prefer archiving (not offered here) when the his
- `delete_event`: Delete an event by id (your own, or one in a shared calendar as admin/manager). If you were only invited, you leave the event instead and it stays for the other
- `delete_node`: Delete a node INCLUDING its whole subtree. The apex (root) cannot be deleted and whole maps cannot be deleted via the API. Irreversible — read the map first and
- `delete_rule`: Delete an automation rule. Its run log stays (with the rule name snapshot). Irreversible.
- `delete_rule_template`: Delete a rule template from the library (author or admin only). Rules already created from it are independent copies and stay untouched.
- `get_map`: Read one map as an indented tree with node ids, statuses ([✓] done, [~] in progress, [ ] todo), deadlines and owners. The header shows the key's access level (o
- `get_org_structure`: Read the organization structure (the org map): positions and functions with node ids, holders and deputies. Use the node ids as dynamic rule targets "position:<
- `get_portfolio`: Read the portfolio overview across all team and shared maps the key owner can read (private maps are excluded, exactly like the Organization page): per-project 
- `list_calendars`: List the shared calendars of the instance — company events (shared), rooms and other bookable things (resource), vacations and time off (absence) — with kind, c
- `list_events`: List the calendar events the key owner sees — own, invited, and every event of the shared calendars — in a day range; default today−365 … +730. A multi-day even
- `list_maps`: List goal maps the key owner can see — own, team and shared maps (id, title, node count, last update, access: owner/edit/work/read). Use archived=true to list a
- `list_people`: List the people work can be assigned to: instance members (e-mail, display name, role) and external contacts visible to the key owner (their owner_email is a ps
- `list_rule_runs`: Read the run log of a map's automation rules (newest first, max 100): what fired, on which node, ok/failed/skipped and what the actions did. skipped = a safety 
- `list_rule_templates`: List the instance-wide library of rule templates (shape of a rule without a map or node scope). To use one, read it and call create_rule on the target map with 
- `list_rules`: List automation rules of a map: id, name, enabled, scope node, trigger, conditions, actions, last_fired and last_error (a non-empty last_error means the rule is
- `save_rule_template`: Save a rule shape into the instance-wide template library (create, or update with template_id — only the author or an admin may update). Templates carry no map 
- `update_event`: Change an existing event by id: your own, one in a shared calendar as admin/manager, or your own time off. Only the given fields change; an empty string clears 
- `update_node`
- `update_rule`: Update an automation rule. Pass only `enabled` to toggle it on/off; otherwise pass the FULL new shape (name, trigger, actions, optional conditions/node_id) — pa
- `who_is_away`: Who is away — time off from absence calendars that is approved or not subject to approval (pending and rejected requests are excluded) — in a day range; default

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
