# @mobile-reality/mdma-mcp

MCP (Model Context Protocol) server for MDMA. Exposes the MDMA spec, authoring prompts, package metadata, and live GitHub documentation to AI assistants.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.3.1
- **Author:** io.github.MobileReality
- **License:** Unknown
- **npm:** @mobile-reality/mdma-mcp
- **Source:** https://github.com/MobileReality/mdma
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-21T07:32:28.715Z
- **Version scanned:** 0.3.1
- **CVEs:** none found by OSV at scan time
**Findings**
- injection-shaped content (note) in the `build-system-prompt` tool: References the system prompt

## Tools

8 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get-spec` — Returns the full MDMA specification: component types, schemas (as JSON Schema), binding syntax, external data sources ({ source, params } refs, the DataSourceDe
- `get-prompt` — Returns a named MDMA prompt (mdma-author, mdma-reviewer, or mdma-fixer). For mdma-author, pass an optional variantId (e.g. "anthropic/sonnet-5.5", "openai/gpt-6
- `list-prompt-variants` — Returns all available MDMA_AUTHOR prompt variants with their id, label, and description. Pass the id to get-prompt as variantId to retrieve the model-optimised 
- `build-system-prompt` — Generates a custom MDMA prompt from structured input (domain, components, fields, steps). Returns only the custom prompt part — use buildSystemPrompt({ customPr
- `validate-prompt` — Validates a custom prompt against MDMA conventions. Returns warnings for anti-patterns and suggestions for improvements.
- `list-packages` — Returns all MDMA npm packages with their purpose, install command, usage example, and category
- `list-docs` — Returns the catalog of MDMA documentation files available for fetching from the public GitHub repo (path, title, description). Use this to discover what docs yo
- `get-doc` — Fetches the latest version of an MDMA documentation file from the public GitHub repo (raw.githubusercontent.com/MobileReality/mdma) and returns its contents as 

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mdma\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mobile-reality/mdma-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mobile-reality%2Fmdma-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40mobile-reality%2Fmdma-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mobile-reality%2Fmdma-mcp
- HTML page: https://forgeregistry.com/registry/%40mobile-reality%2Fmdma-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.