m00nreport/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?
| | This npm package (stdio) | Hosted remote connector |
|---|---|---|
| How it runs | npx @m00nsolutions/mcp-server as a local process | No local process; the client talks to the API over HTTP |
| Auth | An MCP key in M00N_API_KEY | OAuth 2.1 with PKCE, browser consent screen |
| Clients | Any MCP client: Claude Code, Claude Desktop, Cursor, and others | **claude.ai and claude.com only** |
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@ "]. 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:
Every other client takes the same JSON block:
Where that block goes:
| Client | Config file |
|---|---|
| Cursor | ~/.cursor/mcp.json |
| Claude Desktop, macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop, Windows | %APPDATA%\Claude\claude_desktop_config.json |
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.
| Area | What it covers |
|---|---|
| Projects and analytics | Projects, launch trends and statistics, per-test history, search across automated tests |
| Test cases | Create, read, update, move, delete, bulk edit, and link an automated test to the case it covers |
| Folders and suites | The folder and suite hierarchy, plus per-folder statistics |
| Test collections | Reusable named case sets that drop into any execution |
| Manual executions | Build an execution from suites, collections or individual cases, then record per-case results |
| Releases | Create and manage releases, and attach or detach the launches that belong to them |
| Health and coverage | A composite health check, coverage gaps in both directions, case suggestions, feature scan, report export |
| External links | Attach and remove Jira or Linear tickets on a case |