tuskr-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host address for HTTP transport (default: 0.0.0.0) | 0.0.0.0 |
| MCP_PORT | No | Port number for HTTP transport (default: 8000) | 8000 |
| MCP_TRANSPORT | No | Transport type: http or stdio (default: http) | http |
| TUSKR_ACCOUNT_ID | No | Your Tuskr account ID (optional, can be set on server side) | |
| TUSKR_ACCESS_TOKEN | Yes | Your Tuskr API access token (mandatory for authentication) |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Retrives list of projects based on various filter criteria. Args: filter_name: to filter projects with name containing the specified value filter_status: to filter projects by their status. Two supported values 'active' or 'archived' page: controls number of records in output, every page contains 100 records. Default is 1. |
| list_test_runsA | Retrieves list of test runs of a project with support for various filters. Args: filter_project: specifies the project ID to filter the test runs associated with a particular project filter_name: to filter test runs with name containing the specified value filter_key: to filter test runs with key containing the specified value filter_status: to filter test runs by their status. Two supported values 'active' or 'archived' filter_assigned_to: id of the user to whom test runs are assigned filter_incomplete: if True, fetches all pages and returns only test runs that are not 100% complete, with a trimmed payload (id, key, name, percentDone, counts, assignee, deadline, status). When False (default), returns the raw paginated response from the Tuskr API. page: controls number of records in output, every page contains 100 records. Default is 1. Ignored when filter_incomplete is True. |
| create_test_runA | Creates a new test run in a project. Args:
name: a new test run name
project: name or project ID where to create a test run
test_case_inclusion_type: One of 'ALL' or 'SPECIFIC'. If you specify 'ALL', all test cases in the project will be included in the test run.
If you specify 'SPECIFIC', then you will have to indicate the test cases to include as explained below.
test_cases: list of IDs, keys or names. Required if you have set |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| service_description |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: one for listing projects, one for listing test runs, and one for creating test runs. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: list_projects, list_test_runs, create_test_run.
With only 3 tools, the server feels under-scoped for a test management system. While each tool is justified, the count is borderline low.
Obvious gaps exist: no create_project, no update/delete for test runs, and no tool for viewing test cases. The surface covers only basic listing and creation.