MCP Installer vs Dossier

A side-by-side look at the MCP Installer and Dossier MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Installer logoMCP InstallerDeveloper Tools · Local subprocess (stdio)An MCP server that installs other MCP servers for you.63GoodAuth: no auth requiredDossier logoDossierDeveloper Tools · Local subprocess (stdio)MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers48FairAuth: not declared

Verdict: choose MCP Installer for developer tools work as a local process; choose Dossier 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?

MCP Installer logoChoose 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.
Explore MCP Installer

Dossier logoChoose Dossier when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Dossier

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Installer logoMCP InstallerDossier logoDossier
CategoryDeveloper ToolsDeveloper Tools
Quality signal63/100 · Good48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,53210
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools2Not listed

Tools & capabilities

MCP Installer tools 2

  • install_repo_mcp_serverInstall an MCP server via npx or uvx
  • install_local_mcp_serverInstall an MCP server whose code is cloned locally on your computer

Dossier 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.

MCP Installer

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "anaisbetts-mcp-installer": {
      "command": "npx",
      "args": [
        "@anaisbetts/mcp-installer"
      ]
    }
  }
}

Dossier

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dossier": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-dossier/cli"
      ]
    }
  }
}

Frequently asked questions

MCP Installer is categorized under Developer Tools and uses a local stdio subprocess. Dossier belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Installer for developer tools work and Dossier 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.

MCP Installer is listed as free. Auth: no auth required. Dossier 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 anaisbetts-mcp-installer and dossier as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Installer has a quality signal of 63/100 (Good) with 3 views, 0 installs and 1,532 GitHub stars. Dossier has 48/100 (Fair) with 0 views, 0 installs and 10 GitHub stars.