What is the key difference between Mdma and Repowise?

Mdma belongs to the Version Control category with local stdio execution, while Repowise belongs to the Version Control category with local stdio execution.

How do I install Mdma or Repowise in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mdma and Repowise free or paid?

Mdma operates under a Free / Open Source model (No auth required). Repowise operates under a Freemium model (No auth required).

Which MCP server has more tools and community activity?

Mdma lists 8 tools with 3 views and 64 GitHub stars. Repowise lists 6 tools with 2 views and 6,226 GitHub stars.

Can I use both Mdma and Repowise together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Mdma vs Repowise

In-depth architectural comparison of the Mdma and Repowise MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Mdma

Version Control · Local stdio

Quality: 65/100 (Great) | Auth: No auth required

Repowise

Version Control · Local stdio

Quality: 64/100 (Good) | Auth: No auth required

Verdict Summary: Choose Mdma if you need specialized Version Control tools running via a local process. Choose Repowise if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mdma when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: get-spec, get-prompt, list-prompt-variants.

Explore Mdma Details

Choose Repowise when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: Nine task-shaped MCP tools across 15 programming languages, Precomputes answers to common codebase questions with zero LLM calls, Defect-risk scoring validated on multiple repos and languages.

Explore Repowise Details

Feature & Specification Comparison

Specification	Mdma MobileReality Version Control	Repowise repowise-dev Version Control
Summary	MCP server for MDMA (interactive Markdown applications with mounted components). Exposes the MDMA spec, authoring prompts, package metadata, and live docs to AI assistants. Tools: get-spec, get-prompt, build-system-prompt, validate-prompt, list-packages, list-docs, get-doc. Install: npx @mobile-reality/mdma-mcp.	Codebase intelligence for AI coding agents. Indexes a repo into a dependency graph, git history, defect-risk code health, auto-generated docs, and architectural decisions, served as 9 task-shaped MCP tools across 15 languages. Runs 100% local; hosted option available.
Category & Scope

Tools & Capabilities Breakdown

Mdma Tools (8)

get-spec

Returns the full MDMA specification: component types, JSON schemas, binding syntax, and authoring rules

get-prompt

Returns a named prompt (`mdma-author`, `mdma-reviewer`, or `mdma-fixer`). For `mdma-author`, accepts an optional `variantId` (e.g. `google/gemini-2.5-pro`) to return the model-optimised variant

list-prompt-variants

Returns all available `MDMA_AUTHOR` prompt variants (id, label, description) — 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 — returns warnings, suggestions, and constraint reference

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Mdma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mobilereality-mdma": {
      "command": "npx",
      "args": [
        "-y",
        "@mobile-reality/mdma-cli"
      ]
    }
  }
}

Repowise Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "repowise-dev-repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Frequently Asked Questions

Mdma is categorized under Version Control and uses a local stdio subprocess. In contrast, Repowise belongs to Version Control using local stdio subprocess. Select Mdma when you need capabilities focused on version control and Repowise when you require tools for version control.

More alternatives to Mdma More alternatives to Repowise Version Control category hub