Connect your tools

How agents reach a service, how to ask for a specific kind of connection, and how to keep two accounts on one service, such as a staging and a live key.

A connection gives agents access to a service. Connections belong to the workspace, so you connect a service once and every agent in the workspace can use it.

Problems this solves

Problem	What Kavela does
Sign-ins expire and runs fail	Tokens are refreshed before they expire. When a connection does lapse, the run asks you to reconnect it
The agent can't sign in, has no browser, or stops at a CAPTCHA	Every agent has a real browser. A sign-in or CAPTCHA opens the live page for you to clear once, and the agent continues from that page. The sign-in is kept for later runs
The automation only works with a few apps	Any service with an MCP server, an API or a sign-in page
Handing passwords to an agent	You sign in yourself, on the real page. Passwords and codes never go through the chat

How Kav connects a service

Ask for the work, and Kav connects what it needs, in this order:

Order	Route	When
1	A connection the workspace already has, or a one-click one	The service is already connected, or Kavela connects it in one click
2	The service's MCP server	The service publishes one
3	The service's API, with a key or your own app	Kav can do the developer-settings setup in the browser and hand you only the step with the secret
4	The website, with your own sign-in	A personal or social account, or an action the service's API keeps to approved partners

If you don't use the service yet, Kav offers to set up an account for you in one approval, then connects it.

Ask for a specific kind of connection

You want	Say or do
A specific MCP server	Give Kav its address: "Connect our CRM through its MCP server at https://mcp.example.com/mcp"
An API key	Say the sign-in doesn't work for you, and the card adds the key route. Or add it yourself, below
A website sign-in	"Sign in to my LinkedIn in the browser and post this"
To add it yourself	Open Connectors in the sidebar, then New connector, and pick MCP server, New login, New connector or New API

New connector option	What it adds
MCP server	A service's MCP server
New login	A website username and password an agent can sign in with
New connector	An OAuth or service connector. Opens the builder
New API	A custom API integration. Opens the builder

Keep two accounts on one service

Some jobs need two accounts on the same service, such as Stripe staging and Stripe live, or a personal and a company GitHub. Give each one a name:

Add my Stripe live key as a second Stripe account named "Stripe live".

Kav raises a card that saves the key under that name. You can also add one under Connectors: open the service, Add a login, then Keep a key on it as another account.

Then name the account in the request: "Use Stripe staging for this test run."

Rule	Detail
Before a second account	The service has to be connected once
Names	Up to 80 characters, unique on that service
Default	The first account, unless the request names another
In the agent's computer	The first account keeps the usual variable, such as `STRIPE_SECRET_KEY`. Each other account gets `KAVELA_CONN_<SERVICE>__<NAME>`
MCP tools	Use the service's MCP sign-in

Reconnect or remove a connection

Open Connectors in the sidebar. Each account has Reconnect (or Authorize) and Disconnect. The Stay signed in to sites setting keeps website sign-ins between runs.

Risky steps wait for your approval, as set by the workspace's autonomy setting. A web page an agent reads can still contain instructions aimed at the agent, so keep approvals on for actions that leave the workspace.