tcm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TCM_BASE_URL | Yes | Base URL of the TCM instance (trailing slash optional). | |
| CLUTCH_API_KEY | No | Server-to-server key for headless mode. | |
| TCM_USER_TOKEN | No | User's Supabase JWT for interactive mode. | |
| MCP_AGENT_USER_ID | No | Profiles.id UUID of the Clutch Agent service profile for write attribution (required in headless mode). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_suiteA | Resolve a suite name or prefix to a suite reference. Call this before create_test_case or list_test_cases to get the suite_id. Returns all matches so the caller can disambiguate if >1. |
| list_test_casesA | List test cases with lightweight projection (display_id, title, automation_status, priority). Filterable by project, suite, or search term. Default limit 50, max 200. |
| get_test_caseA | Get full detail of a test case by display_id (e.g. "APA-3"), including all steps. Use this before update_test_case to review the current state. |
| create_test_caseA | Create a test case with steps. REQUIRED: call with dry_run: true first. Review the summary with a human. Only call with dry_run: false (or omit dry_run) after explicit human approval. Steps are required. display_id is assigned by TCM on commit. |
| update_test_caseA | Partially update an existing test case by display_id. If steps is provided, ALL existing steps are wiped and replaced (full-replace — not partial). REQUIRED: call with dry_run: true first. The dry-run shows the full before/after diff including steps. Only call with dry_run: false after explicit human approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: create, update, get, list, and suite search. No two tools overlap in function, and search_suite clearly serves as a helper for resolving suite IDs before other operations.
All tools use a verb_noun snake_case pattern (create_, update_, get_, list_, search_). The only deviation is list_test_cases using plural while others use singular, which is a standard convention for list operations.
Five tools is well-scoped for a test case management server. Each tool covers a necessary operation without redundancy or bloat.
Core CRUD operations are present (create, get, update, list), but delete_test_case is missing. Suite management is limited to search, with no create/update/delete for suites, leaving notable lifecycle gaps.