Developer · Local MCP server
Cloud Agent
AI software engineer — writes code, opens PRs, reviews code, generates tests, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.joepangallo/cloud-agent- Version
- 1.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-21
- Updated
- 2026-03-21
- Publisher
- joepangallo (GitHub) · 8 servers with pages here
- Repository
- github.com/joepangallo/mcp-server-cloud-agent
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-server-cloud-agent | 1.1.1 | stdio |
How to connect Cloud Agent
Cloud Agent runs locally from a Node.js package published to the npm registry: mcp-server-cloud-agent version 1.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y mcp-server-cloud-agent@1.1.1. It reads these environment variables: CLOUD_AGENT_API_KEY (required, secret) and CLOUD_AGENT_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cloud-agent": {
"command": "npx",
"args": [
"-y",
"mcp-server-cloud-agent@1.1.1"
],
"env": {
"CLOUD_AGENT_API_KEY": "<secret>",
"CLOUD_AGENT_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from joepangallo (GitHub)
| Server | Runs |
|---|---|
| Agent PayPayment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools. | Local · stdio |
| MCP Audit ServerThin MCP and CLI proxy for AI agent and MCP security auditing via a hosted backend. | Local · stdio |
| MCP Server Agent AnalyticsTrack AI agent fleet performance, costs, anomalies, and trends. | Local · stdio |
| MCP Server IndexforgeSubmit URLs to Google and Bing for indexing, scan sitemaps, check index status. | Local · stdio |
| MCP Server Research SignalsScored trend intelligence from HN, Reddit, ArXiv, and GitHub. | Local · stdio |
| MCP Server Security AuditScan websites for security vulnerabilities, headers, TLS, and email security. | Local · stdio |
| Web Recon AgentOwned-target web security assessment MCP server for authenticated, high-friction apps. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| ClizeReal-world actions for AI coding agents: an inbox with approval outbox, deploys, domains, payments. | Local · stdio |
| CloakBrowser MCPPlaywright MCP-compatible browser automation bridge for CloakBrowser Chromium. | Local · stdio, HTTP |
| CloakcheckScan a page for hidden prompt-injection payloads targeting AI agents. | Remote · HTTP |
| CloakMCPStealth browser MCP server — anti-detection Chromium with snapshot-first agent interface. | Local · stdio |
| Cloud Armor WAF Patrol MCPMCP server for Google Cloud Armor WAF log patrol: deny summaries and false-positive checks. | Local · stdio |
| Cloud Cost Landmine LintNames every line in the file you have open that starts a recurring cloud charge, with the published. | Local · stdio |
| Cloud DevOps MCP ServerCloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations. | Local · stdio |
| Cloud FinOps Skill & MCPCloud cost + FinOps knowledge for AI agents: AWS/Azure/GCP optimisation, AI spend, waste playbooks. | Remote & Local · HTTP, stdio |