MCP↔EEP Bridge

The bridge maps MCP servers into EEP-native discovery, service catalogs, and gate-aware access flows so MCP tools can be consumed inside protocol-grade EEP deployments.

Implementations

• @eep-dev/mcp-bridge (Node.js)
• eep-mcp-bridge (Python)

Exposed bridge endpoints

Aligned with the Node bridge server routes (see @eep-dev/mcp-bridge):

• GET /.well-known/eep.json
• GET /eep/services
• GET /eep/gates
• POST /eep/subscribe
• GET /eep/stream (SSE)
• POST /mcp/tools/call (fail-closed gate enforcement)

Security baseline

• Tool-name validation + unknown tool rejection
• 402 fail-closed access path for gated tools
• Redteam suites in both runtimes

See also

• Reference deployment →
• IETF/W3C roadmap →