Tools & MCP
Connect your assistant to data, APIs, external services, and devices.
Tools let your assistant do more than answer from its built-in knowledge. Depending on the job, you can use built-in tools, add your own HTTP API, connect an MCP server, or let a device provide tools during a voice session.
Which Option Should I Use?
| Need | Use |
|---|---|
| Search documents, remember users, search the web, or generate images | Built-in Tools |
| Call a simple HTTP API that you own | Custom API Tools |
| Connect an existing MCP server by URL | MCP Server |
| Use MCP for voice or device sessions in real time | MCP Endpoint |
| Control capabilities exposed by an ESP32 device | Device Tools |
How Tool Calls Work
When a user asks for something that needs external data or an action, the assistant decides whether to call a tool. Most tool results are passed back to the AI model so it can produce a natural final answer.
Some tools respond directly. For example, image generation can return an image in chat, and a voice music tool can return an audio file for playback.
Plan Access
| Feature | Free | Go | Plus | Pro | Enterprise |
|---|---|---|---|---|---|
| Built-in chat tools | Yes | Yes | Yes | Yes | Yes |
| Custom API Tools | Yes | Yes | Yes | Yes | Yes |
| MCP Tools | No | Yes | Yes | Yes | Yes |
| Realtime voice with MCP | No | Limited | Limited | Higher limits | Custom |
If MCP is not visible in the admin UI, check your current plan and your role permissions for the assistant.