MCP网关

Latchkey 是一个轻量级、无状态的 MCP 网关,用于发现下游工具、本地搜索并并发路由调用。

  • by blogle
  • Rust
  • 本地部署
  • 更新于
在 GitHub 查看 blogle/latchkey

使用说明

Latchkey

A lightweight, stateless MCP gateway: discover downstream tools, search locally, and route calls concurrently.

Status: requirements baseline; the MVP is not implemented. The old gateway/operator prototype is preserved on branch backup/pre-mvp-reset-2026-09-30 and annotated tag pre-mvp-reset-2026-09-30.

MVP requirements contains the supplied 2026-09-30 attachment plus the subsequently mandated standalone development and end-to-end testing requirement. The original attachment remains in the reset commit's history. This spec supersedes the old specification, roadmap and ADRs.

The MVP has one binary, one OCI image, exactly search and exec, SDK-owned MCP transport, a namespaced MCPService CRD, Secret-backed static headers, in-memory search, concurrent execution and OpenTelemetry. Replicas operate independently. The same binary must also run and pass end-to-end tests outside Kubernetes without any Kubernetes mocks.

Code Mode, OAuth delegation, per-user policy, persistence, durable events, stdio processes, admin UI and semantic search are deferred.

There is no runnable service, deployment or build pipeline in this baseline. Keep the existing Nexus path active until migration acceptance is demonstrated.