Octopus remote MCP: deploy/operate without a local install
At a glance
Octopus Cloud ships a built-in HTTP MCP at /mcp so coding agents can list spaces/projects, check PR deployment status, create/promote releases, run runbooks, search task logs and audit events—no per-machine local MCP to install; Server gets it in 2026.3. This workflow is listed under MCP, deploy, platform-ops, devtools, agent-governance.
Official Pantheon MCP lets Claude Code/Cursor/Desktop inspect workspaces, sites, environments, builds, deploys, runtime logs, upstreams and secrets under your Pantheon identity; reads by default, state-changing tools pause for explicit approval; no deletes in beta.
OutSystems MCP is GA on every ODC tenant: Claude Code/Codex/Cursor/Kiro can hand work to Mentor for apps/agents/workflows/libraries, query the estate, publish/promote/roll back, and keep ODC roles, approvals and audit—install from github.com/OutSystems/outsystems-mcp.
Local-first Apache-2.0 CLI for Claude Code/Codex/Cursor: mcp-xray ranks bloated tool schemas, sync compresses CLAUDE.md↔AGENTS.md↔Cursor rules, and shield fails CI on leaked keys/prompt-injection/Trojan Unicode—claims large cuts in model-visible prompt size without API calls.