AgentDock turns the computers and servers you already run into machines an AI assistant can operate for you through one secure MCP endpoint. Connect ChatGPT, Claude, Codex, or any other MCP client and the agent works in the real environment: reading and writing files, searching code, running shell commands, and driving Git where the project actually lives. Long jobs survive interruptions because task state and checkpoints persist on the node, ready to resume where they stopped. Browser work is covered as well, with web pages driven through a native Chrome DevTools connection that reuses your logged-in sessions, captures screenshots, and can even operate macOS desktop applications. Capabilities grow through installable Skills and dynamic MCP servers, so a node picks up new tools without a rebuild. Run a single node on a laptop, or spread nodes across VPS hosts and containers and pair them with the optional NexusDock console for one fleet view, shared Recall memory, reusable workflow templates, and a single MCP address for every machine. Access stays locked down with Bearer tokens or OAuth sign-in, loopback-only defaults, and optional Cloudflare Tunnel or HTTPS exposure when a remote client needs a way in. 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.

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.

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.

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.

Your pi agent is mid-refactor on the server at home, you are on a train with only a phone, and Pi-Remote is the self-hosted relay that puts that live session in your browser so the work does not wait for your desk. Output, tool calls, and status changes sync in real time, with incremental catch up after a reconnect, and the session itself never leaves the local pi process. Send messages while pi is busy and they queue or steer, with delivery confirmed; switch the model or thinking level, compact the context, fork or clone a session, and walk the session tree, all executed locally. Several machines share one relay, and the UI lists each device, its online state, and its sessions, and can start a new session on the device you pick. Link a device by scanning a QR code, checking the 2 digit code on the confirmation page, and approving with the admin token. Desktop and mobile get separate layouts with six skins in Cursor, Claude, and Codex looks, dark and light, and token and cost usage updates in the status area. At home the relay can run serverless over the LAN, with a Cloudflare Tunnel switched on when you leave; on a server it runs under systemd or Docker Compose, and a device stays reachable only while its attach window is open. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

AgenTerm lets your AI agent work inside a remote computer's terminal with the owner's permission, through a relay server you host yourself. Your agent connects to the server over MCP and creates an invitation, single-use and expiring in fifteen minutes by default, or reusable across several devices; you privately share the generated connection command with the person who needs help. That person runs a small client on macOS, Linux, or Windows, reads what access means, and authorizes it; the client then dials out to your server, so the target computer needs no SSH service and no open inbound port. The agent can then run one-off commands with a chosen working directory, environment overrides, and timeouts, receiving stdout, stderr, and exit status, or hold an interactive session open, reading output as it arrives and typing answers to prompts. The person at the keyboard watches every command and its output in the client and can disconnect at any moment, and the client reconnects by itself after a network drop. Use it to troubleshoot a colleague's machine without swapping logs, help family through a terminal problem, or drive a development box with no agent or model account of its own. The relay itself is a single Go binary guarded by a management key, deployed with Docker Compose or systemd, with in-memory sessions and a health endpoint. 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.

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.

Pi Web is a browser interface for the Pi coding agent ecosystem, providing a visual workspace that reads the same local configuration and session files as the CLI. The session workspace groups conversations by project with running state indicators, context usage percentages, cost tracking, and compaction details, while two branching modes let users create independent session files from earlier messages or fork branches within existing sessions to explore alternative coding directions. Real-time streaming via Server-Sent Events delivers agent responses with structured Markdown rendering, thinking steps, tool call visualization, and image drag-and-drop input. The project file explorer browses working directories with syntax-highlighted source preview, Git diff inspection, and rendering for Markdown, images, audio, PDFs, and DOCX files with automatic refresh. Git worktree support switches checkouts from the sidebar while keeping sessions from the same repository grouped together. The Models panel manages provider authentication via OAuth and API keys, model selection, model smoke tests, and models.json configuration shared bidirectionally with the CLI agent. The Skills panel lists, searches, installs, and toggles agent skills without terminal access. The interface ships with English and Simplified Chinese translations, light and dark themes, a chat minimap, keyboard shortcuts, and completion sounds. Basic Auth protects remote access when binding to non-loopback addresses. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

WebCodex gives ChatGPT, Claude, and other MCP clients a real development environment on machines you own, so an AI assistant can edit your actual repositories instead of a pasted snapshot. A self-hosted Server authenticates every request and routes it to a Runner sitting next to your code, where file edits, Git operations, test runs, shell commands, and long jobs execute with your real toolchain. Your projects never move into a hosted workspace; only the tool results you authorize travel back to the model. The browser Runtime Console shows project readiness, the work queue, session activity, and connected Runners, and it is where you decide pending approvals or accept and reject finished work, because the model cannot approve its own changes. Runners join with a short-lived pairing code and stay connected over QUIC, WebSocket, or polling, so machines behind NAT still work. One-command sharing opens a temporary session for a single repository, while durable setups run the Server and Runner as system services behind your own HTTPS domain. Workflow Sessions keep evidence and context across conversations, so long tasks survive closed browser tabs and threads you pick up days later. 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.

Close the laptop, walk away, and your coding agents keep working; CodeRail is the remote control that lets you supervise them from a browser or your phone without handing your machines to anyone's cloud. A small bridge on each computer connects outbound to your server, so there are no open ports and no VPN to babysit, and each machine keeps its own Claude Code and Codex logins because CodeRail never holds your AI keys. Chats show plans, tool calls, models, modes, and background tasks, and when an agent wants to run something sensitive, the approval lands with you wherever you are, including as a phone push notification. Real terminals outlive the browser tab, files can be viewed, edited, uploaded, and downloaded in place, and git work, pull requests included, sits beside the conversation that produced it. Each chat even gets a browser on the computer itself, shared live with everyone in the chat and drivable by the agent. Roles run Owner, Operator, or Viewer per computer, narrowed down to folders and agents, with every change audited, and sessions keep running with every browser closed while history stays readable offline. 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.

Describe the outcome once, in plain language, and a small crew of AI agents divides the work between them and reports back in the same chat. You type the request in the team chat; Boo Zero, the team lead, splits it into jobs on a shared board and hands each card to the teammate best placed to do it. Teammates run on Claude Code, Codex, Hermes, OpenClaw, or Clawboo's built-in runtime, and one team can mix them freely, so the researcher, the writer, and the coder can each work on their strongest tool. You follow every card live on the board and in the chat, watch the team graph to see who is doing what, and add a reviewer agent when a second pair of eyes matters. Finished work returns to Boo Zero, which pulls the pieces together and answers you in the chat. Ready-made teams from the marketplace cover marketing squads, dev teams, and research crews, and you can bring an API key from Anthropic, OpenAI, OpenRouter and more, a free local model through Ollama, or your ChatGPT subscription through the Codex CLI. Spend is tracked per team with budget warnings before costs surprise you. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Running AI agents in production takes more than a model call: Omnara supplies the durable runtime, tools, approvals, and complete event history around any model, on your own machines. You define an agent once in a small YAML file: instructions, a model from OpenAI, Anthropic, OpenRouter, Bedrock, LiteLLM, Ollama, or your own endpoint, and the machines it may use. Launch agents from the REST API, the TypeScript SDK, the command line, or the dashboard, then stream every event live or receive it as a webhook while the agent works. Agents run shell commands and edit files on sandboxes from twelve providers, or on your own laptops, VMs, and containers through a daemon that connects outward, so no inbound ports or SSH keys are exposed. Every step is written to Postgres as an event log, which means an agent survives crashes, restarts, and disconnected machines and resumes exactly where it stopped. Tool permissions can run immediately, ask a person first, or block outright, and agents can start subagents, follow cron schedules, and keep shared memory files between conversations. Teams meet the agents where they already talk: mention the bot in Slack or Discord, or let a GitHub pull request trigger a review, with questions and approvals handled in the thread. 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.

Open Agent Builder delivers a visual canvas for orchestrating AI agent workflows without writing Python scripts or managing complex codebases. The React Flow-powered drag-and-drop interface supports seven node types — Agent, Scraper, Transform, If/Else, Loop, User Approval, and MCP Tool — each configurable with provider-specific settings for Anthropic Claude (Haiku 4.5 and Sonnet 4.5), OpenAI GPT-5, Groq, or any OpenAI-compatible endpoint. The LangGraph orchestration engine handles state management, conditional routing, and human-in-the-loop approval gates while Firecrawl integration converts any website into structured, LLM-ready data through scrape, crawl, and map operations. E2B sandboxed code execution powers Transform nodes for secure data manipulation without risking host system integrity. Real-time streaming updates show execution progress node-by-node as workflows run, with Convex providing reactive database synchronization for workflow state and execution history. The TypeScript-first architecture (96.8% TypeScript) built on Next.js 16 App Router with Tailwind CSS delivers a responsive interface across devices. Clerk handles multi-user authentication with JWT integration for secure workspace isolation. Deploy via npm install and environment configuration with Firecrawl, Convex, and Clerk API keys. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.