"Information about MCP Proxy" matching MCP servers:

A gateway server that enables agentic hosts to access multiple MCP servers through a single namespaced connection or proxy a specific server from MCP-Hive. It provides built-in discovery tools to list available servers, tools, and resources for seamless integration.

Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.

A meta-MCP server that acts as a single connection point to lazily spawn and proxy multiple MCP servers, reducing context bloat and process overhead.

Search and discover AI agents, skills, prompts, bundles and MCP connectors from a curated catalog of 4500+ assets. Provides tools for searching, browsing categories, and accessing detailed information about each asset.

Authenticates with Databricks via OAuth and exposes remote MCP tools from Databricks applications, enabling interaction with Databricks-hosted tools through Claude.

An MCP server that acts as a proxy to connect MCP clients to agent frameworks like Mastra and LangGraph, enabling agent discovery, dynamic server connections, and recursive agent networks.

A single MCP server that provides dynamic access to thousands of APIs through discovery and proxy, eliminating the need to install and configure multiple separate MCP servers.

A bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.

Accepts incoming websocket connections and creates unique POST API endpoints for each one, enabling classix to interact with MCP tools.

Enables deploying a secure MCP gateway that proxies, sandboxes, and policy-governs third-party MCP servers, with credential vaulting and audited tool access across stdio, SSE, and Streamable HTTP.

A thin MCP proxy that connects LLM clients like Claude and ChatGPT to Viraly's platform API, enabling AI agents to perform actions via natural language.

A proxy MCP server that aggregates tools from multiple MCP servers and forwards calls to the appropriate server, used with the Metatool App for GUI tool management.

A central hub that aggregates multiple MCP resource servers into a single unified interface, enabling users to access tools and capabilities from multiple backend servers through one connection point.

A tasks and projects board MCP server for agents, providing create, list, and status update tools with agent-scoped access via control-plane proxy.

Authenticating reverse proxy for MCP servers providing credential isolation, OAuth2 token management, and composite tool aggregation.

A proxy that reduces context token waste by exposing meta-tools (search_tools, load_tool, unload_tool) so the agent loads only needed tool schemas instead of all upstream tools.

Acts as a stdio proxy that answers initialization and list requests instantly from cache and starts real MCP servers only when needed, keeping hosts responsive despite slow upstreams.

Exposes only two meta-tools that discover and invoke backend MCP servers on demand, reducing context bloat while keeping all configured tools available.

Proxies STDIO-based MCP clients to streaming HTTP MCP servers, enabling local clients to connect to remote servers.

A proxy server that converts Model Context Protocol (MCP) messages to Simple Language Open Protocol (SLOP) messages, allowing MCP clients like Claude Desktop to interact with SLOP-compatible servers.