Documentation/MCP / AI Integration/Self-Hosted Setup

MCP for Self-Hosted M00N Report

Connect Claude Desktop, Cursor or any other MCP client to your self-hosted M00N Report instance. This guide covers configuration for internal URLs, handling self-signed certificates, and troubleshooting common issues.

Use the local package, not the remote connector. The stdio server runs on your workstation and reaches your instance directly, so internal DNS and VPN both work. The hosted remote connector would require your instance to be reachable over public HTTPS from Anthropic's servers, so it is not the right fit for an internal deployment.

Prerequisites

Node.js 18+ - Required for npx to download and run the MCP server
Network access - Your workstation must be able to reach the M00N Report API (typically port 443 or 4000)
MCP key created - Create a key in Settings → MCP Keys

Standard Configuration

For self-hosted instances with valid SSL certificates (e.g., Let's Encrypt, corporate CA), use the standard configuration:

{
  "mcpServers": {
    "m00n": {
      "command": "npx",
      "args": ["-y", "@m00nsolutions/mcp-server"],
      "env": {
        "M00N_API_URL": "https://m00n.yourcompany.com",
        "M00N_API_KEY": "m00n_mcp_your_key_here"
      }
    }
  }
}

Important: Replace m00n.yourcompany.com with your actual M00N Report URL. Don't include trailing slashes or paths.

Internal URLs & Hostnames

The MCP server runs on your local machine and connects to M00N Report. This means:

The URL must be resolvable from your workstation, not just from inside your network
If using internal DNS (e.g., m00n.internal.company.com), ensure your machine can resolve it
VPN may be required if M00N Report is only accessible on the internal network

Testing Connectivity

Before configuring MCP, verify you can reach the M00N Report API:

# Test API health endpoint
curl https://m00n.yourcompany.com/api/health

# Expected response:
# {"status":"ok","version":"1.0.0","mode":"selfhosted"}

Self-Signed Certificates

If your self-hosted M00N Report uses a self-signed SSL certificate, you'll need to tell the MCP server to skip certificate verification:

{
  "mcpServers": {
    "m00n": {
      "command": "npx",
      "args": ["-y", "@m00nsolutions/mcp-server"],
      "env": {
        "M00N_API_URL": "https://m00n.internal.company.com",
        "M00N_API_KEY": "m00n_mcp_your_key_here",
        "M00N_INSECURE_SSL": "true"
      }
    }
  }
}

Security Warning: Only use M00N_INSECURE_SSL=true for trusted internal servers. This disables SSL certificate verification, which could expose your MCP key to man-in-the-middle attacks on untrusted networks.

Alternative: Trust the Certificate

Instead of disabling SSL verification, you can add your internal CA certificate to your system's trust store:

macOS: Add to Keychain Access → System → Certificates
Windows: Import to Trusted Root Certification Authorities
Linux: Add to /etc/ssl/certs/ and run update-ca-certificates

After trusting the CA, you can use the standard configuration withoutM00N_INSECURE_SSL.

Firewall & Proxy Considerations

Required Endpoints

The MCP server needs access to these endpoints on your M00N Report instance:

/api/health - Health check
/api/mcp/instructions - Server instructions
/api/mcp/tools and /api/mcp/tools/call - List and execute the 60 tools
/api/mcp/resources, /api/mcp/resources/templates, /api/mcp/resources/read - the 8 resources
/api/mcp/prompts and /api/mcp/prompts/get - the 7 prompts

Note: these are the internal endpoints the stdio bridge calls on your behalf, not a public REST API for test management. Manage cases, executions and releases through the MCP tools or the UI. The one published HTTP contract is the ingest API, documented as OpenAPI 3.0.3 at /api/ingest/v2/openapi.json.

Proxy Configuration

If your network requires a proxy, you may need to configure it at the system level. The MCP server uses Node.js, which respects the standard proxy environment variables:

HTTP_PROXY=http://proxy.company.com:8080
HTTPS_PROXY=http://proxy.company.com:8080
NO_PROXY=localhost,127.0.0.1

Air-Gapped / Offline Installation

For environments without internet access, you can install the MCP server offline.

Troubleshooting

"Cannot connect to M00N Report API"

Verify the URL is correct and doesn't include trailing slashes
Test connectivity with curl https://your-url/api/health
Check if VPN is required for internal access
Verify firewall allows outbound connections to the M00N Report port

"SSL certificate error" / "UNABLE_TO_VERIFY_LEAF_SIGNATURE"

For self-signed certs: Add M00N_INSECURE_SSL=true
For corporate CA: Add the CA cert to your system trust store
Verify the cert hasn't expired

"Authentication failed: Invalid or revoked MCP key"

Check the key starts with m00n_mcp_
Verify the key isn't revoked in Settings → MCP Keys
Ensure you're using an MCP key, not a project API key

"No tools available"

Check your user account has access to at least one project
Verify the MCP key was created for a user with project access

Enable Debug Logging

Add M00N_DEBUG=true to see detailed connection logs:

"M00N_DEBUG": "true"

For more troubleshooting tips, see the Troubleshooting Guide.

← Available Tools Dashboard →

Last updated 21 July 2026