Search Results for "libamd.so.1"

Call all LLM APIs using the OpenAI format [Anthropic, Huggingface, Cohere, Azure OpenAI etc.] liteLLM supports streaming the model response back, pass stream=True to get a streaming iterator in response. Streaming is supported for OpenAI, Azure, Anthropic, and Huggingface models.

...It offers a “single source of truth” registry where developers can register MCP servers and the tools they provide, and MCP clients (such as AI agents) discover and consume those tools through one gateway endpoint. This greatly simplifies the architecture when you have many MCP servers; agents only need to connect to one gateway rather than multiple endpoints. The platform supports enterprise-grade workflows; centralized tool management, access control, self-hosting so that internal servers and tools remain under your organization’s control, and registry metadata to track what tools exist and who can use them. ...

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. ...

...It positions itself as more than a typical VPN; it supports zero-trust network access (ZTNA), “BeyondCorp”-style access, API/AI gateway functionality, and even serves as a PaaS-like deployment surface. One of its key strengths is identity-based, application-layer (L7) aware control, meaning access decisions are made per request, with context and policy rather than simple network-level allow/block rules. It supports both client-based (e.g., WireGuard/QUIC tunnels) and client-less access models, which makes it flexible for both human users and automated workloads. ...

Obot is an open-source platform built to help organizations adopt and operate Model Context Protocol (MCP) capabilities in a centralized, production-friendly way. 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. ...

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...

Docker’s MCP Gateway project is a Docker CLI plugin and supporting gateway system designed to run, manage, and securely expose MCP servers using container isolation. It underpins the MCP Toolkit experience in Docker Desktop, but it can also be used independently as a general-purpose MCP operational layer. 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...