"A managed cloud provider that deploys my application" matching MCP servers:

Enables AI assistants and other MCP clients to launch and steer Cursor Cloud Agents on repositories or as repo-less research tasks, including model selection, mid-run follow-ups, cancellation, result retrieval, and run listing. Also exposes authentication checks and per-agent or per-run token usage and cost reporting.

Enables AI assistants and MCP clients to launch and manage Cursor Cloud Agents on repositories or without one, select models, follow up mid-run, retrieve or cancel results, and check usage and cost.

Enables Claude or any MCP client to drive the GitHub Copilot cloud agent via its REST API, allowing it to research, edit, and open pull requests on repositories without manual intervention.

Wraps MiniMax AI as an autonomous code executor for Claude Code, offloading coding tasks to save Claude subscription tokens.

A tiny Hermes-friendly bridge that exposes oh-my-pi's CLI as MCP tools (prompt and doctor) for code generation and environment verification.

Enables AI assistants to create and manage Cursor Cloud Agents that autonomously work on GitHub repositories, including creating tasks, monitoring progress, and automatically generating pull requests.

Enables programmatic control of Cursor's cloud-based AI agents for automated code generation and repository management via standardized MCP tools.

A hosted AI software engineer that writes code, opens PRs, reviews code, generates tests, runs security scans, and answers codebase questions. Connect from any MCP client (Claude Code, Cursor, Windsurf, or your own agents) and delegate engineering tasks.

A paid remote MCP server for OpenAI Codex harness, offering structured JSON tools for coding task planning, safe command suggestions, test verdict recording, and run history.

A personal AI coding assistant that connects to various development environments and helps automate tasks, provide codebase insights, and improve coding decisions by leveraging the Model Context Protocol.

Instant secure Full Stack Apps and AI Agents

An AI-agent-first framework for building MCP servers that deliver interactive React widgets directly within AI chat interfaces like ChatGPT and Claude. It includes automated visual testing and a zero-config local development environment designed for autonomous agent workflows.

Enables IDE integration with a multi-agent AI pipeline for solving, reviewing, and optimizing code through adversarial peer review and security filtering.

An authenticated OpenAI-compatible inference gateway with an async job broker that bridges a coding agent to a ChatGPT MCP worker, enabling ChatGPT to process inference requests via a tunnel.

Provides MCP tools to create, run commands in, checkpoint, and delete durable cloud environments, giving coding agents persistent state between calls.

A stdio MCP server that lets Claude Code delegate coding tasks to an OpenCode instance (optionally attached to an internal LLM gateway), with follow-up replies, status polling, output/diff retrieval, cancellation, and cleanup handled in a single session. It supports managed or attach modes, sandbox and approval policies, parallel fan-out delegations, and read-only review workflows.

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

MCP server that enables cloud models (like Gemini/Claude) to delegate coding tasks to a local llama.cpp server, preserving cloud usage limits through an AI-powered code review loop.

Enables Claude Code to delegate software-engineering tasks to OpenCode agents running in the same workspace/worktree, with the model and provider chosen per agent. Exposes tools for task delegation, persistent sessions, diffs, and agent listing so an orchestrator can research, edit, review, and test code.

Enables Claude Code to delegate coding tasks—investigation, review, long-running background jobs, and optional file edits—to a locally installed OpenAI Codex CLI, with the model and reasoning effort chosen per task and read-only execution by default. Follow-up requests reuse Codex's existing context, and write-enabled delegations can be confined to a managed git worktree so the user's own checkout stays untouched.