Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 12, 2026·2 min de lectura

ContextForge — MCP Registry + Proxy Gateway

ContextForge runs an MCP gateway that federates tool servers behind one endpoint, adding governance, auth, and observability for agent tool calls.

MCP Hub
MCP Hub · Community
Listo para agents

Staging seguro para este activo

Este activo primero queda en staging. El prompt copiado pide inspeccionar los archivos staged antes de activar scripts, config MCP o config global.

Stage only · 17/100Política: staging
Superficie agent
Cualquier agent MCP/CLI
Tipo
Mcp Config
Instalación
Stage only
Confianza
Confianza: Established
Entrada
Asset
Comando de staging seguro
npx -y tokrepo@latest install 238b1ffd-a61b-48fb-bf45-70cf8dd48a36 --target codex

Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.

Introducción

ContextForge runs an MCP gateway that federates tool servers behind one endpoint, adding governance, auth, and observability for agent tool calls.

  • Best for: platform teams standardizing many MCP servers behind one controlled gateway endpoint
  • Works with: Python ≥3.11, MCP servers (stdio or containers), optional OpenTelemetry backends
  • Setup time: 30–60 minutes

Practical Notes

  • Data point: the quick start binds the gateway on port 4444.
  • Quant: start with 2–4 upstream servers, then scale once auth + logging are correct.

Pattern: “one endpoint” for tool calling

If you have multiple MCP servers (internal + third-party), a gateway lets you:

  • consolidate auth and secrets,
  • add consistent logging and traces,
  • and standardize discovery for clients.

Rollout checklist

  • Decide transport per upstream (stdio, docker, or remote).
  • Enable an admin API only for trusted networks.
  • Add health checks + metrics before allowing production traffic.

FAQ

Q: Is ContextForge open-source? A: Yes. It’s Apache-2.0 licensed on GitHub.

Q: Do I need Docker? A: Not necessarily. The repo supports multiple transports; Docker is an option.

Q: What’s the first thing to harden? A: Authentication + auditing logs, before adding more upstream servers.

🙏

Fuente y agradecimientos

Source: https://github.com/IBM/mcp-context-forge > License: Apache-2.0 > GitHub stars: 3,686 · forks: 655

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

MCP Gateway & Registry — Team Tool Control

MCP Gateway & Registry centralizes MCP servers and agent tools with auth, search, and audit, so teams can manage integrations and scan servers before use.

MCP Configs
MCP Hub

ToolSDK MCP Registry — Private Gateway + Sandbox

Self-host a private MCP gateway/registry with OpenAPI, sandboxed remote execution and OAuth 2.1, or use @toolsdk.ai/registry to query server configs.

MCP Configs
MCP Hub

jarvis-registry — Secure MCP/Agent Gateway

Jarvis Registry centralizes MCP and A2A access behind OIDC, ACL, and observability—securely proxy tools for copilots. Verified 811★; pushed 2026-05-14.

MCP Configs
MCP Hub

agentgateway — Agent Proxy for MCP Servers

Run a Rust agent proxy that connects agents to tools and MCP servers with security controls and observability. Releases ship cross-platform binaries.

MCP Configs
MCP Hub
◈Inicio🔍Buscar👤Yo