Project Bourne vs MCP Installer
A side-by-side look at the Project Bourne 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 Project Bourne for developer tools work as a local process; 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 Project Bourne when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
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 | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed |
Tools & capabilities
Project Bourne 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.
Project Bourne
{
"mcpServers": {
"project-bourne": {
"command": "npx",
"args": [
"-y",
"@project-bourne/mcp@0.8.1"
]
}
}
}
MCP Installer
{
"mcpServers": {
"anaisbetts-mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
}
Frequently asked questions
Project Bourne is categorized under Developer Tools and uses a local stdio subprocess. MCP Installer belongs to Developer Tools and uses a local stdio subprocess. Pick Project Bourne for developer tools 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.
Project Bourne has no declared pricing — check the project's own site. 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 project-bourne and anaisbetts-mcp-installer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Project Bourne has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Installer has 63/100 (Good) with 3 views, 0 installs and 1,532 GitHub stars.
