Git Context MCP vs Mdma — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Git Context MCP vs Mdma
In-depth architectural comparison of the Git Context MCP and Mdma 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
Git Context MCP
Version Control · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Mdma
Version Control · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Git Context MCP if you need specialized Version Control tools running via a local process. Choose Mdma 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 Git Context MCP 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).
Local MCP server that provides structured Git repository analysis (project status, recent activity, code map, and risk hotspots) for AI coding agents.
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.
Category & Scope
Tools & Capabilities Breakdown
Git Context MCP Tools (5)
project_status
Repository state awareness
code_map
Structural understanding
recent_activity
Development churn analysis
work_summary
High-level progress overview
risk_scan
Maintenance risk detection
Mdma Tools (8)
get-spec
Returns the full MDMA specification: component types, JSON schemas, binding syntax, and authoring rules
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).
Git Context MCP is categorized under Version Control and uses a local stdio subprocess. In contrast, Mdma belongs to Version Control using local stdio subprocess. Select Git Context MCP when you need capabilities focused on version control and Mdma when you require tools for version control.
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
list-packages
Returns all MDMA packages with purpose, install command, and usage example
list-docs
Returns the catalog of MDMA documentation files (path, title, description) available for fetching from the public GitHub repo
get-doc
Fetches the latest version of an MDMA documentation file from `raw.githubusercontent.com/MobileReality/mdma`. Supports optional `ref` (branch/tag/SHA, defaults to `main`)