Repository navigation
v0.3.0
A minor release that changes no tools. It adds a way to give one instance less than all of them: OITC_TOOLSETS limits a server to named subsets of its tool surface, so an agent sees only what its job needs.
| Image | openitcockpit/mcp-server:0.3.0 · amd64 + arm64 |
| Digest | sha256:deabba59b700bc8d2170016bf6bc5d80e590683185d024d3459b03bc56ae276d |
| Requires | openITCOCKPIT 5.6 or newer - one image serves every supported release |
| License | MIT |
Toolsets
OITC_TOOLSETS=triage # 12 tools instead of 24
OITC_TOOLSETS=triage,get_container_tree # a set plus one more tool
OITC_TOOLSETS=all # everything - the defaultA tool that is never registered cannot be called, which makes this a boundary rather than a hint. Six sets ship: triage, patch, catalog, onboarding, config, provisioning. A name that is not a set is taken to be a single tool, so a deployment extends a set without editing anything.
The sets live in toolsets.toml, not in code - read from OITC_TOOLSETS_FILE, else ./toolsets.toml, else the packaged copy. A file found earlier replaces the sets rather than merging with them, and each set's description is what its clients are told the instance is for.
Each shipped set also carries a system prompt supplement, English and German, saying what that role does differently. An instance limited to a set serves its supplement as a resource; an unfiltered one serves none.
Reading back what an instance is limited to
The active sets and their descriptions are served as the resource oitc://skills/oitc-toolsets, as well as in the server instructions. The protocol revision from 2026-07-28 removed the initialize handshake, and with it serverInfo and instructions, so on that path this resource is the only way a client can ask what an instance is for. It also names the tools of each set, which tools/list does not - that list is flat.
One instance per role
docker-compose.roles.yml runs four at once - triage, catalog, patch, and a config instance that may write - each with its own toolset, port, bearer token and openITCOCKPIT API key.
docker compose -f docker-compose.roles.yml up -dTools
Unchanged: 39 tools - 24 read-only, 15 write. No tool was added, removed, renamed or given a different parameter.
Run it
docker run -d -p 8000:8000 \
-e MCP_AUTH_TOKEN="a-token-you-generate" \
-e OITC_APIKEY="the-openITCOCKPIT-api-key" \
-e OITC_BASEURL="https://openitcockpit.example.org" \
-e OITC_TOOLSETS="triage" \
openitcockpit/mcp-server:0.3.0Note
Give each instance its own openITCOCKPIT API key. That account's permissions are what every client of the instance acts with, so splitting the tools only means something if the keys differ too.
Note
Pin 0.3.0, don't follow latest. Still 0.x: the tool set and its parameters have not yet held still across releases.
What went into it
- #8 - toolsets, the system prompt supplements, and the resource that reads them back