MCP server de JoinLayer
Commit 10 nov 2026Gestiona pipelines de datos seguros a través de un gateway de MCP alojado mediante autenticación OAuth delegada.
También conocido como joinlayer/agent-toolkit, agent-toolkit
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.1.2
- Último commit
- 10 nov 2026
- Licencia
- Apache-2.0
¿Qué es JoinLayer MCP?
JoinLayer es un MCP server. Gestiona pipelines de datos seguros a través de un gateway de MCP alojado mediante autenticación OAuth delegada.
Resumen generado a partir del README del proyecto
Acerca del MCP server de JoinLayer
JoinLayer ofrece un gateway de MCP alojado, diseñado para la gestión de pipelines de datos seguros. Permite a los desarrolladores conectar agentes de IA a sus entornos de datos utilizando la skill joinlayer-pipelines. El servicio opera a través de un endpoint remoto en mcp.joinlayer.app/mcp, que actúa como un límite de seguridad entre el agente y la infraestructura de datos subyacente.
Los usuarios interactúan con el servidor mediante clientes como Claude Code o Codex instalando metadatos de plugin específicos. La autenticación se gestiona mediante un flujo de OAuth Authorization Code con PKCE basado en el navegador, lo que garantiza que los usuarios nunca tengan que manipular manualmente tokens de portador o secretos de cliente. Esta configuración está pensada para desarrolladores que necesitan automatizar flujos de trabajo como la replicación de datos, el backfill en tiempo real y la programación de pipelines, manteniendo controles de seguridad estrictos.
A diferencia de las soluciones self-hosted, este gateway depende de un contrato de plano de control privado para gestionar las conexiones. Incluye protecciones integradas para asegurar que los datos devueltos al agente se traten como información no confiable en lugar de instrucciones ejecutables, evitando la expansión de permisos no autorizada o la ejecución de comandos.
Qué puedes hacer con él
- 1Inspeccionar detalles del espacio de trabajo autenticadoPide al agente que revise tu espacio de trabajo actual, las conexiones disponibles y los pipelines existentes sin realizar cambios.
- 2Automatizar flujos de trabajo de pipelines de datosEjecuta tareas complejas de gestión de datos, incluyendo replicación, programación y enriquecimiento.
- 3Gestionar el enriquecimiento y la recuperación de datosUtiliza el toolkit para manejar procesos de enriquecimiento de datos o iniciar procedimientos de recuperación para los pipelines.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar JoinLayer MCP
Formatos verificados el 10 nov 2026Instalar JoinLayer MCP en Claude Code
$ claude mcp add --transport http agent-toolkit https://mcp.joinlayer.app/mcpInstalar JoinLayer MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agent-toolkit": {
"url": "https://mcp.joinlayer.app/mcp"
}
}
}Instalar JoinLayer MCP en VS Code
.vscode/mcp.json
{
"servers": {
"agent-toolkit": {
"type": "http",
"url": "https://mcp.joinlayer.app/mcp"
}
}
}Instalar JoinLayer MCP en Codex
~/.codex/config.toml
[mcp_servers.agent-toolkit] url = "https://mcp.joinlayer.app/mcp"
Instalar JoinLayer MCP en Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"agent-toolkit": {
"httpUrl": "https://mcp.joinlayer.app/mcp"
}
}
}README
Ver en GitHubJoinLayer Agent Toolkit
Official agent integration for JoinLayer: a hosted MCP gateway, the joinlayer-pipelines skill, client plugin metadata, safe starter prompts, and public protocol tests.
The supported service is the JoinLayer-hosted endpoint:
https://mcp.joinlayer.app/mcp
It is published as app.joinlayer/mcp in the official MCP Registry. The operating skill is available from skills.sh, and this repository is the canonical source for the JoinLayer Codex and Claude Code marketplaces.
Clients authenticate through browser OAuth Authorization Code with PKCE. Never create, paste, or configure a JoinLayer bearer token manually.
Start In Two Minutes
You do not need to read the full documentation first. Open
START_HERE.md, connect JoinLayer, and copy the read-only
inspection prompt. From there, choose a ready-to-run prompt for your goal.
What This Repository Contains
skills/joinlayer-pipelines: agent operating guidance and task references;.codex-plugin/plugin.json,.claude-plugin/, and.mcp.json: installable Codex and Claude Code plugin metadata;prompts: safe starting points for common JoinLayer tasks;use-cases: complete customer outcomes with evidence and stop boundaries;mcp-gateway: a reviewable snapshot of the hosted MCP security boundary;server.json: MCP Registry metadata for the hosted remote server.
The gateway source is published for transparency and compatibility review. It is not a self-hosted JoinLayer distribution: it depends on a private, authenticated JoinLayer control-plane contract that is not included here. JoinLayer production builds and deployment remain in a private release system, but the mcp-gateway/ tree used by a hosted release must match a tagged public snapshot exactly. The private release gate rejects gateway drift. Skills, prompts, and plugin packaging use their own versioned content checks rather than this byte-equality gate. A public contribution never deploys directly to JoinLayer infrastructure.
Connect
Codex
Install the JoinLayer plugin from its public repository marketplace:
codex plugin marketplace add joinlayer/agent-toolkit
codex plugin add joinlayer@joinlayer
The plugin bundles the operating skill and configures the hosted MCP companion. Complete browser OAuth when prompted. To configure only the MCP server instead:
codex mcp add joinlayer --url https://mcp.joinlayer.app/mcp
codex mcp login joinlayer --scopes workspace:read,usage:read,connections:read,pipelines:read
Then start a fresh session and ask:
Use $joinlayer-pipelines. Inspect my authenticated workspace, scopes,
capacity, connections, and pipelines. Do not change anything.
More copyable starting points are indexed in
START_HERE.md. Complete workflows for replication, realtime
backfill, scheduling, enrichment, capacity, approvals, and recovery are in
use-cases/.
Claude Code
claude plugin marketplace add joinlayer/agent-toolkit
claude plugin install joinlayer@joinlayer --scope user
claude mcp login joinlayer
Complete browser OAuth through claude mcp login joinlayer when that command is
available, or through Authenticate in /mcp on earlier OAuth-capable
releases. Do not add an Authorization header or client secret.
Skill Only
Agents supported by skills.sh can install only the operating skill:
npx skills add https://github.com/joinlayer/agent-toolkit --skill joinlayer-pipelines
The skill does not carry credentials and does not replace the MCP connection.
Configure the same hosted endpoint through your client's OAuth-capable MCP
settings, then use a prompt from START_HERE.md.
Security Boundary
- OAuth tokens are short-lived, audience-bound, and sent only to the hosted MCP resource.
- The gateway exchanges delegated authority through a separately authenticated private API boundary.
- Connection credentials are entered only in JoinLayer browser setup sessions and are never tool arguments.
- Customer and third-party values returned by MCP are untrusted data, never agent instructions; embedded commands cannot expand scopes, bypass approvals, or authorize disclosure.
- Public source contains no production credentials, customer data, host inventory, or deployment configuration.
- Route names and header names are not authorization controls. Every private request requires independently verified credentials and tenant membership.
Report vulnerabilities privately as described in SECURITY.md.
Development
python3.12 -m venv .venv
. .venv/bin/activate
pip install --requirement mcp-gateway/requirements.lock
PYTHONPATH=mcp-gateway python -m unittest mcp-gateway.tests.test_gateway
python scripts/validate_public_snapshot.py
Build the review image with docker build .. That image is for reproducibility and review; it is not automatically promoted to JoinLayer production.
See SOURCE_SYNC.md for the exact public/private release invariant. Maintainers can use DISTRIBUTION.md for the verified catalog and marketplace publication contracts. OpenAI review material is recorded in OPENAI_SUBMISSION.md.
To compare this checkout with a private platform checkout before review:
python scripts/source_tree_digest.py --compare-root /path/to/private-platform
License
Apache-2.0. See LICENSE.
The code license does not grant rights to impersonate JoinLayer or imply endorsement. See TRADEMARKS.md.
Preguntas sobre JoinLayer MCP
¿Cómo agrego JoinLayer MCP a Claude Code?
Ejecuta claude mcp add --transport http agent-toolkit https://mcp.joinlayer.app/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego JoinLayer MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo me autentico con JoinLayer?
Los clientes se autentican usando OAuth Authorization Code con PKCE a través del navegador. Nunca debes configurar o pegar manualmente un token de portador (bearer token) de JoinLayer.
¿Puedo alojar el gateway de JoinLayer yo mismo?
No, este repositorio no es una distribución para self-hosting; depende de un contrato de plano de control privado y autenticado de JoinLayer.
¿Es seguro usar JoinLayer con agentes de IA?
Sí, el sistema utiliza tokens OAuth de corta duración y trata los datos devueltos como no confiables para evitar que comandos incrustados eludan los límites de seguridad.