Skip to main content
hc
Submit
mcpSource-backed

MCP Installer Server

MCP server that lets Claude install other MCP servers into Claude Desktop by writing MCP config entries for npm packages, uvx packages, or locally cloned Node-based MCP server projects.

by Anais Betts · submitted by oktofeesh1·added 2026-06-06·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/mcp-installer-server
Source URLs
https://raw.githubusercontent.com/anaisbetts/mcp-installer/main/README.md, https://github.com/anaisbetts/mcp-installer
Brand
MCP Installer
Brand domain
github.com
Safety notes
MCP Installer can write or update Claude Desktop MCP server configuration entries., The install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies., The install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files., Environment variables passed to the installer are written into the MCP configuration for the installed server., Treat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.
Privacy notes
MCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables., The server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs., Local project paths can reveal usernames, repository names, client names, or private workspace layout., Do not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.
Author
Anais Betts
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

5 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime3Permissions & scopes1Review & approval15 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes.

5 areas
  • SafetyExecution & processesMCP Installer can write or update Claude Desktop MCP server configuration entries.
  • SafetyExecution & processesThe install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies.
  • SafetyLocal filesThe install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files.
  • SafetyExecution & processesEnvironment variables passed to the installer are written into the MCP configuration for the installed server.
  • SafetyPermissions & scopesTreat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.
  • PrivacyCredentials & tokensMCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables.
  • PrivacyData retentionThe server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs.
  • PrivacyLocal filesLocal project paths can reveal usernames, repository names, client names, or private workspace layout.
  • PrivacyCredentials & tokensDo not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.

Disclosure: MIT-licensed open-source MCP utility. It changes local MCP configuration and can add package execution commands; it should be used only with reviewed packages and least-privilege credentials.

Safety notes

  • MCP Installer can write or update Claude Desktop MCP server configuration entries.
  • The install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies.
  • The install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files.
  • Environment variables passed to the installer are written into the MCP configuration for the installed server.
  • Treat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.

Privacy notes

  • MCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables.
  • The server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs.
  • Local project paths can reveal usernames, repository names, client names, or private workspace layout.
  • Do not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.

Prerequisites

  • Claude Desktop or another MCP client that can run stdio Node MCP servers.
  • Node.js and npx available for npm-hosted MCP servers.
  • uvx available before installing Python MCP servers through the uvx path.
  • Package names, local paths, args, and environment variables reviewed before asking Claude to install anything.
  • Permission to modify the Claude Desktop MCP configuration file on the host machine.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
MIT-licensed open-source MCP utility. It changes local MCP configuration and can add package execution commands; it should be used only with reviewed packages and least-privilege credentials.
Full copyable content
{
  "mcpServers": {
    "mcp-installer": {
      "command": "npx",
      "args": ["@anaisbetts/mcp-installer"]
    }
  }
}

About this resource

Content

MCP Installer is an MCP server that helps Claude add other MCP servers to Claude Desktop configuration. It exposes tools for installing package-based MCP servers through npx or uvx and for adding locally cloned Node MCP server projects after running npm install.

This is most useful as an administrative helper when you already know which MCP server should be installed and want Claude to update the configuration for you. Because it can write config entries and store environment variables, treat every tool call as a local configuration change that needs human review.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, NPM metadata, license, package metadata, and TypeScript source for current tool names, install behavior, and config-write paths.

Features

  • Run as a stdio MCP server with npx @anaisbetts/mcp-installer.
  • Install npm-hosted MCP servers by writing npx commands into Claude Desktop MCP configuration.
  • Install uvx-based MCP servers when a package is not found on npm and uvx is available.
  • Add command arguments to installed MCP server configs.
  • Add environment variables to installed MCP server configs.
  • Install locally cloned Node MCP servers by running npm install and wiring discovered package bins or main files.
  • Expose separate tools for package-based and local-path installs.

Installation

Add MCP Installer to Claude Desktop after reviewing the source and package:

{
  "mcpServers": {
    "mcp-installer": {
      "command": "npx",
      "args": ["@anaisbetts/mcp-installer"]
    }
  }
}

Restart the MCP client after adding the server. Before asking Claude to install another MCP server, confirm the exact package name, source repository, command arguments, environment variables, and whether the target server should run with npx, uvx, or a local Node entry point.

Use Cases

  • Add a reviewed npm MCP package to Claude Desktop without editing JSON by hand.
  • Add a reviewed uvx MCP package after confirming uv is installed.
  • Configure a locally cloned Node MCP server for testing.
  • Ask Claude to prepare a draft MCP config entry while you inspect the package and environment variables.
  • Standardize local MCP setup instructions for a team that still reviews each server before use.

Safety and Privacy

MCP Installer can modify local MCP configuration, so it should not be treated as a passive catalog tool. Review package names for typosquatting, inspect source repositories, pin versions where possible, and avoid installing untrusted packages just because the model suggested them.

Be especially careful with environment variables. Values passed to the installer are written into MCP config for the installed server and may include API keys or tokens. Local paths can also reveal private machine or project details. Keep config backups, review diffs manually, and remove unwanted entries before restarting the MCP client.

Duplicate Check

No anaisbetts/mcp-installer, @anaisbetts/mcp-installer, MCP Installer Server, MCP server installer, or matching source URL entry was found in content/mcp or README.md.

#installer#configuration#desktop#npm#developer-tools

Source citations

Add this badge to your README

Show that MCP Installer Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/mcp-installer-server.svg)](https://heyclau.de/entry/mcp/mcp-installer-server)

How it compares

MCP Installer Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
MCP Installer Server

MCP server that lets Claude install other MCP servers into Claude Desktop by writing MCP config entries for npm packages, uvx packages, or locally cloned Node-based MCP server projects.

Open dossier
Agentset logoAgentset MCP Server

Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.

Open dossier
CodeDB logoCodeDB MCP Server

Code intelligence MCP server with a Zig core for local project indexing, structural outlines, symbol lookup, search, dependency graphs, snapshots, remote public-repo queries, and fallback edits.

Open dossier
Webiny logoWebiny MCP Server

Webiny's MCP server for exposing Webiny-specific skills and development instructions to Claude, Cursor, Copilot, Windsurf, opencode, and other AI coding agents over stdio.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand—Agentset logoAgentsetCodeDB logoCodeDBWebiny logoWebiny
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorAnais BettsAgentsetjustrachWebiny Ltd
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓MCP Installer can write or update Claude Desktop MCP server configuration entries. The install_repo_mcp_server tool can add npx or uvx based MCP server commands from package names the model supplies. The install_local_mcp_server tool can run npm install in a local project with a package.json and configure Node to execute discovered package bins or main files. Environment variables passed to the installer are written into the MCP configuration for the installed server. Treat this as an administrative helper; review every package, version, local path, arg, and environment value before approving a tool call.✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.✓CodeDB indexes local projects and exposes file tree, outline, search, symbol, caller, dependency, read, snapshot, project, and context tools to the MCP client. CodeDB's `codedb_edit` tool exists as a fallback editing tool and can create, replace, insert, delete, or modify files when used by a client without native edit tooling. The npm package runs a postinstall step that downloads a native binary from GitHub Releases; review package and release provenance in environments that restrict native binaries. Remote repo queries use the public `api.wiki.codes` service and should be treated as network access outside the local repository. The upstream README marks the project as alpha software, with parser coverage and snapshot formats still stabilizing.✓Webiny MCP is a guidance and skill-loading server; it does not directly manage a Webiny CMS deployment or execute Webiny admin actions. The configure command can update supported agent configuration, so review generated MCP config changes before committing or sharing them. The --skills and --additional-skills flags make the server recursively discover SKILL.md files from local directories; point them only at trusted project guidance. Agent-loaded skills can strongly steer code changes, architecture decisions, and generated commands; review outputs before applying them to production Webiny projects.
Privacy notes✓MCP configuration files can contain API keys, tokens, local paths, package names, arguments, and environment variables. The server reads and writes the user's Claude Desktop MCP config and may reveal existing MCP server names or config structure through tool results or logs. Local project paths can reveal usernames, repository names, client names, or private workspace layout. Do not ask the installer to write real secrets until you understand where the MCP client stores them and who can read the config file.✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.✓Local indexes, snapshots, file trees, symbol names, dependency graphs, snippets, read results, and search results can reveal proprietary code structure and implementation details. Upstream documents sensitive-file blocking for patterns such as environment files, credentials, and keys, but users should still review ignore rules and avoid indexing secret-heavy directories. CodeDB writes telemetry to `~/.codedb/telemetry.ndjson` unless `CODEDB_NO_TELEMETRY=1` is set, then syncs aggregate tool counts, latency, startup, file count, line count, language, version, and platform data on MCP session close. Upstream telemetry docs state that source code, file contents, file paths, and search queries are not collected. Remote public-repo queries and local MCP responses may still be logged by MCP clients, model providers, and terminal history.✓Skill files can contain internal coding conventions, project architecture, extension patterns, package notes, and proprietary implementation guidance. Loaded skill content may be sent to MCP clients, model providers, chat transcripts, and logs when an agent requests it. Custom skill directories can reveal local repository structure and file paths through tool output or error messages. Keep credentials, customer data, private deployment details, and unpublished roadmap notes out of SKILL.md files exposed through the MCP server.
Prerequisites
  • Claude Desktop or another MCP client that can run stdio Node MCP servers.
  • Node.js and npx available for npm-hosted MCP servers.
  • uvx available before installing Python MCP servers through the uvx path.
  • Package names, local paths, args, and environment variables reviewed before asking Claude to install anything.
  • Agentset account or self-hosted Agentset deployment with a populated namespace.
  • Agentset API key with access to the namespace Claude should query.
  • Node.js 18.17 or newer for running the `@agentset/mcp` package.
  • Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
  • macOS or Linux on x64 or arm64 for the published native binary launcher.
  • Node.js 18 or newer when using the `codedeebee` npm launcher.
  • A local project directory that the MCP client exposes through roots or launches from.
  • Review of which local repositories, file types, generated artifacts, and secrets patterns may be indexed.
  • Node.js and npx available for running the @webiny/mcp package.
  • A Webiny project or Webiny-related repository where the agent should use Webiny guidance.
  • Review of the built-in skills and any custom SKILL.md directories before exposing them to a model.
  • Agreement on whether project conventions, extension architecture, package internals, or private implementation notes may be sent to the MCP client and model provider.
Install
Run `npx @anaisbetts/mcp-installer` from Claude Desktop after reviewing the server source and package behavior.
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.
npx -y codedeebee mcp
npx @webiny/mcp serve
Config
{
  "mcpServers": {
    "mcp-installer": {
      "command": "npx",
      "args": ["@anaisbetts/mcp-installer"]
    }
  }
}
{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx"
      }
    }
  }
}
{
  "mcpServers": {
    "codedb": {
      "command": "npx",
      "args": [
        "-y",
        "codedeebee",
        "mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "webiny": {
      "command": "npx",
      "args": [
        "@webiny/mcp",
        "serve"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Agent Skills in Claude Agent SDK Applications

Use Agent Skills in the Claude Agent SDK: filesystem discovery via settingSources, the skills option to enable or filter, and tool access.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Adding Plugin Install Hints to Developer CLIs

Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.