Skip to main content
Glama

testmo-mcp

A Model Context Protocol (MCP) server that provides seamless integration with the Testmo test management platform. This server enables AI assistants to interact directly with your Testmo instance for test case management.

A small local MCP server that exposes Testmo's REST API as tools, so an MCP client (Claude Desktop, Claude Code, etc.) can read your projects/runs/results and create or update runs, results and test cases — without any hosting and without pasting data back and forth.

It runs on your machine and talks to your Testmo instance over HTTPS using an API token you supply via environment variables. The token is never written to disk by the server.

Tools

Read

Tool

What it does

testmo_list_projects

List all projects

testmo_list_runs

List manual runs in a project (name/closed/milestone filters, pagination)

testmo_get_run

One run's summary (status counts, totals)

testmo_list_results

Recorded results for a run

testmo_list_statuses

Result status IDs for a project (Passed/Failed/…)

testmo_list_states

Workflow state IDs (run/case/session) — for state_id when creating

testmo_list_templates

Case template IDs — for template_id / custom fields

testmo_list_cases

List repository cases (folder/name/template filters)

testmo_get

Raw GET against any /api/v1 path (escape hatch)

Write (create/update — no delete)

Tool

What it does

testmo_record_result

Record a result for one test

testmo_record_results_bulk

Record results for 1–100 tests in one request

testmo_create_run

Create a manual run (name, state_id, include_all required)

testmo_update_run

Update a run; set is_closed=true to close it

testmo_create_cases

Create 1–100 repository cases (steps go in custom.custom_steps)

testmo_update_cases

Update 1–100 cases by ids (same fields applied to all)

There is intentionally no delete tool — destructive operations are left out so the server can't remove data.

Related MCP server: TestOps MCP Server

Requirements

  • Node.js 18+ (node --version)

  • A Testmo instance and an API access key (Testmo → User Profile → API access)

Installation

# 1. Clone the repo
git clone https://github.com/<your-account>/testmo-mcp.git
cd testmo-mcp

# 2. Install dependencies
npm install

# 3. (Optional) verify it starts — Ctrl+C to exit
TESTMO_INSTANCE=https://your-team.testmo.net TESTMO_TOKEN=your-testmo-api-key node index.js
# → prints: [testmo-mcp] ready on stdio

Then wire it into your MCP client (below). You don't run the server yourself in normal use — the client launches it for you.

Configure your MCP client

Set the environment variables (see .env.example) and point your client at index.js. For Claude Desktop, edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/) and add:

{
  "mcpServers": {
    "testmo": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/testmo-mcp/index.js"],
      "env": {
        "TESTMO_INSTANCE": "https://your-team.testmo.net",
        "TESTMO_TOKEN": "your-testmo-api-key"
      }
    }
  }
}

Tips:

  • Use the absolute path to node (run which node). GUI apps often launch with a minimal PATH and can't find a bare node.

  • Fully quit and reopen the client so it re-spawns the server.

Environment variables

Var

Required

Purpose

TESTMO_INSTANCE

yes

Your Testmo URL, e.g. https://your-team.testmo.net

TESTMO_TOKEN

yes

API access key (Testmo → User Profile → API access)

TESTMO_DEFAULT_FOLDER_ID

no

Default folder for new cases so Testmo doesn't auto-create one each time

Notes & gotchas

  • This is a local server. It only works where it runs. A client session that executes in the cloud (not on your machine) can't see it — use it from a local session.

  • Testmo has no single "list every test with its name in a run" endpoint. testmo_list_results returns tests that have a recorded result, and the test_id it returns is the run_test_id you pass to testmo_record_result.

  • Linking issue-tracker tickets. Use the issues param on testmo_create_cases / testmo_update_cases. Each item needs display_id (the ticket ID) and integration_id (your Testmo issue integration). Testmo's API doesn't list integration IDs, and it can write linked issues but not read them back. To find your integration_id: check the integration in Testmo's admin area, or create a throwaway case with issues:[{display_id:"<id>", integration_id:<n>}] and read the error — Testmo tells you if an integration ID "does not exist" or "is not associated with this project," so you can find the right one, then delete the throwaway.

  • New cases default to TESTMO_DEFAULT_FOLDER_ID (when set); otherwise Testmo auto-creates a folder per create.

Security

  • The token is read from the environment only; it is never written to any file by this server. .gitignore covers .env, node_modules/, and logs.

  • Whoever configures the client stores the token in that client's config — keep it private and prefer OS secret storage where available. Rotate the key if it is ever exposed.

License

MIT

Available Tools

15 tools
testmo_create_casesA

Create one or more test cases (1-100) in a project's repository. Each case needs a name; folder_id/template_id/state_id are optional (defaults used). Steps and other template-specific fields go in custom with keys like custom_steps, custom_priority (must match the template or you get a 422).

Inputs: cases (required), project_id (required).

testmo_create_runA

Create a new manual test run in a project. Requires name, state_id (from testmo_list_states, entity 'run') and include_all. When include_all is false you must pass cases (array of case IDs).

Inputs: name (required), state_id (required), project_id (required), include_all (required), +8 more.

testmo_getA

Escape hatch: perform a raw GET against any Testmo API path (everything after /api/v1). Use for endpoints not covered by the other tools.

Inputs: path (required).

testmo_get_runA

Get a single run's summary (name, status counts, totals, milestone).

Inputs: run_id (required), expands.

testmo_list_casesA

List test cases in a project's repository. Supports folder/name/template filters and pagination.

Inputs: project_id (required), name, page, per_page, +3 more.

testmo_list_projectsA

List all Testmo projects (id, name, run/milestone counts).

Inputs: no named parameters.

testmo_list_resultsA

List recorded test results for a run. Note: this returns tests that have a recorded result, not necessarily every case in the run. The per-result test_id is the run_test_id needed to record a new result.

Inputs: run_id (required), page, case_id, expands, +3 more.

testmo_list_runsA

List manual test runs for a project. Supports optional name filter, open/closed filter, milestone filter and pagination.

Inputs: project_id (required), name, page, per_page, +2 more.

testmo_list_statesA

List workflow states for a project (run, repository_case, session). Needed for state_id when creating a run or a case.

Inputs: project_id (required).

testmo_list_statusesA

List the result statuses for a project (id → name, e.g. Passed/Failed/Blocked). Needed to know which status_id to use when recording a result.

Inputs: project_id (required).

testmo_list_templatesA

List case templates for a project. Needed for template_id when creating cases (and to know which custom_* fields a template accepts).

Inputs: project_id (required).

testmo_record_resultA

Record a result for one test in a run. run_test_id is the test's per-run id (shown as test_id in testmo_list_results). Get valid status IDs from testmo_list_statuses.

Inputs: run_id (required), status_id (required), run_test_id (required), comment, +1 more.

testmo_record_results_bulkA

Record results for multiple tests in a run in one request (1-100). Each item needs test_id (the per-run test id from testmo_list_results) and status_id. All items are validated before any are written — an invalid item rejects the whole batch.

Inputs: run_id (required), results (required).

testmo_update_casesA

Update 1-100 repository cases (PATCH). Pass ids (the cases to change) plus the fields to apply to ALL of them — the same values are written to every listed case (so name is normally used with a single id). Template custom fields go in custom (e.g. custom_steps, custom_priority) and must exist in every targeted case's template.

Inputs: ids (required), project_id (required), name, tags, +6 more.

testmo_update_runA

Update a run (PATCH). Only provided fields change. Set is_closed=true to close a run (runs cannot be re-opened via the API; false is rejected).

Inputs: run_id (required), docs, name, note, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. The only potential overlap is record_result vs record_results_bulk, but they are clearly single vs bulk operations. The escape hatch testmo_get is explicitly for uncovered endpoints, so no confusion.

    Naming Consistency4/5

    The testmo_ prefix and verb_noun pattern are consistent across tools (list_projects, create_run, update_cases). The single exception is testmo_get which lacks a noun object, but as a general escape hatch this is a minor deviation.

    Tool Count5/5

    15 tools is at the upper boundary of the ideal range but each tool serves a clear purpose in the Testmo workflow, covering projects, runs, results, cases, and supporting lookup data (statuses, states, templates).

    Completeness4/5

    Core CRUD for runs and cases is covered (create, list/get, update) though delete is missing. Results can be listed and recorded both single and bulk. The escape hatch covers additional GET endpoints but not other HTTP methods. Overall the main workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers