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). |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JoinFullStackDev/tcm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server