MCP
MCP, in both directions.
Attach any MCP server and its tools join your agents' toolbox. Helios speaks MCP outward too, so your own clients can put Helios agents to work.
When a customer escalates, check their entitlement in our internal billing service and post the answer in the thread.
- plain·read thread · customer_id
- mcp · internal-billing·get_entitlement
- mcp · internal-billing·list_overage_events
- plain·reply in thread
Entitlement answered in 8s
- Enterprise plan · 2 overages this cycle
- Answer posted before the customer refreshed
Attach a server
Bring any tool that speaks MCP.
Your internal services, your vendor's server, your own scripts. If it speaks MCP, your agents can use it.
OAuth
Point Helios at the server's authorization and token endpoints, set the scopes, and let it hold the grant for you.
Bearer token
Paste a token. It is encrypted at rest and attached to outbound calls server-side, out of the model's reach.
Custom headers
Some servers want their own header. Set up to twenty of them — Authorization included — and Helios sends them on every call, holding back the transport-level headers that would break the connection.
No auth
For a public or internal server that needs no credential, attach the URL and go.
Tool filtering
Choose exactly which tools an agent gets.
An MCP server may expose forty tools. Allow the handful your task needs and Helios refuses the rest.
Filtering happens at the proxy, before a call ever reaches the upstream server. A tool that is not on the allowlist is turned away, whatever the agent decides to try. It is the difference between handing an agent a read-only reporting tool and handing it the whole administrative surface of a system.
Summarize this quarter's incidents from our internal on-call service.
- mcp · oncall·list_incidents · allowed
- mcp · oncall·get_incident · allowed
- code·group by service · rank by minutes
- notion·write quarterly incident review
Incident review drafted
- 31 incidents · 4 services account for 78% of downtime
- Write tools stayed out of reach for this run
Helios over MCP
Your clients, our agents.
Helios is an MCP server as well as an MCP client. Reach your agents from the tools you already have open.
Drive Helios from your client
Point an MCP client at Helios and it gains the tools Helios exposes, so you can reach your agents from wherever you already work.
The same identity and controls
Calls over MCP carry the same authentication as calls through the app, and land against the same organization roles and resource-level access.
One agent, many front doors
Chat, workflows, and MCP all drive the same runtime, the same tools, and the same memory.
Keep going
Extend from here
Guide
Attach an MCP server
Walk through connecting a server, choosing an auth method, and allowing the tools your agents should have.
Platform
The agent runtime
MCP tools sit alongside your integrations, your databases, and the agent's own computer.
Workflows
Put it on a trigger
An agent with your MCP tools, running on a schedule or the moment an event lands.
Hand your agents a new tool.
Start free, attach a server, allow the tools you trust, and watch an agent use them.