A side-by-side look at the MCP API Translator and Openapi To MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP API Translator for developer tools work as a local process; choose Openapi To MCP for developer tools. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | M MCP API Translator | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP API Translator | View Openapi To MCP |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"mcp-api-translator": {
"command": "npx",
"args": [
"-y",
"mcp-api-translator"
]
}
}
}
No confirmed install command for Openapi To MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.