Connections & tools
A Kanbu agent can do more than answer from the knowledge base — in conversation it can call a connected system, show a form, or load a skill playbook. Configure everything in admin under tools / connections and assign it to specific agents.
What you can connect
| Type | Use for |
|---|---|
| Custom HTTP/API tools | Any REST API — order status, tickets, ERP, CRM… |
| MCP | Notion, Linear, Freelo, custom MCP servers, or any other MCP-compatible service |
| Forms | Structured data capture in chat |
| Skills | Playbooks for “how to handle X”, loaded only when needed |
| Built-in tools | Knowledge search, web search, reading a specific page or document, operator handoff, conversation memory, e-commerce tools — enabled automatically, nothing to configure |
How it works
- Create or connect a tool in admin (HTTP / MCP / form / skill).
- Assign it to one or more agents.
- In conversation the agent decides when to use it — customers see the activity trail and citations from knowledge.
Details:
Unknown terms: Glossary.
Frequently asked questions
-
Which tool should I pick to connect my system?
If you have a specific REST API, use a custom HTTP tool. We support any MCP server, though — Notion, Linear, and Freelo connect in one click via OAuth, and you can also connect any other MCP-compatible service or your own self-hosted server by entering its URL and credentials. Use an MCP connection — it's usually faster to set up.
-
What happens if a connected tool fails?
The conversation doesn't crash. The agent sees the failure as a normal tool result and can retry or continue another way.
-
Can the customer see that the agent is using a tool?
Yes, the response shows an activity trail — which tools the agent called and where it drew information from.
-
Can I share one tool across multiple agents?
Yes, for each tool you can select specific agents or turn on Available to all agents.