Support
Get help when you need it.
Contact channels
For bugs, account issues, or general questions:
Response time: within 24 hours on business days.
GitHub Issues
For bug reports, feature requests, and technical issues with the MCP server:
github.com/invarium/invarium-mcp/issues
When filing an issue, include:
- Your MCP client (Claude Desktop, Cursor, Claude Code, etc.)
- The tool that failed and the exact error message
- Steps to reproduce the issue
- Your Python version (
python3 --version)
Community Discord
Coming soon. We are setting up a community Discord for discussions, tips, and direct support from the Invarium team.
Sign up for the waitlist at invarium.dev/community to be notified when the Discord opens.
FAQ
Account and setup
Q: How do I reset my password? A: Go to app.invarium.dev/login and click “Forgot password.” You will receive a reset link via email.
Q: How do I change my workspace name? A: Navigate to Settings in the dashboard sidebar. Under Workspace, edit the name and click Save.
Q: Can I belong to multiple workspaces? A: Yes. You can be a member of multiple workspaces. Switch between them using the workspace selector in the top-left corner of the dashboard.
Q: How do I delete my account? A: Email support@invarium.ai with your account email and a deletion request. We will process it within 48 hours.
MCP server
Q: The MCP server is not connecting. What should I check? A: Verify the following:
- Your API key is correct and set in the
INVARIUM_API_KEYenvironment variable - You have
uvxinstalled (it comes withuv— install viapip install uv) - Your MCP client configuration file is valid JSON
- Run
invarium_connectto test the connection and see the specific error
Q: I get “AUTH_FAILED” when connecting. A: Your API key may be invalid, expired, or revoked. Go to the dashboard under API Keys and create a new key. Update your MCP server configuration with the new key.
Q: Test generation is stuck. How long should it take?
A: Generation typically completes in 10-30 seconds. If invarium_get_tests returns "status": "in_progress" for more than 2 minutes, the generation may have failed. Try generating again with a new request.
Q: Can I use the MCP server without an IDE? A: The MCP server requires an MCP-compatible client. For programmatic use outside an IDE, use the REST API directly (see the CI/CD guide for examples).
Testing
Q: How many tests should I generate?
A: Start with 10-20 tests for initial exploration. For CI/CD gates, 10-20 tests per run is usually sufficient. For thorough coverage, generate 50-100 tests with complexity: 'mixed'.
Q: My BSS score seems too low. What should I check? A: Check the score breakdown in the dashboard:
- Low pass rate — Fix the failing tests, starting with the highest severity
- High severity weighting penalty — You have critical/high failures; fix those first
- Low coverage breadth — You are only testing a few failure categories; generate tests with mixed complexity
- Low consistency — Your agent performs differently at different complexity levels; investigate complex test failures
Q: Can I write my own test cases instead of generating them?
A: Yes. You can create test results manually and sync them with invarium_sync_results. The results format is the same regardless of whether the test cases were generated by Invarium or written by hand.
Q: Do I need to run tests in a specific order? A: No. Test cases are independent and can be run in any order. Each test case is a standalone scenario.
Billing and plans
Q: Is Invarium free during beta? A: Yes. During the beta period, all features are available at no cost. Usage is subject to rate limits.
Q: What happens after beta? A: We will announce pricing and plans before the beta ends. Beta users will receive advance notice and a migration path.
Troubleshooting
Common errors
| Error | Cause | Fix |
|---|---|---|
AUTH_FAILED | Invalid or expired API key | Create a new key in the dashboard |
INVALID_BLUEPRINT | Blueprint JSON does not match the schema | Check the Blueprint Schema and validate your JSON |
RATE_LIMIT_EXCEEDED | Too many requests in the time window | Wait for the retry_after period and try again |
AGENT_NOT_FOUND | No blueprint uploaded for this agent name | Upload a blueprint first with invarium_upload_blueprint |
GENERATION_IN_PROGRESS | A generation is already running for this agent | Wait for it to complete or use a different generation ID |
For the full error code reference, see Error Codes.
Still stuck?
If none of the above resolves your issue:
- Check the Error Codes reference for detailed troubleshooting
- Search GitHub Issues for similar problems
- Email support@invarium.ai with:
- Your workspace name
- The exact error message
- Steps to reproduce
- Any relevant logs or screenshots