Mdma
Expose MDMA specs, prompts, docs, and package metadata to your agent so mobile-related work stays aligned with the MDMA toolchain instead of guessing APIs from stale README scraps.
Overview
MDMA MCP is a MCP server for the Build phase that exposes MDMA spec, prompts, docs, and package metadata to your AI assistant.
What is this MCP server?
- stdio npm package @mobile-reality/mdma-mcp v0.2.4 for MCP hosts
- Surfaces MDMA spec, prompts, documentation, and package metadata to assistants
- Keeps agent answers grounded in upstream MDMA sources during implementation
- Lightweight integration for teams already on the MobileReality MDMA ecosystem
- Reduces context switching between repo docs and the chat window
- Server version 0.2.4
- npm identifier @mobile-reality/mdma-mcp
- Repository subfolder packages/mcp on github.com/MobileReality/mdma
Community signal: 18 GitHub stars.
What problem does it solve?
Builders on MDMA lose time when the agent lacks live spec and package context and invents APIs that do not match the real toolchain.
Who is it for?
Developers using MobileReality MDMA who want MCP-grounded spec and package lookups while coding with Claude Code or Cursor.
Skip if: Teams with no MDMA dependency who only need generic npm or GitHub MCP servers.
What do I get? / Deliverables
After adding mdma-mcp, your agent can pull authoritative MDMA metadata and docs so implementation and scoping answers stay accurate.
- Agent-accessible MDMA spec, prompts, and docs
- Accurate package metadata lookups during implementation
- Less manual doc hunting in the MDMA monorepo
Recommended MCP Servers
Journey fit
Shelved under Build/agent-tooling because the server’s job is feeding structured MDMA knowledge into the agent while you implement or extend mobile-oriented packages. Agent-tooling fits best: it is an MCP bridge for context and metadata, not a ship-time test runner or a launch distribution tool.
How it compares
MDMA metadata and docs MCP, not mobile device automation or a WordPress site editor.
Common Questions / FAQ
Who is mdma-mcp for?
It is for builders and maintainers in the MDMA ecosystem who want their agent to read spec, prompts, docs, and package metadata through MCP.
When should I use mdma-mcp?
Use it during Build and Validate when you are integrating MDMA packages or scoping features and need the agent tied to official MDMA sources.
How do I add mdma-mcp to my agent?
Install @mobile-reality/mdma-mcp from npm, configure a stdio MCP server in your agent host, and call the exposed tools for spec and metadata.