Skip to main content
Glama
enesjakozh
XD3an

MCP Builder

by XD3an
OverviewSchemaRelated ServersScoreDiscussions
Python

mcp-builder

基于 Python 的 MCP 服务器，用于安装其他 MCP 服务器。

该服务器的目的是提供一种完整、用户友好且跨平台的方式来安装和配置 MCP 服务器。

待办事项

  • [ ] 支持更多 MCP 客户端（例如 Cursor、Windsurf 等）

  • [ ] 支持更多 MCP 服务器类型和源（例如 Node.js、Java 等）

  • [ ] 支持安装失败的恢复机制

  • ...

特征

  • 软件包存储库安装：从 PyPI 或 npm 软件包安装 MCP 服务器

  • 本地安装：从本地目录安装 MCP 服务器

  • 配置管理：为已安装的服务器配置环境变量和参数

  • 自动检测：自动检测 MCP 服务器的类型（Node.js 或 Python）

  • 跨平台支持：适用于 Windows、macOS 和 Linux

Related MCP server: MCP Server Deepdive

要求

  • Python 3.10 或更高版本

  • pip（用于 Python 包）

  • Node.js 和 npm（可选，用于 JavaScript 包）

安装

从源安装

git clone https://github.com/xd3an/mcp-builder.git
cd mcp-builder
pip install -e .

用法

直接运行

安装完成后，您可以直接运行 MCP Builder：

# Using the entry point
mcpbuilder

# Or as a module
python -m mcp_builder.server

开发模式

对于开发和测试，您可以使用 MCP CLI 工具：

# Install MCP CLI tools
pip install "mcp[cli]"

# Run in development mode
mcp dev path/to/mcp_builder/server.py

# npx @modelcontextprotocol/inspector
npx @modelcontextprotocol/inspector python -m mcp_builder.server

MCP 客户端集成

Claude 桌面集成

要将 MCP Builder 与 Claude Desktop 一起使用，请将其添加到您的claude_desktop_config.json文件中：

{
  "mcpServers": {
    "mcp-builder": {
      "command": "python",
      "args": [
        "-m",
        "mcp_builder.server"
      ]
    }
  }
}

配置文件位于：

  • Windows： %APPDATA%\Claude\claude_desktop_config.json

  • macOS： ~/Library/Application Support/Claude/claude_desktop_config.json

  • Linux： ~/.config/Claude/claude_desktop_config.json

示例命令

与 Claude Desktop 集成后，您可以要求 Claude：

阅读https://github.com/microsoft/playwright-mcp帮助我在 Claude 配置中安装 playwright-mcp

演示图像

工作原理

MCP Builder 修改 Claude Desktop 配置文件以注册 MCP 服务器。它支持：

  1. Node.js 包：使用npx安装并配置 Claude 使用它们

  2. Python 包：配置 Claude 使用 Python 模块

  3. 本地存储库：安装依赖项并配置 Claude 使用本地代码

Available Tools

2 tools
install_local_mcp_serverC
Install an MCP server from a local directory.

Args:
    path: The path to the MCP server code cloned on your computer
    args: The arguments to pass along
    env: The environment variables to set, delimited by =
ParametersJSON Schema
NameRequiredDescriptionDefault
pathYes
argsNo
envNo

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 mentions installing from a local directory but fails to describe critical behaviors like whether this is a destructive operation, what permissions are needed, how errors are handled, or what the expected outcome is. This leaves significant gaps for an agent to understand the tool's behavior.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded, starting with a clear purpose statement followed by a structured parameter list. It avoids unnecessary verbosity, though the parameter descriptions could be slightly more informative without sacrificing conciseness.

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 an MCP server, no annotations, no output schema, and minimal parameter details, the description is incomplete. It doesn't cover expected outputs, error conditions, dependencies, or behavioral nuances, making it inadequate for an agent to use the tool confidently in varied contexts.

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 description includes an 'Args' section that lists and briefly describes the three parameters (path, args, env), adding meaning beyond the input schema, which has 0% description coverage. However, the explanations are minimal (e.g., 'The arguments to pass along' without specifying format or examples), providing only basic semantic value without fully compensating for the schema's lack of detail.

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 resource ('an MCP server from a local directory'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling tool 'install_repo_mcp_server', which likely installs from a repository rather than a local directory.

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, such as the sibling tool 'install_repo_mcp_server'. It lacks context about prerequisites, typical use cases, or any exclusions, leaving the agent without clear usage direction.

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 pip or npm.

Args:
    name: The package name of the MCP server
    args: The arguments to pass along
    env: The environment variables to set, delimited by =
ParametersJSON Schema
NameRequiredDescriptionDefault
nameYes
argsNo
envNo

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 but provides minimal behavioral context. It mentions installation but doesn't disclose important traits like whether this requires admin privileges, what happens if installation fails, whether it modifies system state permanently, or what the expected output is. The description doesn't contradict annotations since none exist.

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

Conciseness4/5

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

The description is appropriately concise with a clear purpose statement followed by parameter explanations. The structure is front-loaded with the main functionality. However, the parameter explanations could be more efficiently integrated rather than listed as separate bullet points.

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?

For a tool that performs system installation with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't cover important context like prerequisites, error handling, success criteria, or what happens after installation. The agent lacks critical information to use this tool effectively.

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?

With 0% schema description coverage, the description adds value by explaining all three parameters: 'name' as package name, 'args' as arguments to pass, and 'env' as environment variables. However, it doesn't provide format details (e.g., how environment variables should be formatted with '=' delimiter), examples, or constraints beyond basic semantics.

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', specifying installation via pip or npm. It distinguishes from the sibling tool 'install_local_mcp_server' by implying this is for repository-based installation rather than local, though not explicitly stated.

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 existence of sibling tool 'install_local_mcp_server' suggests there are different installation methods, but the description doesn't explain when to choose repository vs local installation.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updates
    • First observedinstall_local_mcp_server
    • First observedinstall_repo_mcp_server
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one installs from a local directory, while the other installs from a package repository via pip or npm. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the installation source.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'install' as the verb and descriptive nouns ('local_mcp_server', 'repo_mcp_server'). The naming is predictable and readable, with no deviations in style or convention.

Tool Count2/5

With only 2 tools, the server feels thin for a 'Builder' purpose, which might imply broader capabilities like configuration, management, or testing of MCP servers. The count is too low for the apparent scope, limiting functionality and potentially causing gaps in agent workflows.

Completeness2/5

The tool surface is severely incomplete for a 'Builder' domain, as it only covers installation from two sources. Missing are obvious operations like uninstalling, listing installed servers, configuring servers, or building/testing MCP projects, which are essential for comprehensive server management.

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

  • MCP Server Deepdive

    KrishnaPapana
    F
    license
    B
    quality
    D
    maintenance
    A Python-based MCP server implementation that can be easily installed via pip or directly from GitHub, providing a simple way to deploy and run MCP server functionality.
    1
    -

  • mcp-server-master

    Leandroglez39
    F
    license
    Not graded
    quality
    D
    maintenance
    This repository provides a template for creating MCP servers with Python, including installation instructions and tools for testing with the MCP Inspector.
    -

Appeared in Searches

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/XD3an/mcp-builder'

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