External APIs & MCP-based integration
Reach any external API, and expose your tools over MCP.
- Any HTTP API
- MCP client and server
- Per-tenant credential scoping
Tools agents can call, and tools you can expose
Emulon treats every external system as a typed tool, whether it speaks plain HTTP or Model Context Protocol.
Any external API
Register a REST endpoint, declare its inputs and outputs, and it becomes a callable tool with the same guardrails as a built-in one.
MCP both directions
Emulon consumes MCP servers you already run and exposes its own, so your internal tools and our agents meet on one protocol.
Vaulted credentials
API keys and OAuth tokens live in a secret manager and resolve at call time, scoped per tenant. Workflow definitions never hold a secret.
Retries and backoff
Rate limits, timeouts, and transient failures are retried with backoff. Calls that change state carry keys so a retry stays safe.
Adding a tool
The same four steps whether the target is a public API or your own MCP server.
Register the endpoint
Add the base URL or MCP server address to the tenant registry, along with the environments it is allowed to run in.
Store the credential
Push the API key or complete the OAuth grant. The secret lands in the vault and is referenced by handle from then on.
Declare the schema
Describe inputs and outputs as typed fields. MCP servers are read automatically; plain APIs get a schema you define once.
Grant it to agents
Attach the tool to the workflows and agents that need it. Access is explicit, so nothing calls a system it was never granted.
What connects through this layer
Protocols, patterns, and data services the tool runtime handles.
Emulon runs as both an MCP client and an MCP server for tenant-registered tools.
Standard transport and auth patterns are handled by the runtime, not by each workflow.
Freight data services we commonly wire in; each one is a tool you enable per tenant.
Why this matters
Freight automation stalls the moment an agent cannot reach the system holding the answer.
No integration backlog
A new data source becomes an endpoint plus a schema rather than a release. Your team adds tools without waiting on ours.
Your tools, our agents
Internal services already exposed over MCP become available to Emulon immediately, keeping business logic where your engineers maintain it.
Credentials stay contained
Secrets are scoped to a tenant and resolved at call time, so an agent run can use a credential without ever reading it.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.