Mdma vs MCP Server Github Act… — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mdma vs MCP Server Github Actions
In-depth architectural comparison of the Mdma and MCP Server Github Actions 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: 63/100 (Good) | Auth: No auth required
MCP Server Github Actions
Version Control · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Verdict Summary: Choose Mdma if you need specialized Version Control tools running via a local process. Choose MCP Server Github Actions 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).
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.
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 is categorized under Version Control and uses a local stdio subprocess. In contrast, MCP Server Github Actions belongs to Version Control using local stdio subprocess. Select Mdma when you need capabilities focused on version control and MCP Server Github Actions when you require tools for version control.
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`)
MCP Server Github Actions Tools (9)
list_workflows
List all workflow files in a GitHub repository.
list_runs
List workflow runs for a repository. Optionally filter by workflow or status.
get_run
Get details of a specific workflow run.
get_run_logs
Get logs URL for a workflow run. GitHub returns a redirect to a zip file.
rerun_workflow
Re-run a complete workflow run.
rerun_failed_jobs
Re-run only the failed jobs from a workflow run.
cancel_run
Cancel a workflow run that is in progress or queued.
list_artifacts
List artifacts produced by a workflow run.
trigger_workflow
Trigger a workflow run via workflow_dispatch. Requires a workflow with workflow_dispatch enabled.
MCP Server Github Actions vs Github Enterprise MCP