MDMA
About
Interactive documents from Markdown. Extends MD with forms, approvals, webhooks, and more — built for next gen apps
Details
- Author
- MobileReality
- GitHub stars
- 34
- Downloads
- 347
- Categories
- Other, AI
Jump to
- Provides full MDMA specification via get-spec tool.
- Returns authoring, reviewing, and fixing prompts via get-prompt.
- Lists available prompt variants for model-optimised prompts.
- Generates custom MDMA prompts from structured input.
- Validates custom prompts against MDMA conventions.
- Lists MDMA npm packages with install commands and examples.
- Retrieves up-to-date documentation from the public GitHub repository.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MDMACommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Add the following to your MCP client configuration:
{
"mcpServers": {
"mdma": { "command": "npx", "args": ["@mobile-reality/mdma-mcp"] }
}
}
No further explicit usage instructions are provided.
get-spec
Returns the full MDMA specification: component types, schemas (as JSON Schema), binding syntax, and authoring rules
get-prompt
Returns a named MDMA prompt (mdma-author, mdma-reviewer, or mdma-fixer). For mdma-author, pass an optional variantId (e.g. "google/gemini-2.5-pro") to get the model-optimised variant — use list-prompt-variants to see all available ids.
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 prompt.
build-system-prompt
Generates a custom MDMA prompt from structured input (domain, components, fields, steps). Returns only the custom prompt part — use buildSystemPrompt({ customPrompt }) in code to combine it with the base MDMA spec.
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 you can pass to get-doc.
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 text. Allowed paths: any entry from list-docs, plus any *.md file under "docs/" or "blueprints/". Defaults to the "main" branch.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mdma": {
"mdma": {
"command": "npx",
"args": [
"@mobile-reality/mdma-mcp"
]
}
}
}
}
McpServers
{
"mdma": {
"command": "npx",
"args": [
"@mobile-reality/mdma-mcp"
]
}
}
@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.
Tools
| Tool | Purpose |
|------|---------|
| get-spec | Returns the full MDMA specification (component types, JSON schemas, binding syntax, authoring rules). |
| get-prompt | Returns a named MDMA prompt (mdma-author, mdma-reviewer, mdma-fixer). For mdma-author, accepts an optional variantId (e.g. google/gemini-2.5-pro) to return the model-optimised variant — use list-prompt-variants to see all available ids. |
| list-prompt-variants | Returns all available MDMA_AUTHOR prompt variants (id, label, description) without the prompt content. Use the id with get-prompt to fetch the model-optimised prompt. |
| build-system-prompt | Generates a custom MDMA prompt from structured input (domain, components, fields, steps, business rules). |
| validate-prompt | Validates a custom prompt against MDMA conventions. |
| list-packages | Returns all MDMA npm packages with purpose, install command, usage example, and category. |
| list-docs | Returns the catalog of MDMA documentation files available for fetching from the public GitHub repo. |
| get-doc | Fetches the latest version of a doc from raw.githubusercontent.com/MobileReality/mdma. Supports an optional ref (branch, tag, or SHA). |
Install
{
"mcpServers": {
"mdma": { "command": "npx", "args": ["@mobile-reality/mdma-mcp"] }
}
}
Distribution venues
Places where MDMA's MCP server is published or should be published. Each venue has its own submission / update flow — when releasing a new version, check each one.
| Venue | Identifier / URL | Notes |
|-------|------------------|-------|
| npm | @mobile-reality/mdma-mcp | Publish via pnpm publish --access public --no-git-checks. |
| Official MCP Registry | io.github.MobileReality/mdma | Published via mcp-publisher. Namespace is case-sensitive — must match GitHub's canonical capitalization. |
| Glama | MobileReality/mdma | Quality + Security scores auto-evaluated periodically. Docker build config lives in the Glama admin page — re-deploy + re-release when bumping. |
| awesome-mcp-servers | punkpeye/awesome-mcp-servers | Entry sits under Developer Tools alphabetically. |
| Smithery Skills | mobilereality/mdma | Skills surface — not the MCP surface (Smithery's MCP flow is HTTP-only, unusable for stdio). |
| MCP.so | mcp.so/server/mdma | Self-serve listing. Manual edit of Title / Description / Tags / Content on the Edit Server page. No versioned republish needed — just refresh the description if the tool set changes. |
| MCPB Desktop Extensions | Anthropic intake form | Partner queue at Anthropic. Bundle built locally; not shipped in this repo. |
Release checklist — when bumping the version
Use this checklist every time you publish a new version (0.2.4 → 0.2.5, etc.).
1. Bump + test
- [ ] Update version in package.json.
- [ ] Update version string in src/index.ts (the McpServer({ version: ... }) call).
- [ ] Update top-level version and packages[0].version in server.json.
- [ ] Update top-level version and packages[0].version in manifest.json.
- [ ] Add a changeset: pnpm changeset at repo root.
- [ ] Run pnpm build && pnpm test && pnpm typecheck in this package.
2. Publish to npm
- [ ] pnpm publish --access public --no-git-checks from this directory.
- [ ] Verify: npm view @mobile-reality/mdma-mcp version mcpName — both should match.
3. Publish to the MCP Registry
- [ ] Ensure mcp-publisher is authenticated: mcp-publisher login github (re-auth if tokens expired).
- [ ] mcp-publisher publish from this directory.
- [ ] Verify: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.MobileReality/mdma" shows the new version.
> Do not commit .mcpregistry_github_token / .mcpregistry_registry_token — they are in .gitignore. GitHub's push protection will block the push anyway; this is a belt-and-braces reminder.
4. Tag the release
git tag '@mobile-reality/mdma-mcp@<version>'
git push origin '@mobile-reality/mdma-mcp@<version>'
5. Build a fresh MCPB bundle (only if submitting a Desktop Extension update)
pnpm's virtual store (.pnpm/) gets stripped by mcpb pack, so you must build the bundle from a clean npm-installed directory or transitive deps (e.g. ajv) will be missing.
Output: <name>-<version>.mcpb. Test-install in Claude Desktop, then attach as a GitHub Release asset.
6. Glama — if tool descriptions or Dockerfile config changed
- [ ] If you added / renamed / changed descriptions of tools: Glama's Quality score will re-evaluate on its next periodic scan. No manual trigger.
- [ ] If packages[0].version bumped: go to the Glama admin page → update Build steps (npm install -g @mobile-reality/mdma-mcp@<version>) → Deploy → Make Release.
7. Downstream awareness
- [ ] Update the MCP tools table in the root README.md if tools were added / renamed / removed.
- [ ] Update this package's own tools table (above) the same way.
- [ ] If tools changed: refresh the manual listing on MCP.so (Edit Server → Description / Content).
- [ ] If a breaking change: note in the changeset; update consumers of createMdmaMcpServer() if any.
Troubleshooting
MCP Registry publish fails with 403 Forbidden
If the error says permission to publish: io.github.gitsad/, io.github.MobileReality/. Attempting to publish: io.github.mobilereality/mdma (lowercase mismatch): the registry is case-sensitive and your mcpName / server.json name must exactly match GitHub's canonical MobileReality capitalization. Fix both files and republish to npm (versions on npm are immutable).
If the error says permission to publish: io.github.gitsad/ (org missing entirely): your MobileReality GitHub membership is private. Make it public at <https://github.com/orgs/MobileReality/people>, then mcp-publisher logout && mcp-publisher login github to refresh the JWT.
MCPB .mcpb crashes on install in Claude Desktop
Usually "missing module" errors in the Developer tab logs. Cause: pnpm's nested .pnpm/ virtual store got stripped at pack time, so transitive deps are missing. Fix: build the bundle from a clean npm-installed directory (see step 5 above). Do not run mcpb pack directly against packages/mcp/node_modules.
Secrets leaking into the bundle
mcpb pack does not respect .gitignore. Any .mcpregistry__token file next to the manifest at pack time gets zipped into the .mcpb. Always delete these before packing, and prefer the /tmp/mcpb-build workflow above which has no tokens in its directory.
Files in this package
| File | Purpose | Tracked? |
|------|---------|----------|
| src/ | TypeScript source for the server + tools. | ✅ |
| dist/ | Compiled JavaScript. | ❌ (gitignored) |
| tests/ | Vitest unit tests for tool logic. | ✅ |
| package.json | Contains the mcpName field required by the MCP Registry. | ✅ |
| server.json | MCP Registry manifest consumed by mcp-publisher. | ✅ |
| manifest.json | MCPB (Desktop Extension) manifest. | ✅ |
| icon.png | 1024×1024 square icon for the MCPB submission. | ✅ |
| screenshots/ | Screenshots bundled with the MCPB for the Claude Desktop install dialog. | ✅ |
| *.mcpb | Built Desktop Extension bundle (build artifact). | ❌ (gitignored) |
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.




