Skip to main content
Glama
Daniel Rosehill's MCP Installer

Daniel Rosehill's MCP Installer

Daniel Rosehill's MCP Installer

A personal MCP server that manages installation of my MCP servers across machines. Perfect for quickly setting up all my MCPs on a new laptop or workstation.

What This Does

This is an MCP server that:

  1. Fetches my MCP registry from a GitHub repo (so I can update the list without republishing to npm)

  2. Installs MCPs to Claude Code, Cursor, VS Code, and other MCP-compatible clients

  3. Prompts for secrets when MCPs require API keys

Related MCP server: Coyote MCP Server

Quick Start

Add to your Claude Code config (~/.claude/settings.json):

{
  "mcpServers": {
    "my-mcps": {
      "command": "npx",
      "args": ["-y", "daniel-rosehill-mcps"]
    }
  }
}

Then in Claude Code, use the tools:

# See all available MCPs
list_mcps

# Install all essential MCPs
install_all essential_only=true

# Install a specific MCP
install_mcp mcp_id="gemini_transcription" secrets={"GOOGLE_API_KEY": "your-key"}

Available Tools

Tool

Description

list_mcps

List all MCPs in the registry (filter by category, essential)

list_installed

Show installed MCPs for a client

install_mcp

Install one MCP to a client

install_all

Install all/essential MCPs to a client

sync_registry

Refresh registry from GitHub

uninstall_mcp

Remove an MCP from a client

get_info

Show installer info and supported clients

Supported Clients

  • Claude Code: ~/.claude/settings.json

  • Cursor: ~/.cursor/mcp.json

  • VS Code: ~/.config/Code/mcp.json

Registry Format

The MCP registry is a JSON file hosted on GitHub. Example entry:

{
  "id": "gemini_transcription",
  "name": "Gemini Transcription",
  "description": "Audio transcription via Gemini",
  "category": "Audio",
  "essential": true,
  "type": "npm",
  "config": {
    "package": "gemini-transcription-mcp"
  },
  "secrets": [
    { "key": "GOOGLE_API_KEY", "description": "Google AI API key", "required": true }
  ]
}

MCP Types

  • npm: Installed via npx -y package-name

  • streamable-http: Modern HTTP streaming transport (recommended for remote servers)

  • sse: Server-Sent Events endpoint (legacy)

  • http: Standard HTTP endpoint

  • docker: Docker container

Environment Variables

Variable

Description

Default

MCP_REGISTRY_URL

Override registry URL

GitHub raw URL

MCP_CACHE_DIR

Cache directory

~/.cache/mcp-installer

MCP_CACHE_TTL

Cache TTL in seconds

3600

License

MIT

Available Tools

7 tools
get_infoB

Get information about the installer, registry URL, cache location, and supported clients.

Inputs: no named parameters.

install_allA

Install all MCPs (or just essential ones) to a client. Skips MCPs that need secrets unless provided.

Inputs: client, essential_only, skip_existing, secrets.

install_mcpB

Install a single MCP to a client. If secrets are required, they must be provided.

Inputs: mcp_id (required), client, secrets, force.

list_installedB

Show what MCPs are already installed in a specific client or all clients.

Inputs: client.

list_mcpsB

List all available MCPs in the registry. Can filter by category or show only essential MCPs.

Inputs: category, essential_only.

sync_registryA

Update the local registry cache from GitHub. Use this to get the latest MCP list.

Inputs: force.

uninstall_mcpC

Remove an MCP from a client configuration.

Inputs: mcp_id (required), client.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_info provides metadata, install_all and install_mcp handle bulk vs. single installations, list_installed and list_mcps show different data sources, sync_registry updates the cache, and uninstall_mcp removes MCPs. The descriptions make it easy to differentiate between similar-sounding tools like list_installed (client-side) and list_mcps (registry).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as get_info, install_all, list_installed, and sync_registry. There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 7 tools, the server is well-scoped for an MCP installer, covering core operations like installation, listing, syncing, and uninstallation without being too sparse or bloated. Each tool serves a clear, necessary function in the workflow, and the count aligns with typical server sizes of 3-15 tools.

    Completeness5/5

    The tool set provides complete coverage for the MCP installer domain, including metadata retrieval (get_info), installation (install_all, install_mcp), inventory management (list_installed, list_mcps), updates (sync_registry), and removal (uninstall_mcp). There are no obvious gaps, as all essential CRUD-like operations for managing MCP installations are present.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides easy setup and configuration for multiple AI development environments including Claude Desktop, VS Code, and Windsurf. Offers automated installation scripts and manual configuration options for seamless integration across different MCP-compatible clients.
      1
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Creates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.
      11
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A robust MCP server with tools to search, install, configure, repair, and uninstall MCP servers, automating setup and maintenance across multiple AI and developer tools.
      4
      17
      MIT