Skip to content
MCP

MCP servers today. A gateway for outside agents next.

OrchKernel uses MCP servers as tools for its agents. The MCP gateway lets the agents you already use act through the same gate.

Both directions

MCP out to your tools, MCP in from outside agents

Either way, every call passes the same gate and lands in the same log.

OrchKernel uses MCP servers

Connect any MCP server. Its tools become tools your agents can declare, and every call goes through the gate.

Your agent in OrchKernel
The gate
Any MCP server

The MCP gateway for outside agents

Claude, Cursor or your own agent connect to OrchKernel as an MCP server. They get their own identity and act only through the gate.

Claude, Cursor or your code
The MCP gateway
The gate
Your systems
The MCP gateway

Bring the agents you already use

Next to the governed actions API and its TypeScript and Python clients.

  • Each outside agent has its own identity and acts for a person.
  • It never holds your vendor keys. OrchKernel runs the approved action with its own credentials.
  • The answer to each call is allowed, needs approval or denied, with the reason.
  • Approvals show the exact payload, and the approved action runs once.

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.

OrchKernel is source-available and self-hosted.