Documentation/MCP / AI Integration/Remote Connector

Remote MCP Connector

Connect Claude, Claude Code, scheduled routines, and other MCP-compatible AI assistants directly to M00N Report - no local install, no Node runtime, no config file. Just paste a URL and authenticate.

What is the Remote Connector?

M00N Report exposes a hosted MCP endpoint at https://m00nreport.com/mcp that any MCP-compatible client can connect to over HTTPS. Unlike the local @m00nsolutions/mcp-server package - which spawns a Node process on your machine - the remote connector runs entirely in our infrastructure.

Zero install

No npx, no Node, no PATH headaches. Works from any device.

Always up to date

New tools and prompts go live the moment we ship them.

Works in routines

Drives Claude scheduled routines, Claude Code agents, and CI bots.

OAuth authenticated

Per-user scoped access. Revoke any session from your dashboard.

Connector Endpoint

The connector URL is the same regardless of client:

https://m00nreport.com/mcp

Authentication: connections are authorized via OAuth. The first time you connect, you'll be redirected to M00N Report to approve the integration. After approval, the client receives a token and uses it on every subsequent request.

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:

~/.claude.json or ./.mcp.json

{
  "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.

Token lifetime: OAuth tokens auto-refresh while the routine is active. If you revoke the connector in Settings, every dependent routine fails on its next tick - reconnect and they resume automatically.

ChatGPT & Other MCP Clients

MCP is an open protocol. Any client that speaks the spec's HTTP transport can connect to https://m00nreport.com/mcp.

ChatGPT custom connectors (GPT-5 Pro / Enterprise): paste the same URL into the custom-connector dialog. OAuth flow runs the same way as Claude. Tool discovery is automatic.
Cursor, Continue, Cline, Zed: any IDE assistant that supports remote MCP servers. Use the type: "http" entry shown above.
Custom agents (LangChain, Mastra, your own): point at the URL and implement standard OAuth 2.1 with PKCE. Discovery is served from /.well-known/oauth-authorization-server.

Heads up: not every MCP client supports remote HTTP transport yet - some still require stdio. If your client only supports stdio, fall back to the local NPM package.

Managing Connections

Every active OAuth session is listed under Settings → API & Integrations → MCP Sessions. You can:

See which client (Claude Desktop, Claude Code, ChatGPT, etc.) holds the token
See last-used timestamp and IP
Revoke individual sessions without affecting others
Rotate the underlying API key - revokes all sessions at once

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.

← Quick Start Configuration →