MCP Configuration
Configure the M00N MCP server with environment variables to customize behavior, enable debugging, and connect to your M00N Report instance.
Environment Variables
The MCP server is configured entirely through environment variables in your AI assistant's config file:
| Variable | Required | Default | Description |
|---|---|---|---|
M00N_API_URL | Yes | - | Full URL to your M00N Report instance. Example: https://m00nreport.com |
M00N_API_KEY | Yes | - | Your MCP key from Settings → MCP Keys. Starts with m00n_mcp_ |
M00N_TIMEOUT_MS | No | 30000 | Request timeout in milliseconds. Increase for slow networks or large data sets. |
M00N_DEBUG | No | false | Enable verbose logging for troubleshooting. Set to true to see detailed logs. |
M00N_INSECURE_SSL | No | false | Skip SSL certificate verification. Only use for self-hosted with self-signed certs. |
Full Configuration Example
Here's a complete configuration with all optional settings:
{
"mcpServers": {
"m00n": {
"command": "npx",
"args": ["-y", "@m00nsolutions/mcp-server"],
"env": {
"M00N_API_URL": "https://m00nreport.com",
"M00N_API_KEY": "m00n_mcp_your_key_here",
"M00N_TIMEOUT_MS": "30000",
"M00N_DEBUG": "false"
}
}
}
}Enabling Debug Mode
If you're experiencing connection issues or unexpected behavior, enable debug mode to see detailed logs:
{
"mcpServers": {
"m00n": {
"command": "npx",
"args": ["-y", "@m00nsolutions/mcp-server"],
"env": {
"M00N_API_URL": "https://m00nreport.com",
"M00N_API_KEY": "m00n_mcp_your_key_here",
"M00N_DEBUG": "true"
}
}
}
}Debug logs will be written to stderr. In Claude Desktop, you can view these in the application logs. In Cursor, check the MCP server output panel.
API URL Configuration
SaaS (M00N Report Cloud)
For the hosted M00N Report service, use:
https://m00nreport.comSelf-Hosted Instances
For self-hosted M00N Report, use your instance URL:
https://m00n.yourcompany.comThe MCP server connects to /api/mcp/ endpoints, so ensure your reverse proxy or firewall allows access to these routes.
Rate Limiting
The MCP API is rate-limited to prevent abuse and ensure fair usage:
- 60 requests per minute per MCP key
- Rate limit headers are returned with each response
- Hitting the limit returns a 429 status with
Retry-Afterheader
For most use cases, this limit is more than sufficient. If you're building automated tooling on top of MCP, consider implementing request batching.
Security Best Practices
- Never share your MCP key - It provides the same access as logging in with your account
- Use descriptive key names - Makes it easy to identify and revoke specific keys (e.g., "Claude Desktop - Work MacBook")
- Revoke unused keys - Go to Settings → MCP Keys to revoke keys you no longer need
- Review the audit log - Admins can see all MCP activity in Settings → MCP Keys → Activity Log
- Avoid M00N_INSECURE_SSL - Only use for trusted internal servers with self-signed certificates
Multiple M00N Instances
If you need to connect to multiple M00N Report instances (e.g., staging and production), you can add multiple server configurations:
{
"mcpServers": {
"m00n-prod": {
"command": "npx",
"args": ["-y", "@m00nsolutions/mcp-server"],
"env": {
"M00N_API_URL": "https://m00nreport.com",
"M00N_API_KEY": "m00n_mcp_prod_key_here"
}
},
"m00n-staging": {
"command": "npx",
"args": ["-y", "@m00nsolutions/mcp-server"],
"env": {
"M00N_API_URL": "https://staging.m00n.yourcompany.com",
"M00N_API_KEY": "m00n_mcp_staging_key_here"
}
}
}
}When querying, specify which instance you want to use in your prompt (e.g., "Using m00n-prod, show me the test pass rate...").