A connection only sees the toolsets it asks for. all — what the
setup examples use — turns on every one of them. core is
always enabled even if you ask for nothing; anything else comes from the
x-heizen-toolsets header or a ?toolsets= query param on the server URL,
either all or a comma-separated list. The header wins if you send both.
| Toolset | Tools | Contents |
|---|---|---|
core |
40 | Projects, project brief and context, catalog, tickets, stories, epics, sprints |
tests |
26 | Test plans, suites, cases, environments, executions, runs |
docs |
23 | Wiki, folders, resources and their folders, tags |
requirements |
6 | Search, read, create, update and link requirements; list modules, scopes and personas |
delivery |
8 | Worklogs, story comments |
meetings |
14 | Recordings, notes, transcripts, calendar, bot control |
integrations |
12 | Jira, Confluence, GitHub, PR linking |
api |
1 | studio_api_call escape hatch for endpoints without a tool |
admin |
0 | The project-tag catalogue and its standing guidance documents |
Unknown toolset names are ignored rather than rejected. The gate applies to
tools/call as well as tools/list, so a hidden tool can’t be invoked by
guessing its name. Call list_toolsets in a session to see what’s active.
For what each set actually contains, see Tools.