Superdocs vs MCP Installer
A side-by-side look at the Superdocs and MCP Installer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Superdocs for workplace & productivity work over a hosted endpoint; choose MCP Installer for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Superdocs when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SUPERDOCS_API_KEY.
Choose MCP Installer when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
install_repo_mcp_server, install_local_mcp_server.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Developer Tools |
| Quality signal | 41/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | SUPERDOCS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,532 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Superdocs | View MCP Installer |
Tools & capabilities
Superdocs tools
No tool names declared yet. Check the project README from the listing page.
MCP Installer tools 2
install_repo_mcp_serverInstall an MCP server via npx or uvxinstall_local_mcp_serverInstall an MCP server whose code is cloned locally on your computer
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.
Superdocs
{
"mcpServers": {
"superdocs": {
"url": "https://api.superdocs.app/v1/agents/signup"
}
}
}
MCP Installer
{
"mcpServers": {
"anaisbetts-mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
}
Frequently asked questions
Superdocs is categorized under Workplace & Productivity and uses a remote HTTP/SSE transport. MCP Installer belongs to Developer Tools and uses a local stdio subprocess. Pick Superdocs for workplace & productivity work and MCP Installer for developer tools.
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.
Superdocs is listed as freemium — a free tier with paid plans. Auth: api key required. MCP Installer is listed as free. Auth: no auth required. 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 superdocs and anaisbetts-mcp-installer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Superdocs has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. MCP Installer has 63/100 (Good) with 3 views, 0 installs and 1,532 GitHub stars.