Custom tools (HTTP & MCP)
Connect the agent to any API of your own with a custom HTTP tool, or to any MCP server — no code required.
When a built-in action doesn't cover what you need, build your own. Custom tools let the agent reach your warranty lookup, internal pricing service, custom CRM, or any MCP server. They require a plan that includes the advanced-skills feature.
Custom HTTP tools
Define a tool that calls one of your HTTPS endpoints. From the Actions → Create builder you provide:
Prop
Type
The agent calls the tool with the parameters you defined and uses the response in its reply.
MCP servers
Point the agent at a Model Context Protocol server and it gains every tool that server exposes. You provide the server URL and, if needed, an auth token.
Security
Custom tools call endpoints you control, from our servers. For your safety they must use HTTPS, can't target private/internal network addresses, don't follow redirects to internal hosts, and have their credentials stored encrypted. The response is treated as untrusted content and can't issue instructions to the agent. Your endpoint's data (and any secrets in it) is never exposed on the public chat wire.