@meshtest/server

MCP (Model Context Protocol) server for MeshTest — exposes live API testing as 5 tools that AI agents like Claude can call directly.

@meshtest/server lets you drive the entire MeshTest engine — service discovery, regression runs, single-endpoint probes, baseline diffs, AI failure explanation — from inside any MCP-compatible client (Claude Desktop, Cursor, your own agent). Same manifests, same auth, same drift detection as the CLI — just orchestrated by an LLM instead of a human.

Install

npm install -g @meshtest/server

Or run on demand with npx:

npx -y @meshtest/server

Node 18+ required.

Use it from Claude Desktop

Add this to your claude_desktop_config.json (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "meshtest": {
      "command": "npx",
      "args": ["-y", "@meshtest/server"],
      "env": {
        "MESHTEST_CONFIG": "/absolute/path/to/your/repo/meshtest.config.json"
      }
    }
  }
}

Restart Claude. You'll see five new tools appear:

| Tool | What it does | |---|---| | discover_services | Scans configured registries, returns every *.meshtest.yaml it finds with health/coverage metadata | | run_regression | Runs a full test suite, returns structured pass/fail results | | probe_endpoint | Single HTTP request with status/body/latency assertions | | diff_against_baseline | Compares a live response to its stored baseline, flags drift | | explain_failure | Plain-English diagnosis of why a test failed (rule-based today, AI-augmented if ANTHROPIC_API_KEY is set) |

Use it from Cursor

Add this to your Cursor MCP config (~/.cursor/mcp.json):

{
  "mcpServers": {
    "meshtest": {
      "command": "npx",
      "args": ["-y", "@meshtest/server"]
    }
  }
}

Use it from your own agent

It's just a stdio MCP server. Spawn the binary, talk JSON-RPC.

meshtest-server

See the Model Context Protocol spec for client-side details.

Configuration

The server reads meshtest.config.json from (in order):

1. --config <path> flag
2. MESHTEST_CONFIG env var
3. ./meshtest.config.json
4. ~/.meshtest/config.json

{
  "registries": ["~/code/repo-a", "~/code/repo-b"],
  "env": "staging",
  "timeout_ms": 10000,
  "baseline_dir": "~/.meshtest/baselines"
}

Documentation

Full reference, guides, and tool schemas: meshtest-docs.vercel.app

Quick links:

• MCP integration guide — Claude Desktop + Cursor setup
• MCP tools reference — every tool's input/output schema
• Config schema — meshtest.config.json fields
• CLI reference — for when you also want the human-facing CLI

License

See LICENSE. Free for personal, commercial, and internal business use. Source is not redistributed.

— Mukul Kumar · github.com/developerKumar