Skip to main content
Glama
iampopovich

testit-mcp-server

by iampopovich

TestIT MCP

npm version MIT License

Production-ready MCP server for TestIT focused on WorkItems, TestRuns, and TestPlans.

Features

  • Simple API Key authentication via PrivateToken or Bearer scheme.

  • Project-aware tools with optional default project via TESTIT_PROJECT_ID.

  • Project resolution by projectId (UUID) or projectName.

  • Support for TestIT v2 API.

  • stdio transport for local MCP clients (npx or local build).

Related MCP server: jira-aio-mcp-server

Tool Coverage

  • Projects: list, search, get, create, update, delete

  • Work Items: list, search, get, create, update, delete, history, versions, restore, attachments

  • Test Runs: list, get, create, start, stop, delete, results

  • Test Results: get, search, create, update

  • Test Plans: list, get, create, update, delete

  • Shared Steps: list, get (as specialized work items)

  • Configurations: list, get, create, update

  • Analytics: project analytics, test plan analytics, test run analytics

Authentication

This server uses the TestIT API Key:

  1. Use your user-generated API Secret Key in TESTIT_TOKEN.

  2. Server uses Authorization: PrivateToken {token} by default.

  3. If token starts with Bearer , it uses it as is.

Environment Variables

TESTIT_URL=https://testit.instance.com/
TESTIT_TOKEN=your-api-token
# Optional default project (UUID):
# TESTIT_PROJECT_ID=550e8400-e29b-41d4-a716-446655440000
  • TESTIT_URL required

  • TESTIT_TOKEN required

  • TESTIT_PROJECT_ID optional

Run Locally

Prerequisites

  • Node.js v18+ and npm

Step-by-step

  1. Clone the repository:

git clone https://github.com/iampopovich/testit-mcp-server.git
cd testit-mcp-server
  1. Install dependencies:

npm install
  1. Create your local environment file from the example and fill required values:

cp .env.example .env
  1. Build the project:

npm run build
  1. Start the MCP server:

npm start

MCP Client Setup

{
  "mcpServers": {
    "testit": {
      "command": "npx",
      "args": ["-y", "testit-mcp-server"],
      "env": {
        "TESTIT_URL": "https://{testit-instance-address}",
        "TESTIT_TOKEN": "{your-api-token}",
        "TESTIT_PROJECT_ID": "{TestIT-project-uuid}"
      }
    }
  }
}

Related MCP Connectors

  • An MCP server that provides access to Testiny projects, test cases and test runs

  • Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.

  • Search, read, and automate TextMine documents, records, workflows, integrations, and agent tasks.

  • Run, debug, and triage tests from your IDE using natural language, no dashboard switching, no manual data transfers. The TestMu AI (formerly LambdaTest) MCP Server is a single remote server exposing four tool suites: HyperExecute — analyze your project, generate YAML configs and test runner commands, then monitor jobs and sessions. Automation — pull a TestID's details plus command, network, and console logs into one chat for instant root-cause analysis. Includes mobile app upload. SmartUI — explain pixel, layout, DOM, and perceptual changes in a visual regression run, with context-aware React/HTML/CSS fixes. Accessibility — audit any public URL or a local React app against WCAG and get ready-to-apply remediation steps. Connects over https://mcp.lambdatest.com/mcp using OAuth 2.1 — no API keys in your config. One-click install in Cursor; works with Claude, GitHub Copilot, Cline, and any MCP client. Tests execute on the TestMu AI cloud: 3,000+ browsers and 10,000+ real devices.

Related MCP Servers