k11 API Functional QA
k11-software-solutions/k11techlab-api-functional-qa-mcp
Functional API tests: story-to-flow, negative tests from the spec, DB checks, evidence.
- tools
- 8
- transport
- STDIO
- env var
- 1
- last updated
- Nov 13, 2026
Tools
8 toolsPublic tool metadata for what this MCP can expose to an agent.
list_environmentsEnvironments and whether each allows writes (and why), auth profiles, databases, fixtures, flows.
Environments and whether each allows writes (and why), auth profiles, databases, fixtures, flows.
No parameter schema in public metadata yet.
draft_flowUser story → scenarios, the spec operations most likely involved, and a flow skeleton.
User story → scenarios, the spec operations most likely involved, and a flow skeleton.
No parameter schema in public metadata yet.
generate_negative_testsNegative and boundary cases for one operation, with real base values from fixtures.
Negative and boundary cases for one operation, with real base values from fixtures.
No parameter schema in public metadata yet.
write_flowValidates and saves a flow under tests/api/.
Validates and saves a flow under tests/api/.
No parameter schema in public metadata yet.
run_flowsRuns flows (all, by path or by tag) with full evidence and reports.
Runs flows (all, by path or by tag) with full evidence and reports.
No parameter schema in public metadata yet.
call_apiOne request with the same guardrails, to explore an API while writing tests.
One request with the same guardrails, to explore an API while writing tests.
No parameter schema in public metadata yet.
query_dbOne read-only query against a test database, with masking.
One read-only query against a test database, with masking.
No parameter schema in public metadata yet.
export_pytestA flow as plain pytest + httpx code.
A flow as plain pytest + httpx code.
No parameter schema in public metadata yet.
Sponsors
Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthly
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any language
Agent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any languageConfiguration
QA_MCP_ROOTFolder with tests/api/ and .qa-mcp/api-test.yaml
Readme
k11 API Functional QA — MCP server & Claude Code plugin
Functional API tests that prove the API did the right thing, down to the database row.
Contract checks tell you an API still has the right shape. They don't tell you whether placing an order charges the right amount, whether cancelling really soft-deletes the row, or whether a malformed request crashes the server. This MCP server lets Claude (or any MCP client) write and run those tests with you:
Details
- Repository
- github.com/k11-software-solutions/k11techlab-api-functional-qa-mcp
- Website
- github.com/K11-Software-Solutions/k11techlab-api-functional-qa-mcp
- Package
k11-api-functional-qa-mcp- Transport
- STDIO
- Registry
- MCP registry, active