What is Mcp Hosts Installer

mcp-hosts-installer is a Model Context Protocol (MCP) server designed to install and configure other MCP servers across different hosts such as Cursor, Claude, and VsCode IDE.

Use cases

Use cases for mcp-hosts-installer include setting up development environments quickly, managing multiple MCP server installations across different projects, and simplifying the process of integrating various MCP servers into existing workflows.

How to use

To use mcp-hosts-installer, you need to install it by adding the appropriate configuration to your IDE’s configuration file. For Claude, modify ‘claude_desktop_config.json’ to include the mcp-hosts-installer command. For Cursor, update ‘mcp.json’ with the necessary command.

Key features

Key features of mcp-hosts-installer include the ability to install MCP servers hosted on npm or PyPi, compatibility with multiple IDEs (Cursor, Claude, VsCode), and the requirement of ‘npx’ and ‘uv’ for Node.js and Python servers respectively.

Where to use

mcp-hosts-installer can be used in software development environments where multiple MCP servers need to be installed and configured efficiently, particularly in IDEs like Cursor, Claude, and VsCode.

mcp-hosts-installer - A MCP Server to install MCP Servers in different hosts (Cursor, Claude…)

This server is a server that installs other MCP servers for you. Install it, and you can ask the selected host to install MCP servers hosted in npm or PyPi for you. Requires npx and uv to be installed for node and Python servers respectively.

How to install:

• For Claude

Put this into your claude_desktop_config.json (either at ~/Library/Application Support/Claude on macOS or C:\Users\NAME\AppData\Roaming\Claude on Windows):

• For Cursor

Put this into your mcp.json (either at /Users/NAME/.cursor on macOS or C:\Users\NAME\AppData\Roaming\.cursor on Windows):

• For VsCode

Put this into your mcp.json (either at /Users/NAME/.code on macOS or C:\Users\NAME\AppData\Roaming\.code on Windows):

By default, when using a host (Cursor…), it makes sense to install the MCP server on the current development environment, i.e., Cursor.
If you don’t specify a host, I prefer the active environment so I can use the MCP server immediately without any additional configuration.
Other options (like “claude” or “vscode”) require explicit specification because they correspond to other environments or tools.
In short: by default, without any specification from you, the installation is performed on the current environment, because that’s the environment you’re currently working in.

Example prompts In Cursor

Install the MCP server named mcp-server-fetch

Please install the MCP server at /Users/NAME/code/mcp-youtube, I’m too lazy to do it myself.

Install the MCP server @modelcontextprotocol/server-github. Set the environment variable GITHUB_PERSONAL_ACCESS_TOKEN to ‘1234567890’