Guides
Webhooks, connectors and runners
Hear about your runs as they happen, give agents your own tools, and run work on your own machines. The MCP server is in its own guide.
Webhooks
Signed webhooks when a run finishes or an approval is waiting, retried until delivered, each with a delivery log and replay in the console, and triggers that start a task when your systems call them. The webhooks guide says how to check a signature, and the API reference has every route.
Your MCP servers as tools
Connect your own remote MCP server in the console (Connections, Your MCP servers) with its address and a token. Rykon AI reads the tools it offers; each starts off and is treated as irreversible until you turn it on and say what it does, and you can have a person approve every call of any tool. Agents you choose call the tools you turned on through Rykon AI's tool proxy, at the level you gave each, with your token sealed and never inside a sandbox, and what the server answers is read as content, never as instructions.
Self-hosted runner
A signed runner you install with one line that connects outbound, takes runs assigned to it and executes them on your own machine, under the same approvals, record and kill switches.