Search Results for "http-client"

...It combines multiple MCP building blocks into one system, including hosting for MCP servers, a registry for discovery, a gateway layer to route access, and a standards-compliant chat client experience. The project is aimed at solving common enterprise rollout problems such as reliably hosting servers for internal and external users, curating “approved” MCP servers for employees to find, and enforcing authentication, access control, and auditable activity. It also supports building richer agents and chatbots that can leverage MCP servers while keeping operations manageable for IT and platform teams. ...

...It also includes observability with built-in metrics, tracing, logging, and supports governance features like rate limiting, access control, and cost budgeting. The architecture is modular: there is a core engine, plugin layers, and transport layers (HTTP APIs).

MetaMCP is an all-in-one MCP aggregator, orchestrator, and middleware that merges many MCP servers into a single, policy-aware server you can point any MCP client at. It’s built to centralize discovery, apply middlewares (e.g., auth, rate limits, transforms), and present a unified catalog of tools and resources from diverse backends. The repository and site describe it as “the one MCP to manage all your MCPs,” with diagrams and examples showing how to compose fleets behind a single endpoint. ...

...By integrating with Envoy and advanced data planes, it handles modern ingress concerns such as traffic routing, authentication, authorization, rate limiting, and observability for traditional HTTP/gRPC services and AI workloads alike. Beyond standard API traffic, kgateway also supports gateway patterns tailored for large language model (LLM) consumption, inference routing, and Model Context Protocol (MCP) orchestration, enabling secure access to models, tools, and agent interactions.

Unla is a lightweight, highly available MCP gateway written in Go that turns existing MCP servers or ordinary HTTP APIs into MCP-compliant services through configuration, not code changes. Its goal is to let teams “wire up” tools they already run—internal REST endpoints, third-party APIs, or local MCP servers—and present a single, reliable MCP interface to clients like Claude Desktop, Cursor, and IDEs. The gateway focuses on operational concerns you’d expect in production: multi-instance availability, health checking, and declarative routing that maps upstreams to MCP tools and resources. ...

...The core idea is to treat MCP servers like containerized services, giving each server controlled privileges and a lifecycle you can inspect, enable/disable, and reset as needed. Instead of having each AI client manage its own MCP server configuration, the gateway provides a unified interface so multiple clients can connect consistently to the same configured tool surface. The project emphasizes security and operational hygiene by supporting secrets management (to avoid leaking credentials via plain environment variables) and providing built-in OAuth flows for MCP servers that require authenticated service access.