Connect Claude, ChatGPT, Cursor, or your own agent to your enterprise apps — without giving it an ungoverned backdoor.
Most "connect your agent" integrations hand the model a raw API key and hope. The Governed Agent Gateway is the opposite: a single northbound path an external agent calls, where nothing reaches your systems except through the same governance every ReDevOps mission runs under. We govern the capability boundary and every operation performed through it — not the agent's hidden reasoning, which no one can.
Whatever protocol delivers the request, it crosses exactly one path — there is no protocol-specific bypass:
identity → permissions / ABAC → risk tier → budget → approval gate → GovernedEnvelope → invoke (a governed capability, or a delegated Mission) → egress policy → verification → evidence + audit → response
Point any MCP client at the gateway, or call the REST delegation API. Authentication is OAuth 2.1 + PKCE in production; a scoped bearer for a read-only slice. The live demo exposes a read-only surface over the sample Projects workspace:
# discover the capabilities your principal is permitted to see curl https://demo.redevops.io/projects/api/agent-gateway/capabilities \ -H "Authorization: Bearer <token>" # call one — over the REST delegation API… curl -X POST https://demo.redevops.io/projects/api/agent-gateway/capabilities/missions.list/invoke \ -H "Authorization: Bearer <token>" -d '{}' # …or over MCP (tools/list · tools/call) curl -X POST https://demo.redevops.io/projects/api/agent-gateway/mcp \ -H "Authorization: Bearer <token>" \ -d '{"method":"tools/call","params":{"name":"projects.list"}}'
Self-hosting? The gateway ships in agentic-os; a turnkey MCP Streamable-HTTP server is one pip install 'agentic-os[mcp]' away, and the same governed path backs it. Ask in #agentic-apps for a demo token.
Semantic capabilities, not raw CRUD. Read is open by default; writes and goal-delegation are governed and, on the hosted demo, held back to a read-only slice:
projects.list, projects.get_status, missions.list / get / explain, sources.search.missions.delegate_goal: hand ReDevOps a goal; it plans and runs a governed mission, gating its own side effects on your approval.prepare_* / request_* pattern (e.g. draft outreach, then request-send): approval-gated, idempotent, reversible.What an agent (or a mission) can reach is the connector catalog — each adapter a governed capability behind one contract, and each connectable in plain language through the Connect Compiler (describe an integration, confirm, the runtime wires it).
| Area | Connectors |
|---|---|
| CRM & billing | HubSpot · Stripe · Polar |
| Messaging & email | Gmail · Google Calendar · Slack · WhatsApp Business (Meta Cloud API) |
| Marketing & social | Klaviyo · Postiz · Ayrshare · Blotato |
| Productivity plane | Google Workspace · Microsoft 365 · LibreOffice · file formats (CSV/MD/XLSX/DOCX) |
| Sources (evidence) | Google Drive · OneDrive · Postgres · ReDevOps RAG |
Credentials follow a three-owner boundary: the OAuth app secret stays in the connect layer, your account token lives in the CredentialBroker, and a mission or the model only ever sees an opaque reference resolved at the moment of use — never the secret itself.
Want to connect your agent? Ask in #agentic-apps on the ReDevOps Slack, or email info@redevops.io — we'll set you up with a scoped token and the endpoint for your workspace.