Custom APIs
MCP server
Give AI Agent steps the tools of an external MCP server over Streamable HTTP, found and called as the agent works, with an allowlist of permitted tools.
01 / Workflows
What you can automate.
The MCP connection points at a server's Streamable HTTP endpoint, with no authentication, a bearer token, or an API key header. AI Agent steps search the server's tools for the one they need and call it. You can limit which tools are allowed and add hints that help the search pick the right one.
- Let an AI Agent step look up data in a system that exposes MCP.
- Use a vendor's MCP server instead of building an integration.
- Limit an agent to a server's read-only tools.
02 / Capabilities
What it covers.
The full reference, with connection types, is in the MCP server docs.
Capabilities
- Streamable HTTP transport
- No authentication, bearer token or API key
- Allowlist of tools the agent may call
- Tool hints that guide the search
- Extra static headers on every request
Data handled
- Tool descriptions and input schemas
- Tool call arguments and results
03 / Availability
In every edition.
MCP server is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans
- Open-source engineAGPL-3.0, run and operate it yourself.Included
- CloudWe host and manage your instance.Included
- EnterpriseYour cloud or on-premises, supported by our team.Included
04 / Questions
Common questions.
Is MCP server included in my plan?
Yes. MCP server is a standard integration, included in Cloud, Enterprise and the open-source engine.
How is it set up?
A connection stores the MCP server credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.
Can a person approve before anything is written?
Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.
More in Custom APIs
Related integrations.
Connect the system you need.
Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.
All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.