Decision Log vs MCP Installer

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

D
Decision LogDeveloper Tools
Append-only decisions with provenance, supersession, retrieval, and audited MCP actions.37FairAuth: not declared
MCP Installer logoMCP InstallerDeveloper Tools · Local subprocess (stdio)An MCP server that installs other MCP servers for you.63GoodAuth: no auth required

Verdict: choose Decision Log for developer tools work; 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?

D
Choose Decision Log when

  • You need dedicated capabilities in the Developer Tools domain.
Explore Decision Log

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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
D
Decision Log
MCP Installer logoMCP Installer
CategoryDeveloper ToolsDeveloper Tools
Quality signal37/100 · Fair63/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—1,532
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listed2

Tools & capabilities

Decision Log 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 uvx
  • install_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.

Decision Log

No confirmed install command for Decision Log yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Installer

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

Frequently asked questions

Decision Log is categorized under Developer Tools and uses an install path we have not confirmed yet. MCP Installer belongs to Developer Tools and uses a local stdio subprocess. Pick Decision Log 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. Decision Log has no confirmed install command yet — follow its own setup instructions.

Decision Log 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 decision-log and anaisbetts-mcp-installer as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Decision Log 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.