Skip to main content
Glama
enesjakozh
XD3an

MCP Builder

by XD3an
OverviewSchemaRelated ServersScoreDiscussions
Python

mcp-빌더

다른 MCP 서버를 설치하기 위한 Python 기반 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 패키지의 경우 선택 사항)

설치

소스에서 설치

지엑스피1

용법

직접 실행

설치 후 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 데스크톱 통합

Claude Desktop과 함께 MCP Builder를 사용하려면 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

  • 리눅스: ~/.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