MCP Server over a Test Results Store
Let coding agents query test runs and artifacts through typed tools.
- Runs out of the box: yes
- Tests: no
- CI: no
- Docs: no
- Used in production: no
Learning demo, not turnkey. This example is experimental: it shows an idea that works on the bench, but it has not been reviewed for production use. Expect rough edges and check with the owner before reusing it.
Purpose#
A read-only Model Context Protocol server that exposes a test results store through a handful of typed tools: list recent runs, fetch one run's failures and download an artifact reference. Responses are small and structured so an agent can answer "what failed overnight?" without scraping dashboards.
It runs against a local sample database; connecting it to real data would need an access review first.
Technologies & features#
- Technologies
- TypeScriptModel Context ProtocolNode.js
- Features
- MCP Server Integration
- Topics
- AI/ML for DevprimaryTesting & QA
Lessons learned#
- Note
Returning ten failures with a continuation token worked better for agents than returning every failure at once.
Try it#
git clone https://git.example.internal/test-engineering/mcp-test-results.git
cd mcp-test-results
pnpm install && pnpm build
node dist/server.js --db ./sample/results.sqliteCommands come from the owner’s README. Credentials are never stored here.