The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Testcollab MCP Server listing page.
Connect your AI coding assistant to TestCollab — manage test cases, test plans, and suites directly from Claude, Cursor, Windsurf, Codex, or any MCP-compatible client.
Log in to TestCollab → My Profile Settings → API Token tab → Generate new API token.
Claude Code — add to .mcp.json in your project root:
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Codex - register TestCollab from the command line:
Or add the server to ~/.codex/config.toml for all projects, or .codex/config.toml in a trusted project:
Run codex mcp list to confirm the server is configured. See the official Codex MCP documentation for configuration scopes and additional options.
Cursor — add to .cursor/mcp.json in your project root:
List test cases from a project with optional filtering.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
project_id | number | No* | Project ID (*required if TC_DEFAULT_PROJECT not set) |
suite | number|string | No | Filter by suite ID or title |
filter | object | No | Filter conditions |
sort | array | No | Sort specification |
limit | number | No | Max results (1-100, default: 50) |
offset | number | No | Skip N results (default: 0) |
Restart your client, then ask: "What tools do you have for TestCollab?"
You should see the TestCollab tools listed. Try: "Show me all test cases".
| Variable | Required | Default | Description |
|---|---|---|---|
TC_API_TOKEN | Yes | — | API token from your TestCollab profile |
TC_API_URL | No | https://api.testcollab.io | TestCollab API base URL |
TC_DEFAULT_PROJECT | No | — | Default project ID (makes project_id optional in every tool call) |
EU region: If your TestCollab account is hosted in the EU, use
https://api-eu.testcollab.ioas yourTC_API_URL.
| Tool | Description |
|---|---|
| get_project_context | Get suites, tags, custom fields, requirements, test plan folders, releases, users — call this first |
| list_test_cases | Query test cases with filtering, sorting, and pagination |
| get_test_case | Fetch a test case with full step details |
| create_test_case | Create a test case with steps, tags, custom fields |
| update_test_case | Update any test case field |
| list_test_plans | List test plans with filtering/sorting (including release ID/title filters) |
| get_test_plan | Fetch one test plan with included test cases count, configurations, runs, current progress status, and release info |
| create_test_plan | Create a test plan with cases, configurations, assignment, and optional release association |
| update_test_plan | Update test plan metadata, status, assignment, and release association |
| delete_test_plan | Delete a test plan |
| list_suites | List all test suites in a project (supports title, parent, and description filters) |
| get_suite | Get suite details |
| create_suite | Create a new suite |
| update_suite | Update a suite |
| delete_suite | Delete a suite |
| move_suite | Move a suite to a different parent |
| reorder_suites | Reorder suites within a parent |
See Use Cases for detailed workflows.
If you're contributing or want to run from source instead of npx:
Then point your MCP client to the built file:
Server not appearing in your client
node --versionTC_API_TOKEN=your-token npx @testcollab/mcp-serverAuthentication errors
TC_API_URL points to the correct server"project_id is required" error
TC_DEFAULT_PROJECT in your env config, orMIT