OutSystems MCP GA: build, ship, and operate ODC from your coding agent
At a glance
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. This workflow is listed under MCP, low-code, platform-ops, enterprise, devtools.
Agents / tools
OutSystems MCP, Mentor, Claude Code, Codex, Cursor, AWS Kiro, MCP
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.
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.
Enterprise GA for cg-oci, cg-apk, cg-versions, and cg-api so Claude Code/Cursor agents verify image tags, Wolfi package equivalents, EOL status, and org policy/attestations via browser OAuth or chainctl—server-side caps instead of prompt guardrails.