techzone-mcp

MCP server for IBM Technology Zone: manage your reservations end-to-end and search the TechZone catalog from Claude. Every state-changing tool describes itself as such so Claude confirms with you before calling; cancellation additionally requires echoing the reservation's exact name.

Tools

Tool	What it does
whoami()	Validates your token, returns your TechZone profile
list_reservations()	All reservations: status, environment, dates (no credentials)
get_reservation(id)	Full detail for one reservation, incl. access info
check_expiring(days)	Active reservations ending within N days (default 3)
search_catalog(term)	Search environments/collections in the catalog
get_catalog_entry(kind, name)	Detail for one catalog entry
search_collections(term)	Search reservable TechZone collections by name
get_collection(id)	Deployment options (platforms/regions) for a collection
extend_reservation(id, days)	Write: extend a reservation's end date by N days
create_reservation(collection_id, name, ...)	Write: reserve an environment from a collection
cancel_reservation(id, confirm_name)	Destructive: delete a reservation (name must match)

Plus two resources: techzone://reservations (live reservation summary) and techzone://reservation/{id} (full detail for one reservation).

Setup

1. Get your API token: techzone.ibm.com → My Profile → API token.
2. Install and register with Claude Code:

uv sync
claude mcp add techzone --env TECHZONE_API_TOKEN=<your-token> -- uv --directory /path/to/techzone-mcp run techzone-mcp

(Or put TECHZONE_API_TOKEN=<your-token> in a .env file in this directory — it is gitignored.)

TechZone tokens expire periodically; when the server reports a 401, grab a fresh token from My Profile.

Development

uv sync
uv run pytest                  # unit tests (mocked, no live API)
uv run python walkthrough.py   # interactive live walkthrough of every tool

The walkthrough steps through all 11 tools against the real API: read-only steps run on Enter, write steps are skipped unless you type yes, and sensitive service-link values are redacted from output.

API endpoints are undocumented publicly; they were derived from the open-source itzcli and verified live. See PLAN.md for design notes.