Integrations
The Integrations section is where Agirunner connects to external systems instead of pretending everything lives inside one runtime.
Current Focus
Section titled “Current Focus”The most prominent integration surface today is remote MCP servers.
Operators can:
- register a remote server
- verify connectivity
- configure OAuth client profiles
- inspect discovered tools
- make those tools available to specialists through platform-managed policy
In the current product, that integration flow spans both UI and API surfaces:
- remote MCP server records
- verification and re-verification
- OAuth reconnect or disconnect flows
- client-profile lifecycle management
- discovered-tool inspection
That makes MCP one of the clearest examples of Agirunner’s platform/runtime boundary in action. The platform owns registration and policy; the runtime later consumes the granted tool surface.
Other Integration Surfaces
Section titled “Other Integration Surfaces”The dashboard also has dedicated route surfaces for Triggers and Webhooks. Those surfaces matter because many teams will want Agirunner to react to upstream events and emit downstream events instead of staying inside a manual-only workflow model.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Integrations are how Agirunner stops being a closed box:
- MCP Servers connect external tool surfaces that specialists can use during execution
- Triggers And Webhooks connect the workflow system to upstream and downstream automation
- API Keys and the API Reference provide the credential and contract layer for non-dashboard clients
- Workflows is where many of those integrations eventually show up as launched work, operator attention, or emitted results