AI 클라이언트가 다른 MCP server를 검색, 추가, 활성화하고 프록시할 수 있게 하며, 런타임에 도구들을 통합된 접두사로 모아줍니다.
다른 이름 sitbon/magg
- 스타
- 143
- Tools
- 14
- 다운로드, 30일
- 3,127
- 최신 버전
- 1.2.1
- 마지막 커밋
- 2026년 9월 27일
- 라이선스
- AGPL-3.0
Magg MCP란?
AI 클라이언트가 다른 MCP server를 검색, 추가, 활성화하고 프록시할 수 있게 하며, 런타임에 도구들을 통합된 접두사로 모아줍니다. 14개 도구를 제공합니다. 예: magg_list_servers, magg_add_server, magg_remove_server.
프로젝트 README에서 생성된 요약
Magg MCP server 정보
AI 어시스턴트의 기능을 확장하려는 개발자는 Magg를 사용하여 여러 Model Context Protocol server를 관리하고 통합할 수 있습니다. Magg는 LLM이 세션 중에 새로운 서버를 동적으로 검색, 추가 및 구성할 수 있도록 하는 중앙 허브 역할을 합니다. 이 meta-server를 사용하면 AI 클라이언트는 새로운 기능이 추가될 때마다 사용자가 수동으로 개입할 필요 없이 자체 도구 세트를 확장할 수 있습니다.
이 도구는 Claude Desktop과 같은 클라이언트와의 로컬 통합을 위한 stdio 또는 시스템 전반의 액세스를 위한 HTTP를 통해 작동합니다. 인메모리 방식을 포함한 다양한 전송 방식을 지원하며, 동적 업데이트에 어려움을 겪는 클라이언트를 돕기 위해 ProxyMCP 도구를 제공합니다. 사용자는 kit를 사용하여 서버 그룹을 관리하고 로컬 JSON 파일에 설정을 유지할 수 있습니다. 보안이 필요한 원격 설정의 경우 RSA 기반 JWT 인증을 포함하며, 프로덕션 또는 개발 환경을 위해 Docker 이미지를 사용하여 배포할 수 있습니다.
활용 사례
- 1동적 도구 검색AI 어시스턴트가 새로운 MCP server를 검색하고 설치하여 즉석에서 새로운 SKILL을 습득할 수 있습니다.
- 2통합 도구 액세스개발자는 통합된 접두사를 사용하여 단일 인터페이스를 통해 여러 서버의 도구에 액세스할 수 있습니다.
- 3자동 서버 유지 관리시스템이 상태 검사를 수행하고 실패한 서버를 복구하거나 재구성하도록 시도할 수 있습니다.
- 4그룹화된 기능 관리사용자는 kit 관리 기능을 사용하여 관련 도구 세트 전체를 한 번에 로드하거나 언로드할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Magg MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Magg MCP 설치
$ claude mcp add magg -- uvx maggCursor에 Magg MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"magg": {
"command": "uvx",
"args": [
"magg"
]
}
}
}VS Code에 Magg MCP 설치
.vscode/mcp.json
{
"servers": {
"magg": {
"type": "stdio",
"command": "uvx",
"args": [
"magg"
]
}
}
}VS Code CLI에 Magg MCP 설치
$ code --add-mcp '{"name":"magg","type":"stdio","command":"uvx","args":["magg"]}'Claude Desktop에 Magg MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"magg": {
"command": "uvx",
"args": [
"magg"
]
}
}
}Codex에 Magg MCP 설치
$ codex mcp add magg -- uvx maggCodex config.toml에 Magg MCP 설치
~/.codex/config.toml
[mcp_servers.magg] command = "uvx" args = ["magg"]
Gemini CLI에 Magg MCP 설치
$ gemini mcp add -s user magg uvx -- maggGemini settings.json에 Magg MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"magg": {
"command": "uvx",
"args": [
"magg"
]
}
}
}Magg MCP 도구 14
README에서 감지됨magg_list_serversmagg_add_servermagg_remove_servermagg_search_serversmagg_list_toolsmagg_smart_configuremagg_analyze_serversmagg_statusmagg_checkmagg_reload_configmagg_load_kitmagg_unload_kit
| magg_list_servers | — | |
| magg_add_server | — | |
| magg_remove_server | — | |
| magg_search_servers | — | |
| magg_list_tools | — | |
| magg_smart_configure | — | |
| magg_analyze_servers | — | |
| magg_status | — | |
| magg_check | — | |
| magg_reload_config | — | |
| magg_load_kit | — | |
| magg_unload_kit | — |
도구 14개 모두 보기도구 수 줄이기
magg_list_kitsmagg_kit_info
| magg_list_kits | — | |
| magg_kit_info | — |
구성
MAGG_JWT
| 이름 | 설명 | 유형 |
|---|---|---|
| MAGG_JWT | — |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능sitbon/magg is public and reachablegithub.com/sitbon/magg ↗통과
- 패키지가 이 저장소를 소스로 명시magg names sitbon/magg as sourcepypi.org/project/magg/ ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-09-27github.com/sitbon/magg ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from magg통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음80 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음14 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기🧲 Magg - The MCP Aggregator
A Model Context Protocol server that manages, aggregates, and proxies other MCP servers, enabling LLMs to dynamically extend their own capabilities.
What is Magg?
Magg is a meta-MCP server that acts as a central hub for managing multiple MCP servers. It provides tools that allow LLMs to:
- Search for new MCP servers and discover setup instructions
- Add and configure MCP servers dynamically
- Enable/disable servers on demand
- Aggregate tools from multiple servers under unified prefixes
- Persist configurations across sessions
Think of Magg as a "package manager for LLM tools" - it lets AI assistants install and manage their own capabilities at runtime.
Features
- Self-Service Tool Management: LLMs can search for and add new MCP servers without human intervention.
- Dynamic Configuration Reloading: Automatically detects and applies config changes without restarting.
- Automatic Tool Proxying: Tools from added servers are automatically exposed with configurable prefixes.
- ProxyMCP Tool: A built-in tool that proxies the MCP protocol to itself, for clients that don't support notifications or dynamic tool updates (which is most of them currently).
- Smart Configuration: Uses MCP sampling to intelligently configure servers from just a URL.
- Persistent Configuration: Maintains server configurations in
.magg/config.json. - Multiple Transport Support: Works with stdio, HTTP, and in-memory transports.
- Bearer Token Authentication: Optional RSA-based JWT authentication for secure HTTP access.
- Docker Support: Pre-built images for production, staging, and development workflows.
- Health Monitoring: Built-in
magg_statusandmagg_checktools for server health checks. - Real-time Messaging: Full support for MCP notifications and messages - receive tool/resource updates and progress notifications from backend servers.
- Python 3.12+ Support: Fully compatible with Python 3.12 and 3.13.
- Kit Management: Bundle related MCP servers into kits for easy loading/unloading as a group.
- MBro CLI: Included MCP Browser for interactive exploration and management of MCP servers, with script support for automation.
Installation
Prerequisites
- Python 3.12 or higher (3.13+ recommended)
uv(recommended) - Install from astral.sh/uv
Quick Install (Recommended)
The easiest way to install Magg is as a tool using uv:
# Install Magg as a tool
uv tool install magg
# Run with stdio transport (for Claude Desktop, Cline, etc.)
magg serve
# Run with HTTP transport (for system-wide access)
magg serve --http
Alternative: Run Directly from GitHub
You can also run Magg directly from GitHub without installing:
# Run with stdio transport
uvx --from git+https://github.com/sitbon/magg.git magg
# Run with HTTP transport
uvx --from git+https://github.com/sitbon/magg.git magg serve --http
Local Development
For development, clone the repository and install in editable mode:
# Clone the repository
git clone https://github.com/sitbon/magg.git
cd magg
# Install in development mode with dev dependencies
uv sync --dev
# Or with poetry
poetry install --with dev
# Run the CLI
magg --help
Docker
Magg is available as pre-built Docker images from GitHub Container Registry:
# Run production image (WARNING log level)
docker run -p 8000:8000 ghcr.io/sitbon/magg:latest
# Run with authentication (mount or set private key)
docker run -p 8000:8000 \
-v ~/.ssh/magg:/home/magg/.ssh/magg:ro \
ghcr.io/sitbon/magg:latest
# Or with environment variable
docker run -p 8000:8000 \
-e MAGG_PRIVATE_KEY="$(cat ~/.ssh/magg/magg.key)" \
ghcr.io/sitbon/magg:latest
# Run beta image (INFO log level)
docker run -p 8000:8000 ghcr.io/sitbon/magg:beta
# Run with custom config directory
docker run -p 8000:8000 \
-v /path/to/config:/home/magg/.magg \
ghcr.io/sitbon/magg:latest
Docker Image Strategy
Magg uses a multi-stage Docker build with three target stages:
pro(Production): Minimal image with WARNING log level, suitable for production deploymentspre(Pre-production): Same as production but with INFO log level for staging/testing (available but not published)dev(Development): Includes development dependencies and DEBUG logging for troubleshooting
Images are automatically published to GitHub Container Registry with the following tags:
- Version tags (from main branch):
1.2.3,1.2,dev,1.2-dev,1.2-dev-py3.12, etc. - Branch tags (from beta branch):
beta,beta-dev - Python-specific dev tags:
beta-dev-py3.12,beta-dev-py3.13, etc.
Pull requests build and test images but do not publish them unless a maintainer adds the
push-image label, which publishes ephemeral pr-NN / pr-NN-dev tags (same-repo PRs
only). Ephemeral pr-* tags and untagged manifests are cleaned up weekly; version tags
are kept forever, so pinned deployments are never affected.
Docker Compose
For easier management, use Docker Compose:
# Clone the repository
git clone https://github.com/sitbon/magg.git
cd magg
# Run production version
docker compose up magg
# Run staging version (on port 8001)
docker compose up magg-beta
# Run development version (on port 8008)
# This uses ./.magg/config.json for configuration
docker compose up magg-dev
# Build and run with custom registry
REGISTRY=my.registry.com docker compose build
REGISTRY=my.registry.com docker compose push
See compose.yaml and .env.example for configuration options.
Usage
Running Magg
Magg can run in three modes:
-
Stdio Mode (default) - For integration with Claude Desktop, Cline, Cursor, etc.:
magg serve -
HTTP Mode - For system-wide access or web integrations:
magg serve --http --port 8000 -
Hybrid Mode - Both stdio and HTTP simultaneously:
magg serve --hybrid magg serve --hybrid --port 8080 # Custom portThis is particularly useful when you want to use Magg through an MCP client while also allowing HTTP access. For example:
With Claude Code:
# Configure Claude Code to use Magg in hybrid mode claude mcp add magg -- magg serve --hybrid --port 42000With mbro:
# mbro hosts Magg and connects via stdio mbro connect magg "magg serve --hybrid --port 8080" # Other mbro instances can connect via HTTP mbro connect magg http://localhost:8080
Available Tools
Once Magg is running, it exposes the following tools to LLMs:
magg_list_servers- List all configured MCP serversmagg_add_server- Add a new MCP servermagg_remove_server- Remove a servermagg_enable_server/magg_disable_server- Toggle server availabilitymagg_search_servers- Search for MCP servers onlinemagg_list_tools- List all available tools from all serversmagg_smart_configure- Intelligently configure a server from a URLmagg_analyze_servers- Analyze configured servers and suggest improvementsmagg_status- Get server and tool statisticsmagg_check- Health check servers with repair actions (report/remount/unmount/disable)magg_reload_config- Reload configuration from disk and apply changesmagg_load_kit- Load a kit and its servers into the configurationmagg_unload_kit- Unload a kit and optionally its servers from the configurationmagg_list_kits- List all available kits with their statusmagg_kit_info- Get detailed information about a specific kit
Quick Inspection with MBro
Magg includes the mbro (MCP Browser) CLI tool for interactive exploration. A unique feature is the ability to connect to Magg in stdio mode for quick inspection:
# Connect mbro to a Magg instance via stdio (no HTTP server needed)
mbro connect local-magg magg serve
# Now inspect your Magg setup from the MCP client perspective
mbro:local-magg> call magg_status
mbro:local-magg> call magg_list_servers
MBro also supports:
- Scripts: Create
.mbrofiles with commands for automation - Shell-style arguments: Use
key=valuesyntax instead of JSON - Tab completion: Rich parameter hints after connecting
See the MBro Documentation for details.
Authentication
Magg supports optional bearer token authentication to secure access:
Quick Start
-
Initialize authentication (creates RSA keypair):
magg auth init -
Generate a JWT token for clients:
# Generate token (displays on screen) magg auth token # Export as environment variable export MAGG_JWT=$(magg auth token -q) -
Connect with authentication:
- Using
MaggClient(auto-loads from MAGG_JWT):from magg.client import MaggClient async def main(): async with MaggClient("http://localhost:8000/mcp") as client: tools = await client.list_tools() - Using FastMCP with explicit token:
from fastmcp import Client from fastmcp.client import BearerAuth jwt_token = "your-jwt-token-here" async with Client("http://localhost:8000/mcp", auth=BearerAuth(jwt_token)) as client: tools = await client.list_tools()
- Using
Key Management
- Keys are stored in
~/.ssh/magg/by default - Private key can be set via
MAGG_PRIVATE_KEYenvironment variable - To disable auth, remove keys or set non-existent
key_pathin.magg/auth.json
Authentication Commands
magg auth init- Initialize authentication (generates RSA keypair)magg auth status- Check authentication configurationmagg auth token- Generate JWT tokenmagg auth public-key- Display public key (for verification)magg auth private-key- Display private key (for backup)
See examples/authentication.py for more usage patterns.
Configuration
Magg stores its configuration in .magg/config.json in your current working directory. This allows for project-specific tool configurations.
Dynamic Configuration Reloading
Magg supports automatic configuration reloading without requiring a restart:
- Automatic file watching: Detects changes to
config.jsonand reloads automatically (uses watchdog when available) - SIGHUP signal: Send
kill -HUP <pid>to trigger immediate reload (Unix-like systems) - MCP tool: Use
magg_reload_configtool from any MCP client - Smart transitions: Only affected servers are restarted during reload
Configuration reload is enabled by default. You can control it with:
MAGG_AUTO_RELOAD=false- Disable automatic reloadingMAGG_RELOAD_POLL_INTERVAL=5.0- Set polling interval in seconds (when watchdog unavailable)
See Configuration Reload Documentation for detailed information.
Environment Variables
Magg supports several environment variables for configuration:
MAGG_CONFIG_PATH- Path to config file (default:.magg/config.json)MAGG_LOG_LEVEL- Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL (default: INFO)MAGG_STDERR_SHOW=1- Show stderr output from subprocess MCP servers (default: suppressed)MAGG_AUTO_RELOAD- Enable/disable config auto-reload (default: true)MAGG_RELOAD_POLL_INTERVAL- Config polling interval in seconds (default: 1.0)MAGG_READ_ONLY=true- Run in read-only modeMAGG_SELF_PREFIX- Prefix for Magg tools (default: "magg"). Tools will be named as{prefix}{sep}{tool}(e.g.,magg_list_servers)MAGG_PREFIX_SEP- Separator between Magg's prefix and its tool names (default: "_"). Backend server tools always use_MAGG_BACKEND_INIT_TIMEOUT- Seconds to wait for a backend server to start before giving up on it (default: 30,0waits forever)
Example configuration:
{
"servers": {
"calculator": {
"name": "calculator",
"source": "https://github.com/executeautomation/calculator-mcp",
"command": "npx @executeautomation/calculator-mcp",
"prefix": "calc",
"enabled": true
}
}
}
Adding Servers
Servers can be added in several ways:
-
Using the LLM (recommended):
"Add the Playwright MCP server" "Search for and add a calculator tool" -
Manual configuration via
magg_add_server:name: playwright url: https://github.com/microsoft/playwright-mcp command: npx @playwright/mcp@latest prefix: pw -
The
magg serverCLI (see below) -
Direct config editing: Edit
.magg/config.jsondirectly
Managing Servers from the CLI
Server and kit configuration can be managed entirely from the command line — no MCP client
or running server required. The CLI edits .magg/config.json directly, and a running Magg
instance picks up the changes automatically via config reload.
(Tools that require a live server, like magg_search_servers, magg_check, and
magg_smart_configure, remain available through any MCP client such as mbro.)
# List servers (human-readable, or JSON on stdout for scripting)
magg server list
magg server list --json
# Add a server
magg server add playwright https://github.com/microsoft/playwright-mcp \
--command "npx @playwright/mcp@latest" --prefix pw
# Add a server without enabling it, with transport options
magg server add web https://example.com/web --uri http://localhost:9000/mcp \
--transport '{"keep_alive": false}' --disable
# Update an existing server (pass '' to clear an optional field)
magg server update playwright --prefix play --notes "Browser automation"
magg server update playwright --command "npx @playwright/mcp@next"
magg server update playwright --notes ""
# Enable / disable / inspect / remove
magg server enable playwright
magg server disable playwright
magg server info playwright --json
magg server remove playwright
Real-time Notifications with MaggClient
The MaggClient now supports real-time notifications from backend MCP servers:
from magg import MaggClient, MaggMessageHandler
# Using callbacks
handler = MaggMessageHandler(
on_tool_list_changed=lambda n: print("Tools changed!"),
on_progress=lambda n: print(f"Progress: {n.params.progress}")
)
async with MaggClient("http://localhost:8000/mcp", message_handler=handler) as client:
# Client will receive notifications while connected
tools = await client.list_tools()
See Messaging Documentation for advanced usage including custom message handlers.
Kit Management
Magg supports organizing related MCP servers into "kits" - bundles that can be loaded and unloaded as a group:
# List available kits
magg kit list
# Load a kit (adds all its servers)
magg kit load web-tools
# Unload a kit (removes servers only in that kit)
magg kit unload web-tools
# Get information about a kit
magg kit info web-tools
# Export the current configuration (or a loaded kit) as a kit file
magg kit export --name my-kit --output my-kit.json
When unloading a kit, servers that belong only to that kit are removed, while servers shared with other kits are kept.
You can also manage kits programmatically through Magg's tools when connected via an MCP client:
magg_list_kits- List all available kitsmagg_load_kit- Load a kit and its serversmagg_unload_kit- Unload a kitmagg_kit_info- Get detailed kit information
Kits are JSON files stored in ~/.magg/kit.d/ or .magg/kit.d/ that define a collection of related servers. See Kit Documentation for details on creating and managing kits.
MBro Scripts
Automate common workflows with MBro scripts:
# Create a setup script
cat > setup.mbro <<EOF
# Connect to Magg and check status
connect magg magg serve
call magg_status
call magg_list_servers
# Add a new server if needed
call magg_add_server name=calculator source="npx -y @modelcontextprotocol/server-calculator"
EOF
# Run the script
mbro -x setup.mbro
MCP 2026-07-28 (Stateless Spec)
The MCP 2026-07-28 spec moves the protocol to a stateless request/response core. Magg's take: something still has to own long-lived stdio subprocesses, backend connections, and tool-list caching — and that's exactly the layer an aggregator provides. See Magg and the Stateless MCP Spec for the impact analysis and migration plan, including how Magg bridges pre-2026 (stateful) backends to stateless-era clients and how hierarchical Magg deployments fit in.
Documentation
For more documentation, see docs/.
Appearances
Magg appears in multiple locations. Please feel free to submit a PR to add more appearances below in alphabetical order.
Listing, Index, and other MCP Sites
Magg ships a server.json manifest for the
official MCP Registry (as io.github.sitbon/magg),
and magg_search_servers queries the registry as a first-class discovery source alongside
Glama, GitHub, and npm. See MCP Registry Documentation for publishing
instructions.
mcp-name: io.github.sitbon/magg
Awesome GitHub MCP Lists
Magg MCP 질문
Magg MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add magg -- uvx magg를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Magg MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Magg MCP는 어떤 도구를 제공하나요?
14개 도구를 제공합니다. 예: magg_list_servers, magg_add_server, magg_remove_server, magg_search_servers, magg_list_tools.
Magg는 무엇을 하나요?
Magg는 다른 MCP server를 관리하고 프록시하는 meta-MCP server입니다. LLM이 서버를 검색, 추가, 활성화하고 런타임에 도구들을 통합할 수 있도록 지원합니다.
Magg를 어떻게 설치하고 실행하나요?
uv tool install magg 명령어로 설치한 후, stdio 방식은 magg serve를, HTTP 방식은 magg serve --http를 실행합니다.
Magg는 인증을 지원하나요?
네, magg auth init 및 magg auth token으로 생성한 RSA 기반 JWT 토큰을 사용하여 선택적으로 bearer token 인증을 제공합니다.
Magg는 설정을 어디에 저장하나요?
서버 설정은 .magg/config.json 파일에 저장되며 동적으로 다시 로드됩니다.
Magg를 stdio와 HTTP 모드에서 동시에 실행할 수 있나요?
네, magg serve --hybrid를 통해 stdio와 HTTP를 동시에 제공하는 하이브리드 모드를 사용할 수 있습니다.