@m00nsolutions/mcp-server

Agentic test management over MCP. This server lets an AI assistant do the work rather than read about it: author test cases, plan and populate manual test executions, link automation back to the cases it covers, cut releases and read project health in M00N Report, an AI-native test management platform.

Which Install Do I Need?

If you are not connecting from claude.ai or claude.com, use this package with an MCP key. That is the rest of this README. For the connector, see the connector guide.

Requirements

Node 20 or newer, and any MCP-capable client.

Installation

No install step. The client launches it with npx, as configured below.

To pin a version in a shared or CI environment, append one to the package name in args, like ["-y", "@m00nsolutions/mcp-server@<version>"]. npm view @m00nsolutions/mcp-server versions lists what is published. A placeholder rather than a number on purpose: a concrete example here goes stale on the next release, and a stale one recommends pinning to a version that no longer has the current fixes.

Quick Start

1. Get an MCP key

In M00N Report, open Settings -> MCP Keys and create a key. It starts with m00n_mcp_ followed by 48 hex characters. This is not the credential the test reporters use; theirs starts with m00n_ and is refused here.

An MCP key carries exactly the permissions of the account it belongs to, never more, and can be scoped down further. Scoping removes tools from the list the client sees, so a shorter tool list than you expected is a scoping decision, not a fault.

The key goes in your own MCP client config on your machine. Do not put it in a workspace file that lives in a repository.

2. Connect your client

Claude Code, one line:

claude mcp add m00n --env M00N_API_URL=https://m00nreport.com --env M00N_API_KEY=m00n_mcp_... -- npx -y @m00nsolutions/mcp-server

Every other client takes the same JSON block:

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

Where that block goes:

For a self-hosted instance, point M00N_API_URL at your own root origin, with no /api suffix. A trailing slash is stripped for you.

3. Confirm the connection

Restart the client, then ask it:

List my M00N Report projects

A list of your projects means the server is connected and the key is valid. An error, or the assistant saying it has no such tool, means it is not; see Troubleshooting.

Tools

Eight areas. The full list with arguments is at /documentation/mcp/tools, kept beside the code. The server fetches its own list from your instance at startup, so what your client sees is what your instance supported when the client connected.

An execution is a manual test run: assignees, environment, dates, and per-step results captured against a snapshot of each case at the moment it was added.

How many tools your key can see comes from your instance:

curl -s -H "X-MCP-Key: $M00N_API_KEY" "$M00N_API_URL/api/mcp/tools" | jq .count

A scoped key sees fewer. No number is quoted here on purpose: the surface changes with the release, and a figure in a README is the one place nobody remembers to update.

Prompts

Guided multi-step workflows the client can offer by name. Each takes a single optional project argument, a name or a UUID; omit it and the server picks the project when only one is in scope.

Resources

Read-only views the client can pull without calling a tool: all projects, project health summary, flaky tests report, currently failing tests, folder structure, launch report, test case content, release summary.

Configuration

The two booleans are on for true, 1 or yes, in any case. Every other value, false and 0 included, leaves them off.

Set both of the first two or neither. Setting one is treated as a mistake and refused, because a half-configured server that starts anyway is harder to diagnose than one that does not.

The base URL is M00N_API_URL here; the test reporters call the same URL M00N_SERVER_URL. All six packages read M00N_API_KEY, but theirs is a project API key rather than an MCP key, so one exported shell variable cannot serve both.

Running Without a Key

Started with neither M00N_API_URL nor M00N_API_KEY, the server runs in preview mode: it lists its tools, prompts and resources from a bundled snapshot and refuses every call with a message saying what to set. Nothing is sent anywhere, because there is nowhere to send it.

That is what lets an inspector, a client or a directory show the tool surface before anyone has signed up. It is a description of the server, never a working one, so the listings come from the snapshot rather than from your instance: a scoped key normally sees fewer tools than the snapshot shows.

Maintainers refresh the snapshot with npm run snapshot:refresh against an unscoped key.

Self-Hosted

Point M00N_API_URL at your own instance and issue the MCP key from that instance. Everything else is identical, which matters when the reason you self-host is that test data cannot leave your network.

With a self-signed certificate, add "M00N_INSECURE_SSL": "true" to the same env block. Full notes: /documentation/mcp/self-hosted.

What Gets Sent

To M00N_API_URL over HTTPS: the tool calls your assistant makes and their arguments. The server is a proxy to your own instance and stores nothing itself.

Every tool call is written to an MCP audit log with a UI in the app, and per-key rate limiting caps a runaway agent. The key is never written to that log, nor to stderr. Under M00N_DEBUG the arguments of every tool call are printed to stderr, so treat that output as you would the data itself.

Troubleshooting