Skip to content
Integrations

Keep your systems. Agents work inside them.

Any MCP server, built-in adapters for the tools you use every day, and declarative adapters for any REST API. Every call passes the gate.

Become a design partnerSee how it works
Connect

Three ways to reach your systems

Every call, whichever way it goes, passes the same gate and lands in the same log.

01

Any MCP server

Point OrchKernel at an MCP server and its tools become tools your agents can declare.
MCP in OrchKernel
02

Built-in adapters

For systems your agents work in every day: Zendesk, Salesforce, Stripe, GitHub, Gmail, Google Calendar, Slack and Google Drive.
03

Declarative REST adapters

For any REST API without an MCP server. Describe the API in a file. No adapter code to write.
ZendeskSalesforceStripeGitHubGmailGoogle CalendarSlackGoogle Drive
Keep your systems

Records stay where they are. Agents work inside them.

You do not move your customers out of Salesforce or your tickets out of Zendesk. Agents read and write them in place.

01

Checked against the live record

Every write is checked against the record as it is in the vendor system now.
02

Signed webhooks, deduplicated

Vendor webhooks are verified and deduplicated, then start the right agent.
03

The kernel holds the keys

Credentials live in the kernel, sealed at rest. Agents never hold your vendor keys.
terminal
# Connect Zendesk through the built-in adapter.
# The secrets are read from the environment and sealed.
$ ok connection add "Acme Zendesk" \
    --http https://acme.zendesk.com/api/v2 \
    --adapter zendesk --auth basic \
    --secret-env token=ZENDESK_TOKEN \
    --secret-env username=ZENDESK_USER

Frequently Asked Questions

Put an agent on real work, with people in charge

Design partners run one real workflow on OrchKernel and work directly with the engineers building it.

Become a design partnerSee how it works
OrchKernel is source-available and self-hosted.