Remote MCP Connector

What is the Remote Connector?

M00N Report exposes a hosted MCP endpoint at https://m00nreport.com/mcp that Claude connects to over HTTPS using OAuth 2.1 with PKCE. Unlike the local @m00nsolutions/mcp-server package - which spawns a Node process on your machine - the remote connector runs entirely in our infrastructure.

Connector Endpoint

The connector URL is the same regardless of client:

https://m00nreport.com/mcp

Claude Desktop

In Claude Desktop, open Settings → Connectors and click Add custom connector. Provide:

• Name: m00n
• URL: https://m00nreport.com/mcp

Claude opens an OAuth window in your browser. Sign in to M00N Report and approve. The connector flips to Configure(instead of Connect), and the M00N tools become available in any new chat.

Claude Code

Claude Code reads MCP servers from your ~/.claude.json (user scope) or .mcp.json (project scope). Add an HTTP-type entry:

{
  "mcpServers": {
    "m00n": {
      "type": "http",
      "url": "https://m00nreport.com/mcp"
    }
  }
}

Run claude. On first invocation Claude Code opens the OAuth flow in your default browser; once approved, the token is stored in the Claude Code keychain and reused for every future session.

Verify with /mcp inside Claude Code - you should see m00n listed as connected with the full set of tools available.

Scheduled Routines

Claude routines (cron-driven remote agents) inherit MCP connectors from your account. Once you've connected M00N via the steps above, any routine you author can call M00N tools directly.

Practical patterns we use ourselves:

• Morning health check - daily 9:00 routine that calls get_launches_trends + get_coverage_gapsand posts a summary to Slack.
• Release readiness - routine triggered before cut: get_release → get_launch_tests → verdict in a Confluence page.
• Flake watcher - weekly routine that mines search_tests for chronic flakes and files Jira tickets.
• Regression pass builder - pre-sprint routine that calls create_execution, then add_collections_to_execution, add_suites_to_execution and add_cases_to_execution to assemble the manual run for the sprint.
• Coverage closer - routine that reads get_coverage_gaps, then calls link_autotest_to_case for autotests that already cover a case and create_test_case for the ones that need one.

Cursor, ChatGPT & Other MCP Clients

The remote connector is scoped to Claude. Our authorization server accepts OAuth callbacks on claude.ai and claude.com only, so pasting https://m00nreport.com/mcp into another client's custom-connector dialog fails the handshake.

Every other client connects the same way instead - the local stdio server plus an MCP key. The transport differs; the capabilities do not. You get the identical 60 tools, 7 prompts and 8 resources:

• Cursor, Continue, Cline, Zed, Windsurf: add the @m00nsolutions/mcp-server entry from the Quick Start wherever the tool keeps its MCP servers.
• ChatGPT and other hosted assistants: run the same stdio package wherever the client executes tools, with M00N_API_KEY set to your MCP key.
• Custom agents (LangChain, Mastra, your own): spawn npx -y @m00nsolutions/mcp-server as a subprocess and speak MCP over stdio, passing the key in M00N_API_KEY.

Managing Connections

Disconnect a connector from the client that holds it: remove it under Settings → Connectors in Claude Desktop, or delete the m00n entry from ~/.claude.json or .mcp.json for Claude Code. Access tokens expire after an hour and refresh tokens after 30 days, so a disconnected client loses access on its own.

On the M00N Report side, every tool call made over the connector is written to the MCP audit log, viewable by admins under Settings → MCP Keys → Activity Log with the tool name, parameters, target project, result status and duration. That is where you check what an assistant or a routine actually did.

Troubleshooting

OAuth window doesn't open

Some clients suppress browser launch when running headlessly (CI containers, SSH sessions). Run interactively the first time to complete the handshake, then the cached token works in headless mode.

"Connector unreachable" or 502 errors

If you're behind a corporate proxy, ensure outbound HTTPS to m00nreport.com is allowed. The connector uses standard port 443 - no special ports or protocols.

Tools missing after reconnect

Some clients cache the tool list. Restart the client (or run /mcp reload in Claude Code) to refresh discovery.