Cloud Agent
Delegate implementation work to a remote AI software engineer from your IDE agent—code changes, pull requests, reviews, and test generation via Cloud Agent MCP.
Overview
Cloud Agent is a MCP server for the Build phase that lets your local agent invoke a hosted AI software engineer to write code, open PRs, review changes, and generate tests.
What is this MCP server?
- Remote AI software engineer: writes code, opens PRs, reviews code, and generates tests from agent-driven prompts
- npm mcp-server-cloud-agent (v1.1.1) over stdio for Claude Code, Cursor, and similar clients
- Authenticated with CLOUD_AGENT_API_KEY (ca_ prefix) from the Cloud Agent web workspace
- Optional CLOUD_AGENT_URL override (default hosted backend: agent.leddconsulting.com)
- Offloads heavy implementation loops while you stay in local orchestration and product decisions
- Registry version 1.1.1
- npm package mcp-server-cloud-agent with stdio transport
- Default backend URL documented as https://agent.leddconsulting.com
What problem does it solve?
You are one person trying to ship a SaaS or agent product, and local AI assistance runs out of steam when tasks need multi-file PRs, reviews, and test coverage.
Who is it for?
Solo developers who already use Cloud Agent workspaces and want PR-level coding help exposed as MCP tools in Claude Code or Cursor.
Skip if: Builders who only want lightweight inline completions with no external service, API key, or PR-based workflow.
What do I get? / Deliverables
Your IDE agent can trigger Cloud Agent workflows so implementation, PRs, reviews, and tests progress on a remote engineer while you direct priorities from MCP.
- Agent-triggered code changes and pull requests via Cloud Agent
- Review feedback and test generation routed through MCP tool calls
- Configurable backend URL for default or custom Cloud Agent deployment
Recommended MCP Servers
Journey fit
Cloud Agent accelerates writing and iterating on code, which is core Build work even when it also touches review-like tasks. Agent-tooling captures an MCP bridge to an external coding agent workspace, not your app’s frontend components or launch SEO.
How it compares
Hosted AI engineer MCP bridge—not a local-only edit skill or a generic git CLI wrapper.
Common Questions / FAQ
Who is Cloud Agent for?
It is for indie builders and small teams who use Cloud Agent’s web workspace and want their MCP client to delegate coding, PRs, reviews, and tests to that service.
When should I use Cloud Agent?
Use it during Build when you are actively implementing features and need an external AI engineer to produce PRs and tests while you orchestrate from your agent.
How do I add Cloud Agent to my agent?
Install mcp-server-cloud-agent, set CLOUD_AGENT_API_KEY (ca_*) from your workspace, optionally set CLOUD_AGENT_URL, register stdio in your MCP config, and restart your client.