One endpoint for every MCP server you run: MCPHub gathers local and remote Model Context Protocol servers behind stable URLs, so AI clients connect once and see what you allow. Claude Code, Cursor, and Cherry Studio can use four routes: everything at /mcp, a named group at /mcp/{group}, one server at /mcp/{server}, or semantic tool search at /mcp/$smart. Smart routing runs vector search on PostgreSQL with pgvector and an OpenAI-compatible key, so the model gets a shorter tool list. Servers attach over stdio, SSE, or streamable HTTP, OpenAPI services can be wrapped as MCP tools, and changes apply without downtime. In the other direction, MCP tools can be exported as an OpenAPI 3.0.3 spec for OpenWebUI and other OpenAPI clients. Bearer keys, OAuth 2.0 (client and server modes), and GitHub or Google sign-in in database mode control access, with per-user visibility for servers and groups. Encrypted per-user credentials let one shared server use each person's own key. Logs show tool-call activity, request status, and latency, health checks track each connection, and the dashboard controls which tools, prompts, and resources each server exposes. Large text tool results can be compressed, interactive MCP Apps are proxied through MCPHub routes, and a built-in market lets you browse a server catalog. Typical uses include a team-wide gateway, per-project groups, and direct single-server routes for debugging. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

MCPJungle puts every MCP server your AI tools use behind one endpoint, so Claude, Cursor, Codex, and your own agents all connect to a single gateway instead of a tangle of per-client configurations. Register remote HTTP servers and local STDIO servers once, and their tools, prompts, and resources become discoverable through the gateway in one place. Tool groups expose curated subsets at their own endpoints, so a coding agent sees only the tools its job needs instead of hundreds of irrelevant ones competing for context. The dashboard gives you a visual registry of servers, tools, and groups for everyday management, while the CLI and REST API cover scripting and automation. Development mode runs with zero authentication for a personal setup; enterprise mode adds per-client tokens that allow-list exactly which servers each client may reach. User accounts and manual server initialization give teams a governed shared deployment, with OpenTelemetry metrics showing what clients call and how the gateway performs. Upstream servers can authenticate with bearer tokens or OAuth, so credentials stay centralized in the gateway rather than copied into every client config. Registry data persists in a local file for solo use or in PostgreSQL when the gateway becomes shared team infrastructure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MPL-2.0 licensed.

With 2,600+ GitHub stars, MetaMCP solves the MCP server sprawl problem by aggregating any number of upstream servers into a single authenticated endpoint that any MCP client connects to once. Group servers into namespaces — development tools in one, data sources in another — then publish each namespace as its own SSE, Streamable HTTP, or OpenAPI endpoint with API-key authentication in headers or query parameters, or full OAuth per the MCP Spec 2025-06-18 standard. The aggregation engine discovers tools, resources, and prompts from all active servers in parallel, prefixes tool names with server identifiers to prevent collisions, and applies configurable middleware including tool filtering to reduce context-window bloat and description overrides to improve LLM comprehension. The web management UI lets you configure MCP servers with stdio, SSE, or Streamable HTTP transports, toggle servers active or inactive per namespace, create and revoke API keys per endpoint, and inspect discovered tools with their schemas. Nested MetaMCP support enables hierarchical architectures where one MetaMCP instance consumes another, creating multi-level tool organization with automatic name resolution. Compatible with Claude Desktop, Claude Code, Cursor, Open WebUI, and any MCP-compatible client through a single connection URL. The Docker container packages the TypeScript backend with PostgreSQL for configuration persistence, exposing the management UI on port 12005 and MCP endpoints on configurable ports. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

MCPProxy puts one safe endpoint in front of every MCP server your AI agents use, and it holds each new server in quarantine until a person approves it. Add stdio or HTTP servers on the Servers page, then review the captured tool definitions and scanner findings in the Review queue before any agent can call them. The Tools page lists every tool with a Read, Write, or Destructive tier, an approval state, and a usage count, plus switches to hide whatever you do not want exposed. Agents see a short set of discovery and call tools instead of the full catalog, and the Home dashboard estimates how much context that saves per request. The Activity Log records each call with its server, intent, status, and duration, and exports for audits. The Usage page charts calls per tool, response sizes, errors, latency, and activity over time, filtered by profile, client, or token. Profiles and agent tokens scope what each client may reach, a Secrets page keeps credentials out of config files, and a setup wizard connects Claude Code, Claude Desktop, Cursor, Windsurf, and VS Code. Platform teams and solo builders get one place to see and control everything their agents can touch. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Preloop is a self-hostable control plane that governs every AI agent tool call and model call, and can run ticket-triggered agent work that returns as reviewable pull requests. An MCP firewall can allow, deny, or hold any tool call for approval, with require-justification rules written as YAML and CEL policy. Human approvals arrive on mobile, watch, Slack, Mattermost, email, webhook, or the command line, and agents can ask a person a question before continuing. The model gateway speaks OpenAI, Anthropic, and Gemini formats, applies budgets and allowed-model lists, and attributes token spend by model, agent, session, API key, flow, and user. Flows start agents from GitHub, GitLab, Bitbucket Cloud, Jira, webhooks, or CI jobs, in hosted containers or on private runners that connect over an outbound WebSocket. Twenty-one presets review pull requests, implement issues, triage tickets, scan for vulnerabilities, and collect evidence packs. Operators can steer a running agent from the console, phone, or watch with notes, then review the resulting pull request. One session timeline records tool calls, model calls, policy decisions, approvals, spend, outcomes, and synchronized recordings. Fleet Map shows people, devices, agents, models, and observed work in one view. An account kill switch blocks gateway and tool traffic and stops managed runs, with audited recovery. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Backed by the Linux Foundation with contributions from AWS, Cisco, IBM, Microsoft, Red Hat, and Shell, Agentgateway is the first data plane built from the ground up for AI agent workloads — providing a unified Rust-based proxy that handles conventional HTTP and gRPC traffic alongside MCP tool servers, A2A agent communication, and LLM inference endpoints through a single deployment. The LLM gateway routes requests to OpenAI, Anthropic, Gemini, AWS Bedrock, and other providers through an OpenAI-compatible unified API with per-tenant budget controls, spend tracking, prompt enrichment, load balancing across multiple model endpoints, and automatic failover when providers experience outages. The MCP gateway federates multiple tool servers behind one endpoint, supporting stdio, HTTP/SSE, and Streamable HTTP transports with built-in OAuth authentication compliant with the MCP auth specification, integrating Auth0 and Keycloak out of the box. OpenAPI integration exposes existing REST APIs as MCP-native tools without code changes, enabling legacy services to participate in agent workflows. Policy-based RBAC controls which agents access which tools, while OpenTelemetry integration provides distributed tracing across agent communication chains. Deploy as a standalone binary with flat YAML configuration or on Kubernetes using the built-in controller with Gateway API support for declarative infrastructure-as-code management. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Send every AI request through one gateway that holds your model providers, API keys, and access rules. The web console starts with a first-run admin setup, then an LLM Provider page where OpenAI-compatible endpoints, Anthropic Claude, Azure OpenAI, Tongyi Qianwen, Moonshot, Zhipu, and other services are added with their tokens. AI Route Config maps path prefixes and model match rules to weighted target services, with token failover and first-packet timeouts to keep traffic moving when a key fails. Consumer Management issues key, OAuth2, and JWT credentials, and each route can limit access to named consumers. Plugin Management lists ready-made AI plugins for caching, context limits, data masking, prompt templates, prompt decorators, load balancing, and intent checks, plus traffic and security plugins that can be configured per route. MCP Management hosts MCP servers behind the same authentication and rate limits so agents call tools through one governed address. Service Sources import backends from Nacos, Zookeeper, Consul, Eureka, static addresses, or domains, and domain and certificate pages handle HTTPS, including free automatic certificates from Let's Encrypt. An LLM proxy for a product team, a shared model endpoint for several agents, or a replacement for an ingress controller all fit this console. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One gateway, every AI model: APIPark gives your applications a single, consistent API for OpenAI, Anthropic, Google Gemini, DeepSeek, and 100+ other models, and gives your team a portal to publish and share whatever gets built on top. Standardized request and response formats mean swapping a provider or rewriting a prompt never touches client code. Pair a model with a prompt template and it becomes a ready-made API for sentiment analysis or translation, listed in the developer portal with its own readme and generated API docs. Model Fallback swaps in the highest-priority available model when one misbehaves. API key balancing spreads traffic across several keys for the same provider. Already have REST services? Import an OpenAPI document, file the service under a category and tags, and let consumers subscribe, with optional manual review before anyone gets access. Any service can be switched on as an MCP tool that AI assistants can discover and call, and local open-source models can be deployed and exposed the same way. Usage charts follow requests, traffic, and tokens per service and consumer. Request logs flow out to files, HTTP endpoints, Kafka, NSQ, or Syslog. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Jentic One is a self-hosted execution layer that lets AI agents call real APIs through a broker that checks permissions and injects stored credentials, so agents do useful work without ever holding your API keys. You register the APIs an agent may use, store each credential once on your own infrastructure, and approve which agents can connect. Every call the agent makes passes the permission check first, and denied requests stop at the broker with a 403 instead of reaching the outside service. Allowed calls go out with the credential attached, and each one lands in an execution record you can review later. Cutting off a single agent takes one change in the control plane, with no key rotation across your other tools. Agents connect through the jentic CLI, a generated skill, an MCP server, or plain HTTP, so coding assistants and in-house agents share the same gate. The stack runs as two units over one database: the control plane on port 8000 for administration, and the broker data plane that agents call. Quickstart runs on SQLite for trials, and production setups move to Postgres with pinned images and TLS. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Every team building with coding agents has the same drawer problem: the best Skill, MCP server, or agent file lives in one person's repo, undocumented, while three colleagues rebuild it from scratch. Agentic Resource Registry is the internal catalog that ends the duplication, a self-hosted registry where your organization publishes Skills, MCP servers, hooks, prompts, agent files, and sandboxes in one searchable place. Browse by teamspace, publisher, category, or harness and see at a glance what each resource supports and how often it has been pulled. Authors build agent files in a four-step builder with a live summary and draft readiness checks, then submit them into a review queue where admins inspect the full prompt and version diffs before approving. Forking an approved release creates your own draft with pinned components, and reviewers can compare it against upstream line by line. The companion CLI installs any approved resource into Claude Code, Cursor, Codex, Kiro, Copilot, OpenCode, Pi, and more, generating the correct config for each harness automatically. Approved resources are also discoverable over the open ARD standard, so a running agent can hand part of its task to another approved agent or a remote A2A service. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

SkillHub gives teams a private, npm-style registry for AI agent skills, so a useful skill package is published once, reviewed, versioned, and installed into a compatible agent from the command line. Upload a package from the web console, the CLI, or the REST API, pick PUBLIC, NAMESPACE_ONLY, or PRIVATE visibility, and track releases with semantic versions plus tags such as beta and stable. Team namespaces keep their own members with Owner, Admin, and Member roles and publishing policies, while full-text search filters by namespace, downloads, ratings, and recency and hides whatever a user may not see. Every submission enters a review queue: namespace admins approve or reject team skills, platform admins decide promotions to the global scope, and each governance action lands in the audit log. A built-in Skill Scanner inspects published packages and shows its report on the skill page, with optional behavioral, LLM, VirusTotal, and Cisco AI Defense engines. Members can star and rate skills, follow download counts, receive notifications, and report problem packages. Skill suites bundle several skills into one versioned collection with an entry skill, scoped API tokens serve the CLI and scripts, and the interface speaks English, Simplified Chinese, Russian, and Korean. Packages live on local disk or S3-compatible storage such as MinIO. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

ToolHive is an open-source MCP server management platform that lets you run, secure, and orchestrate Model Context Protocol servers in isolated containers, giving AI agents structured access to tools like GitHub, databases, and cloud services without exposing host credentials or network. Every server launches inside its own sandboxed container with a minimal permission file, network access filtering, and encrypted secrets management, preventing misbehaving connectors from reaching beyond their defined scope. The built-in registry provides a catalog of vetted servers you can install with one command, while custom images and package-manager references let you onboard proprietary connectors without writing Dockerfiles. Platform teams deploy the Kubernetes operator to declare MCP servers as cluster resources using Custom Resource Definitions, with automated lifecycle management and multi-namespace isolation. The Virtual MCP Server gateway aggregates multiple backends behind a single endpoint, centralizing OIDC authentication, tool filtering, and composite cross-server workflows so clients connect once instead of juggling separate URLs. An MCP Optimizer analyzes tool schemas via semantic search and surfaces only relevant tools per request, cutting token consumption by up to 85%. OpenTelemetry traces and Prometheus metrics deliver full visibility into tool execution, latency, and request audit trails across every managed server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Unla puts a friendly front door on every API you already run, so AI clients can call it as an MCP server without anyone writing a line of glue code. Describe an endpoint in YAML or the form editor, name its arguments, choose where each one goes in the request, and the gateway exposes it as a tool over SSE or streamable HTTP. Import an OpenAPI file to generate a whole server at once, or proxy a third-party MCP server and route it under a prefix of your choice. The Gateway Manager shows every server as a card or table row with its routes, enabled tools, and tool counts. Every save creates a numbered config version with its author and timestamp, so changes are easy to audit and roll back. Tenants keep teams separate, user accounts carry roles, and CORS settings sit next to each route. Configuration hot reloads, syncs across replicas, and persists to disk, SQLite, PostgreSQL, or MySQL. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 5,000 GitHub stars since its June 2026 launch, OOMOL OpenConnector bridges the gap between AI agents and the real world by handling the authentication nightmare that stops LLMs from calling external APIs safely. The runtime connects to more than 1,000 SaaS providers — GitHub, Gmail, Notion, Slack, Microsoft, HubSpot, Google Workspace, and hundreds more — through 10,000+ prebuilt typed Actions that agents can discover and execute without ever touching raw credentials. OAuth2 flows, API key rotation, custom credentials, and no-auth providers are all managed centrally with AES-encrypted storage, scoped runtime tokens, and configurable action allowlists and blocklists that enforce least-privilege access. Agents interact through five access surfaces: the Model Context Protocol endpoint at /mcp for Claude and other MCP-capable hosts, a full REST API at /v1 for programmatic control, an auto-generated OpenAPI specification for code generation, a TypeScript SDK for application integration, and the oo CLI for local agent relay. The built-in Web Console provides browser-based administration for configuring OAuth apps, managing connections, inspecting action schemas, and reviewing execution logs with redacted inputs. Deploy via Docker Compose with SQLite for single-server setups, run from source on Node.js 22+, or push to Cloudflare Workers with D1 and R2 for edge deployment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Connecting autonomous AI assistants to internal enterprise databases and legacy systems is streamlined by AnythingMCP, a visual Model Context Protocol gateway with automated knowledge graph generation and granular access controls. Engineers can import OpenAPI specifications, Postman collections, SOAP WSDL files, or raw database credentials to generate standardized Model Context Protocol tools in minutes without writing custom code. The built-in knowledge graph automatically maps entity relationships across disparate databases and software platforms, teaching agents how to correlate customer records in CRM tools with live order histories in enterprise resource planning software. System administrators can enforce fine-grained access policies by restricting tool execution permissions to specific roles and scoping database operations to read-only queries with strict row limits. An interactive web console provides real-time tool inspection, payload testing, request tracing, and comprehensive audit logs that capture every upstream invocation with full parameter visibility. Enterprise teams can integrate identity providers through OAuth2, SAML single sign-on, and SCIM automated user provisioning while protecting sensitive credentials using AES-256-GCM encryption at rest. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GNU AGPLv3 licensed.