# Governed at the edges, open in the middle.

**Governed at the edges, open in the middle.**

KrewOS is not trying to become your integration layer. It calls the systems you already run, and exposes governed crews to the assistants and workflow tools your teams already use — with policy, evidence and approval enforced by the runtime rather than by the caller.

Integrations

[Read the integration docs](/docs) [For engineering](/role-eng)

## Model Context Protocol, in both directions.

**KrewOS as an MCP server**

Your deployed crews are callable as standard tools by external assistants. Governance travels with the crew: the evidence floor, approval gates, budget ceilings and audit recording are enforced by the runtime, never by the calling interface. An assistant cannot ask a crew to skip its approval gate, because the gate is not part of the interface it can see.

**KrewOS as an MCP client**

Approved external MCP servers are consumable as Tools under the same registry, permission and audit controls as any first-party Tool. Administrators can withhold individual tools from a server while admitting the rest — a server is not an all-or-nothing trust decision.

| | Tools | Actions |
| - | - | - |
| **What they do** | Read or compute. No externally visible change. | Cause an external side effect — send, post, write, pay, publish. |
| **Idempotency key** | Not required | Required |
| **Compensation behaviour** | Not applicable | Must be declared |
| **Approval gate** | Optional | Required where configured, and required by the compiler on any untrusted-input path. |
| **Checkpointing** | On node boundary | Before and after the effect |
| **Replay behaviour** | Re-executed freely | Never re-executed; the recorded result is reused |

## n8n is a first-class adapter, not a competitor.

A crew can call a governed n8n workflow as an Action, and n8n can start a deployed crew through an authenticated API or an event. We are not rebuilding four hundred connectors, and you should be suspicious of anyone who says they have.

**Crew calls n8n**

Registered as an Action with an idempotency key and declared compensation. The workflow’s effect declaration is part of the crew’s compiled proof.

**n8n calls the crew**

Authenticated API or event trigger. The crew still runs its gates, and the n8n caller waits or receives a webhook when the human step completes.

**Direct integrations**

REST, webhooks and read-only database connectors where a workflow tool would just be a hop. All under the same permission registry.

## Bring your own key.

Platform-managed or tenant-managed credentials, held as encrypted secret references and injected at call time by the gateway.

Keys never appear in prompts, logs, manifests, exports, error messages or support tooling. A support engineer with full impersonation cannot read a tenant key, because the plaintext is never in a surface impersonation can reach. Model profiles declare which credential set they may use, so a crew cannot silently fall back to a platform key when your key rate-limits — it fails, or degrades to a declared fallback profile you approved.

anthropic openai google-vertex azure-openai aws-bedrock self-hosted-openai-compatible

Under BYOK, model consumption is billed by your provider directly and your KrewOS credits cover only platform runtime. Two meters, one wallet — and the second meter reads zero. [How credits work →](/credits)

**Git, Claude Code and Codex**

Export an engineering-ready repository — manifest, components, schemas, prompts, policies, evaluations, tests, deployment files and agent instruction files. Linked projects round-trip through a diff and approval workflow; ejected projects are yours outright. [For engineering →](/role-eng)

**Identity**

OIDC and SAML single sign-on with enforced MFA and role mapping from your IdP groups. SCIM user provisioning is on the roadmap and is not shipped today; we will not list it as available until it is. [Security details →](/trust/security)

---

Canonical page: https://dev.krewos.ai/integrations