MCP Reference
The Invarium MCP server connects your IDE to the Invarium platform. It exposes five tools for uploading blueprints, generating tests, retrieving results, and syncing test runs — all through the Model Context Protocol.
You can use it from any MCP-compatible client: Claude Desktop, Cursor, Claude Code, or any custom MCP integration.
Tools
invarium_connect
Verify your API key and test the connection.
↗invarium_upload_blueprint
Upload an agent blueprint to the dashboard.
↗invarium_generate_tests
Generate behavioral test cases for an agent.
↗invarium_get_tests
Retrieve generated test cases and check generation status.
↗invarium_sync_results
Sync test results from your IDE to the dashboard.
↗Authentication
All MCP tools require a valid API key. Set the INVARIUM_API_KEY environment variable in your MCP server configuration:
{
"mcpServers": {
"invarium": {
"command": "uvx",
"args": ["invarium-mcp"],
"env": {
"INVARIUM_API_KEY": "inv_your_key_here"
}
}
}
}Get your API key from the Invarium dashboard under API Keys in the sidebar.
API keys are scoped to a workspace. All agents and test runs created with a key belong to that workspace.
MCP Resources
The Invarium MCP server also exposes two resources that your MCP client can read:
| Resource | URI | Description |
|---|---|---|
| Agent Blueprint Template | invarium://templates/agent-blueprint | A JSON template with all supported blueprint fields, ready to fill in. Useful for scaffolding a new blueprint from scratch. |
| Blueprint Prompt Template | invarium://templates/blueprint-prompt | A natural-language prompt you can give to an LLM to help it generate a blueprint from your codebase. |
These resources are read-only and always available once the MCP server is connected.