Skip to main content
Glama
Gnayiak

cursor_mcp_installer

by Gnayiak
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

🚀 Cursor MCP 安装工具

为 Cursor 设计的 MCP 服务器安装程序，轻松扩展 AI 能力

📋 功能简介

这是一个元服务器，专为 Cursor 用户设计，可帮助您一键安装和配置其他 MCP 服务器。支持从 npm 或 PyPi 安装服务器，并自动处理配置过程。

技术要求：

  • 需安装 npx 用于 Node.js 服务器

  • 需安装 uv 用于 Python 服务器

Related MCP server: Cursor MCP Installer

🔧 安装方法

将以下配置添加到 Cursor MCP 配置文件：

  • Windows: C:\Users\用户名\.cursor\mcp.json

  • macOS: ~/.cursor/mcp.json

方法一（推荐）：

{
  "mcpServers": {
    "cursor-mcp-installer": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@yumia-pretty/cursor-mcp-installer@latest"
      ]
    }
  }
}

方法二：

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

📊 兼容性

该工具兼容所有标准 MCP 服务器，包括 npm 包和本地开发的服务器。

📦 源代码

此项目的源代码托管在GitHub上：yumia-pretty/cursor-mcp-installer

Available Tools

2 tools
install_local_mcp_serverC

Install an MCP server whose code is cloned locally on your computer

ParametersJSON Schema
NameRequiredDescriptionDefault
pathYesThe path to the MCP server code cloned on your computer
argsNoThe arguments to pass along
envNoThe environment variables to set, delimited by =

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('install') but doesn't describe what installation entails (e.g., whether it modifies system files, requires permissions, has side effects, or what happens on success/failure). For a tool that likely performs system-level operations, this lack of detail is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word contributing to understanding the core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of installing software (potentially involving system changes) and the absence of both annotations and an output schema, the description is insufficient. It doesn't explain what 'install' means operationally, what gets installed where, or what the expected outcome is. For a tool with no structured safety or output information, more descriptive context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters (path, args, env) adequately. The description adds no additional parameter semantics beyond what's in the schema, such as format examples for 'env' or typical use cases for 'args'. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('install') and resource ('MCP server whose code is cloned locally on your computer'), making the purpose understandable. However, it doesn't explicitly differentiate from its sibling 'install_repo_mcp_server' beyond the 'cloned locally' phrasing, which implies but doesn't explicitly contrast with repository-based installation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, including its sibling 'install_repo_mcp_server'. It doesn't mention prerequisites (e.g., having the code already cloned), exclusions, or contextual factors that would help an agent choose between installation methods.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

install_repo_mcp_serverC

Install an MCP server via npx or uvx

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe package name of the MCP server
argsNoThe arguments to pass along
envNoThe environment variables to set, delimited by =

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Install') but doesn't describe what happens during installation (e.g., whether it modifies system files, requires admin permissions, handles errors, or has side effects like downloading dependencies). This leaves significant gaps in understanding the tool's behavior and potential risks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and method, making it easy to understand at a glance. Every part of the sentence contributes essential information, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of an installation tool with no annotations and no output schema, the description is insufficient. It lacks details on what 'install' entails (e.g., success/failure outcomes, post-installation steps, or error handling). For a tool that likely involves system changes, more context is needed to ensure safe and correct usage by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear documentation for all three parameters. The description adds no additional semantic information beyond what's in the schema (e.g., it doesn't explain typical values for 'name', usage of 'args', or format examples for 'env'). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Install') and the resource ('an MCP server'), specifying the method ('via npx or uvx'). It distinguishes from the sibling tool 'install_local_mcp_server' by implying this is for remote/package-based installation rather than local, though not explicitly stated. However, it lacks specific details about what 'install' entails (e.g., global vs. local, dependencies).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives is provided. The description mentions 'via npx or uvx', which hints at usage contexts (Node.js or Python package managers), but it doesn't specify when to choose this over the sibling 'install_local_mcp_server' or other installation methods. There are no prerequisites, exclusions, or clear scenarios outlined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one installs MCP servers from local code, while the other installs them via package managers (npx/uvx). There is no overlap or ambiguity between these installation methods, making it easy for an agent to select the correct tool based on the source of the server.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'install' as the verb and descriptive suffixes ('local_mcp_server', 'repo_mcp_server'). The naming is uniform and predictable, using snake_case throughout, which aids in clarity and usability.

Tool Count3/5

With only 2 tools, the server feels thin for an installer purpose, as it might lack operations like uninstalling, listing installed servers, or updating. While the tools cover basic installation scenarios, the limited count suggests incomplete functionality for managing MCP servers comprehensively.

Completeness2/5

The tool surface is significantly incomplete for an installer domain. It only provides installation methods but lacks essential operations such as uninstallation, listing installed servers, updating servers, or checking installation status. This creates gaps that could lead to agent failures when trying to manage MCP servers beyond initial setup.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gnayiak/cursor-mcp-installer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server