Testdino MCP Server

Most developer tooling work still happens through a UI a human drives. Testdino MCP MCP server moves it into the conversation instead. A MCP server for TestDino.

The short version

This MCP server bridges the gap between your TestDino test management platform and AI agents. Instead of manually navigating the TestDino dashboard, you can ask your AI assistant to:

• 🔍 Health Check — Verify your connection and validate your TestDino PAT. Get account information and list all available organizations and projects
• 📊 Test Run Management — List and retrieve detailed information about your test runs with filtering options (branch, time, author, commit, environment)
• 🧪 Test Case Analysis — Get comprehensive details about individual test cases, including errors, logs, execution steps, and artifacts (screenshots, videos, traces)
• 🐛 AI-Assisted Debugging — Debug test case failures with historical data aggregation, failure pattern analysis, and AI-friendly debugging prompts. Analyze patterns across multiple executions to identify root causes
• 🧭 Test Quality Audit — Fetch a server-curated audit prompt plus branch signals, analyze your local test code, and store the completed report back in TestDino without uploading raw source files
• 📝 Test Case Management — Create, update, list, and retrieve manual test cases with comprehensive filtering and organization (status, priority, severity, type, layer, behavior, tags)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: TESTDINO_PAT, TESTDINO_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js: Version 20.0.0 or higher - NPM: Latest version recommended (for package management) - TestDino Account: Valid account with Test Runs and/or Test Case Management access - Personal Access Token (PAT): Required for authentication. Get it from TestDino Settings → Personal Access Tokens

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by testdino-hq; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Testdino MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.