Mdma vs ToughTongue AI
A side-by-side look at the Mdma and ToughTongue AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mdma for conversational ai work as a local process; choose ToughTongue AI for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mdma when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get-spec, get-prompt, list-prompt-variants.
Choose ToughTongue AI when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 59/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 71 | 6 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Mdma | View ToughTongue AI |
Tools & capabilities
Mdma tools 8
get-specReturns the full MDMA specification: component types, JSON schemas, binding syntax, external data sources (`{ source, params }` refs and the `rows` / `series` / `options` kinds), and authoring rulesget-promptReturns 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 variantlist-prompt-variantsReturns all available `MDMA_AUTHOR` prompt variants (id, label, description) — use the id with `get-prompt` to fetch the model-optimised promptbuild-system-promptGenerates a custom MDMA prompt from structured input (domain, components, fields, steps, business rules). Pass `dataSources` (an external data-source catalog of `rows` / `series` / `options` entries) to get the full system prompt with the catalog and the rule to reference data via `{ source, params…validate-promptValidates a custom prompt against MDMA conventions — returns warnings, suggestions, and constraint referencelist-packagesReturns all MDMA packages with purpose, install command, and usage examplelist-docsReturns the catalog of MDMA documentation files (path, title, description) available for fetching from the public GitHub repoget-docFetches the latest version of an MDMA documentation file from `raw.githubusercontent.com/MobileReality/mdma`. Supports optional `ref` (branch/tag/SHA, defaults to `main`)
ToughTongue AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mdma
{
"mcpServers": {
"mdma": {
"command": "npx",
"args": [
"-y",
"@mobile-reality/mdma-cli"
]
}
}
}
ToughTongue AI
{
"mcpServers": {
"toughtongue-ai": {
"command": "npx",
"args": [
"-y",
"plugins"
]
}
}
}
Frequently asked questions
Mdma is categorized under Conversational AI and uses a local stdio subprocess. ToughTongue AI belongs to Conversational AI and uses a local stdio subprocess. Pick Mdma for conversational ai work and ToughTongue AI for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mdma has no declared pricing — check the project's own site. ToughTongue AI has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mdma and toughtongue-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mdma has a quality signal of 59/100 (Good) with 2 views, 0 installs and 71 GitHub stars. ToughTongue AI has 47/100 (Fair) with 3 views, 0 installs and 6 GitHub stars.