Tools and connections
Let an agent use web tools, webhooks and MCP servers, and keep every change waiting for your approval.
Out of the box an agent answers from its instructions and documents. Connections let it do more: look an order up, check a booking, send a lead to your own system. You choose what it may use, and anything that changes something outside Kumoda waits for you.
Open Integrations. The tabs there are Integrations, Web tools, MCP servers and MCP clients. The first three are things your agents use. The last one is something else: it lets your AI look at Kumoda (see Kumoda as an MCP server).
The rule behind all of it
A tool that only reads runs when the agent asks. A tool that changes something waits for your approval, each time. Keys you give Kumoda are saved encrypted and are never shown again.
Give an agent a connection
A connection is made once, under Integrations, and then switched on for each agent that should use it. On the agent's page, open Tools and switch on the connections it may use. The page shows how many tools are on, and how many can change something.
An account can hold up to 50 connections, and a connection can be used up to 60 times an hour. A connection's name must be unique within its workspace.
Web tools
A web tool lets an agent call any service that has a web API.
Under Integrations, Web tools, choose Add a web tool and fill in:
| Field | What to put |
|---|---|
| Name | Letters, numbers and underscores, such as order_status. |
| Method | GET only reads. POST, PUT, PATCH and DELETE change something, so they always ask you first. |
| What it does | The agent reads this to decide when to use the tool. |
| Address | Starts with https://. Write {{input_name}} where the agent's value goes, and {{secret:NAME}} for a key. |
| Inputs | The values the agent fills in: a name, a type (text, number or yes/no) and what it is. Up to 12. |
| Headers (optional) | For example Authorization with the value Bearer {{secret:API_KEY}}. Up to 12. |
| Secrets (optional) | Keys the call needs. Saved encrypted, used only when the call is made, never shown again. Up to 5. |
A GET tool that actually changes something can be marked so it asks you first. For methods other than GET you choose whether the inputs go in the request body as JSON.
Example address: https://api.myshop.com/orders/{{order_id}}
Use Try it on a web tool to make a real call with sample values. It only runs tools that read: a tool that changes something is never run from here, an agent files it for your approval.
Webhooks
A webhook lets an agent send information to a system you own: a Zapier, Make or n8n flow, or your own server.
Under Integrations, add a webhook with a name (letters, numbers and underscores, such as send_lead), an address (it must start with https://), what it is for (the agent reads this to decide when to use it: say what it sends and when), and an optional token, which is sent as a bearer token if your address expects one.
The agent sends a short summary and a few name and value pairs, as JSON, with the agent's name and a timestamp. Use Try it to see your address answer.
MCP servers
An MCP server publishes its own tools: a CRM, a calendar, a database, search. Connect one and your agents can use those tools. Under Integrations, MCP servers, choose Connect an MCP server.
Name and address. The name is letters, numbers and underscores (such as my_crm, up to 30 characters), and its tools are named after it. You cannot change the name later. The address starts with https:// and often ends in /mcp. Kumoda only calls public addresses on the normal https port, and the key must not be written inside the address.
How the server checks you. Pick one:
- A key: an API key or token. It is sent as a bearer token, unless you name another header (for example
X-Api-Key). - Headers: for a server that wants several headers, or its own scheme. Up to six headers, each value encrypted. A value can be
Bearer your-key. - No key: the server is open.
Check the server. Choose Check the server and Kumoda connects and lists its tools before anything is saved. For each tool you choose:
- Use: switch the tool on for your agents.
- Without asking: let an agent use it straight away. Leave it off for anything that changes something, and each use will wait for your approval. A tool the server says only reads is marked as such.
If you change the address or the key after checking, the list is asked for again, because it may have changed.
Connect. Nothing is saved until the server answers. If you connect without checking, every tool starts on, and only the tools the server says only read run without asking.
Change a connected server
Open the server's card under MCP servers:
- Edit changes the address, a note on what it is for, and the key. For the key you can keep the saved one, send a key, send headers, or choose no key. The saved values are never shown, only which header they are sent in. Kumoda asks the server first, and keeps what was saved if the server refuses.
- Refresh tools asks the server for its tools again. Tools you had already chosen keep your choices. A tool the server added since starts switched on.
- Open Tools on the card to Switch all on or Switch all off, and to set Use and Without asking per tool (a search box appears when a server has more than six tools). The card counts how many tools are on, how many run without asking, and how many ask first.
- Remove deletes the key, and agents linked to it stop using it.
A server can offer up to 60 tools.
Customers' messages and your connections
By default, only you can make an agent use a connection, when you test the agent. A message from a customer cannot cause a call. To allow it, open the connection's card, open the Customers' WhatsApp messages setting, and tick Allow customers' WhatsApp messages to make the agent use it. Kumoda asks you to confirm. In the platform, this applies to a message from a customer on any channel (WhatsApp, the website chat window or the API), not only WhatsApp.
Even then, each use is filed as a request and waits for your approval (this option, Ask me to approve each one first, is recommended). Switching it off lets customer-triggered uses happen straight away, so anything a customer can talk the agent into will happen.
Approvals: "Waiting for you"
When an agent asks to use something that needs your OK, it is filed as a request instead of being done. The agent tells the customer that you have to approve it and that it has not been done yet.
You are told straight away:
- By email, with a link.
- On WhatsApp, if your own number (with the country code) is in your profile. Reply
approve 3fa91correject 3fa91c, using the six-character code in the message. The whole message must be that command, and it must come from your number. - In Flow, under Needs you, with Approve and Reject buttons (see Flow), and in the daily briefing.
- Under Integrations, a Waiting for you box appears with the requests, each showing which agent asked and what it wants to do.
Approving makes the call once, exactly as shown. Rejecting does nothing and sends nothing. Up to 20 requests can be waiting at a time. If more arrive, the extra ones are not filed and the agent tells the customer you will follow up.
What is read-only
- A web tool using
GET(unless you marked it as changing something), and an MCP tool the server says only reads, can run without asking. - When you ask Flow a question and it asks one of your agents, only reading tools are offered. Anything that would need approval is left out.
- Kumoda's own MCP server is read-only: it cannot send, change or delete anything. See Kumoda as an MCP server.
How calls are kept safe
- Only
https://addresses on the normal port, and only public addresses. The name is resolved and the address checked, and the call is made to the address that was checked. Redirects are not followed. - Replies are shortened, and keys found in a reply are hidden. What comes back from a service is treated as data, never as instructions.
- Keys and tokens are saved encrypted, and used only when a call is made.
- Every use shows in the agent's runs.