convez.ai
MCP ServerIntegração & APIsAvançado
Jemplayer82

MCP Agent Bus

Jemplayer82/mcp-agentbus

Barramento de mensagens em tempo real para orquestração de agentes

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que implementa um barramento de mensagens em tempo real para comunicação inter-agentes. Permite que múltiplos agentes Claude se coordenem e troquem mensagens de forma assíncrona e escalável.

Instalação

$npx convez-ai Jemplayer82/mcp-agentbus

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 1 mês
Versão
v1.4.0
Issues abertas
0
Contribuidores
1

Casos de uso

  • Coordenação entre múltiplos agentes autônomos
  • Sistemas multi-agente com comunicação assíncrona
  • Orquestração de workflows complexos entre LLMs

Veredito

MCP server bem estruturado para cenários de multi-agência. Requer familiaridade com padrões de mensageria e arquitetura de sistemas distribuídos, mas oferece uma primitiva poderosa e ausente no ecossistema Claude.

README

A tradução para o português deste README ainda está na fila.

mcp-store

A self-hosted app store for Model Context Protocol servers. Browse a curated catalog, fill in your secrets, click Deploy — no YAML required.

FastAPI Docker Catalog Transport


What is it

MCP Store is a lightweight web app that turns deploying MCP servers into a point-and-click operation. Instead of hand-editing docker-compose.yml files, you open a browser, pick the servers you need from the catalog, paste your API keys, and click Deploy.

The orchestrator generates a compose stack and pushes it to Docker directly or through Portainer — secrets never touch a config file.


How it works

1 — Catalog loads from YAML

catalog/catalog.yaml defines every available server — its name, category, Docker image or npx package, required env keys, and docs link. catalog.py parses it into Pydantic models at startup. No database needed.

2 — UI renders the catalog & checks installed state

The SPA calls /api/catalog then /api/installed, which introspects the live Portainer/Docker stack to show which servers are already running. Cards render with category tags, secret input fields, and docs links.

3 — You check boxes, fill secrets, click Deploy

Selected server IDs plus env values are POSTed to /api/deploy. Secrets travel only from browser → localhost:8090 → Docker/Portainer. They are never written to disk unless you explicitly opt in.

4 — composegen.py builds the stack

Each entry is resolved to a service definition:

Entry typeHow it runs
supergateway-npxWraps any npx package behind supergateway on the streamableHttp transport
imagePulls a prebuilt ghcr.io image directly
buildClones a GitHub repo and builds the image on your Docker host

Ports, volumes, and shm_size are applied per spec. An nginx proxy can optionally front all services on the same network.

5 — Deploy adapter pushes the stack

Docker socket: the compose dict is applied via the Docker SDK directly on the host.

Portainer adapter: the YAML is posted to Portainer's REST API, creating or merging into a named stack on the target endpoint. Merge mode does a read-modify-write so existing services aren't pruned.

6 — Build-from-source (optional)

Paste any public GitHub URL under Add Custom Server → GitHub URL. The preview endpoint auto-detects a Dockerfile vs package.json and recommends the right deploy type. Click Deploy — the orchestrator clones and builds on your Docker host. Edge targets push the resulting image to a registry first.


Catalog

21+ curated servers across 13 categories, defined in catalog/catalog.yaml. Each entry ships with env-key scaffolding — you fill in values, never the catalog.

CategoryServers
memoryMemory (knowledge graph)
reasoningSequential Thinking
aiOllama · EverArt
devGitHub · GitLab · Sentry
searchSearXNG · Brave Search · Fetch
storageFilesystem · Google Drive
databasePostgreSQL
communicationSlack
productivityLinear · Notion · GSD Cloud Gateway
browserGSD Browser · Puppeteer
infrastructurePortainer MCP
financeSchwab Trading
home-automationHome Assistant

Install

Option A — Docker Socket

Deploys MCP servers directly to this machine. Simplest setup, no extra tools needed.

docker run -d \
  --name mcp-store \
  -p 8090:8000 \
  -v mcp-store-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  ghcr.io/jemplayer82/mcp-orchestrator:latest

Open http://localhost:8090 and deploy your first servers.

Option B — Portainer API

Deploys to a remote host through Portainer's REST API. Your token stays server-side.

docker run -d \
  --name mcp-store \
  -p 8090:8000 \
  -v mcp-store-data:/data \
  ghcr.io/jemplayer82/mcp-orchestrator:latest

Open http://localhost:8090 → Deploy Target → Portainer API → enter your URL, API token, and Endpoint ID → Save Config.

docker-compose (recommended)

curl -O https://raw.githubusercontent.com/Jemplayer82/mcp-store/main/docker-compose.yml
docker compose up -d
version: "3.9"

services:
  mcp-store:
    image: ghcr.io/jemplayer82/mcp-orchestrator:latest
    container_name: mcp-store
    restart: unless-stopped
    ports:
      - "8090:8000"
    volumes:
      - orchestrator_data:/data
      # Uncomment for Docker socket mode:
      # - /var/run/docker.sock:/var/run/docker.sock
    healthcheck:
      test: ["CMD", "curl", "-sf", "http://localhost:8000/api/health"]
      interval: 30s
      timeout: 5s
      retries: 3

volumes:
  orchestrator_data:

Custom servers

Any npx package

Open Add Custom Server → npx Package and enter a package name or github:owner/repo spec. Works with anything that runs via npx -y <package>.

Build from a GitHub URL

Paste any public GitHub repo URL under Add Custom Server → GitHub URL. The preview endpoint detects a Dockerfile or package.json and recommends the right deploy type automatically.

⚠️ Building from a GitHub URL runs that code on your Docker host. Only use sources you trust. A _trust_confirmed=yes env flag is required as an explicit acknowledgement.

Save to My Catalog

Custom servers can be saved to your local catalog so they persist across sessions and appear in the main grid alongside official servers.


Security

  • No secrets in the repo. The catalog stores only env key names and labels — never values.
  • Portainer token stays server-side. The SPA calls only localhost:8090/api/* — your token is never sent to the browser or logged.
  • Transient by default. Secrets entered at deploy time are used once and discarded unless you explicitly opt in to persistence.
  • Docker socket warning. Mounting /var/run/docker.sock gives the container host-level access. Use Portainer mode for a lower-privilege setup on remote hosts.
  • Build trust gate. Deploying a build-type server requires _trust_confirmed=yes as a speed-bump against accidentally running untrusted code.

Development

git clone https://github.com/Jemplayer82/mcp-store
cd mcp-store
pip install -r requirements.txt
uvicorn app.main:app --reload --port 8090

Hot-reload with Docker:

docker compose -f docker-compose.dev.yml up

Run tests:

pytest tests/

Adding a server to the catalog

Fork the repo, add an entry to catalog/catalog.yaml, open a PR. See catalog/README.md for the full schema and rules. Official entries must be type supergateway-npx or image — never build.


MIT License

Ver o original no GitHub

Bom para

Relacionados