"A list of all remote servers" matching MCP servers:

A Model Context Protocol (MCP) server that enables remote access to OpenCode AI coding agent, allowing MCP-compatible clients to leverage OpenCode's capabilities.

Enables agent-style remote development over SSH with file operations and command execution, exposing native tools for searching, editing, and transferring files on remote machines.

Plori runs AI agents in Workspaces. A Workspace is a project folder in the cloud. Several agents can work in it at the same time, each on its own copy of the files, and Plori merges their work back into the folder. Every version of the files is kept.

Enables delegating coding tasks to isolated Claude Code subprocesses billed against a GLM Coding Plan, with tools to delegate, await, continue, list, cancel, and inspect runs.

Enables running one Codex CLI task at a time in an isolated temporary folder, returning Codex's answer and a manifest of produced files for manual review and selective copying.

Run DeepSeek as a real sub-agent inside Claude Code / Codex CLI — not just a single LLM call. DeepSeek gets its own 7-tool agent loop (Read/Write/Edit/Bash/Glob/Grep/NotebookEdit) inside a sandboxed workspace.

Enables remote control of AI coding assistants (Claude Code/Codex) via Telegram, allowing you to manage long-running tasks, send commands, and receive notifications from anywhere. Supports unattended mode with smart polling for up to 7 days and multi-session management.

An MCP server that lets AI coding assistants delegate work to Capy's cloud agents and wait for results, all within the editor.

Enables MCP clients to invoke Cursor SDK's agent runtime, run coding agents, list models, and continue conversations.

Provides AI coding agents a full abap2UI5 development loop—writing ABAP classes, validating views, deploying, and running apps headless with screenshots—all locally without an SAP system.

Enables Codex to delegate review and implementation tasks to the local Qoder CN CLI as background jobs, with two permission tiers and polling-based status updates.

A single, queryable source of engineering constraints that coding agents consult at code-generation time, exposed over an MCP server.

Enables handing one self-contained job to the Claude Code CLI on the local machine and getting back its final message plus a manifest of the artifacts it produced, without letting Claude write into the user's project. Reads are limited to named directories and all writes stay in a throwaway run directory, so the user reviews the listed files and copies in only what they approve.

Provides per-Subagent MCP controls to any coding agent or client across all your MCPs and prevents context window waste. Loads only 3 tools instead of all your MCP Server's tool definitions. Agents discover tools on-demand, only when needed and only the servers and tools they are allowed.

An MCP server that enables local AI models to receive guidance from remote 'senior' AI providers like OpenAI, Anthropic, and Gemini to solve programming problems. It features intelligent multi-turn dialogue management, context synchronization, and automated session history tracking.

Local MCP server that wraps the codex CLI asynchronously, returning a job_id immediately to avoid MCP protocol timeouts, and providing tools to start, poll, list, and cancel codex jobs.

Enables external agents to list T3 environments and projects, start coding threads, monitor progress, send follow-up instructions, and interrupt running turns via MCP.

Enables primary AI orchestrators to delegate token-heavy coding tasks to economical models via OpenRouter, running sandboxed autonomous ReAct loops with filesystem operations and git audit tools while reducing token costs.

Exposes the local Claude Code CLI as a subagent for Codex, enabling background review and implementation jobs with two fixed permission tiers.

Allow your AI coding agents to access Figma files & prototypes directly. You can DM me for any issues / improvements: https://x.com/jasonzhou1993 1. Access all figma pages 2. Access all figma components 3. Access figma prototype flows