Mdma vs MCP Server Azure Devo… — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mdma vs MCP Server Azure Devops
In-depth architectural comparison of the Mdma and MCP Server Azure Devops 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: 60/100 (Good) | Auth: No auth required
MCP Server Azure Devops
Version Control · Local stdio
Quality: 65/100 (Great) | Auth: other
Verdict Summary: Choose Mdma if you need specialized Version Control tools running via a local process. Choose MCP Server Azure Devops 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.
Azure DevOps integration for repository management, work items, and pipelines.
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 is categorized under Version Control and uses a local stdio subprocess. In contrast, MCP Server Azure Devops belongs to Version Control using local stdio subprocess. Select Mdma when you need capabilities focused on version control and MCP Server Azure Devops 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 Azure Devops Tools (30)
get_me
Get details of the authenticated user (id, displayName, email) (Azure DevOps Services only)
list_organizations
List all accessible organizations (Azure DevOps Services only)
list_projects
List all projects in an organization
get_project
Get details of a specific project
get_project_details
Get comprehensive details of a project including process, work item types, and teams
list_repositories
List all repositories in a project
get_repository
Get details of a specific repository
get_repository_details
Get detailed information about a repository including statistics and refs
get_file_content
Get content of a file or directory from a repository
get_repository_tree
List a repository's file tree from any path and depth
create_branch
Create a new branch from an existing one
create_commit
Commit multiple file changes to a branch using unified diffs or search/replace instructions