Autonomous agents

An agent that runs unattended, such as a scheduled job or a backend service, has nobody to sign in for it. Create it as an agent in Makini: it has a name and a role, no email address, and it authenticates with a token you generate. You connect its platforms for it.

Agents and MCP users

	MCP user	Agent
Identified by	Email address	Name
Signs in with	A one-time code or your company sign-in	A token you generate
Platforms are connected by	The person, from their agent	You, from the dashboard
A platform that isn't connected	The agent is given a link to connect it	Doesn't exist for the agent
Roles and tool permissions	Yes	Yes

Agents are available on plans that are billed by tool call, during the trial, and in provider mode. They aren't available on per-seat plans, and you can't move to a per-seat plan while the application has agents.

Set up an agent

Create the agent

Open Users → MCP users and click Create agent. Give it a name and a role. The role decides which tools it may run, exactly as it does for a person.

Connect its platforms

The agent's page lists the platforms its role can see. Click Connect on each one the agent should reach.

If the platform uses one shared account for everyone (set under Platforms), it connects straight away.

Otherwise Makini Link opens. Enter the credentials the agent should use, and you return to the agent's page.

The agent only ever sees platforms that are connected. A platform you haven't connected is left out of list_platforms, and asking for it by name answers that it isn't available.

Generate a token

Click Generate token and copy it. Makini shows it once and doesn't store it, so keep it in your secret store. An agent can hold up to ten tokens, for example one for each environment.

Connect with the token

The token is a long-lived OAuth refresh token. Your agent exchanges it for a short-lived access token and sends that to the connector URL. The agent's page shows the three values you need: Connector URL, Token URL and Client ID.

The response carries an access_token that lasts five minutes. Send it as a Bearer token on every request to the connector URL, and exchange the refresh token again when it expires. The refresh token itself doesn't change.

In your own code, refresh a little before each access token expires:

A token that hasn't been used for 90 days stops working. Generate a new one on the agent's page.

Manage an agent

To	Do this	What happens
End one token	Revoke it on the agent's page	That token stops within five minutes. The agent's other tokens keep working.
Pause the agent	Edit, then turn off Enabled	Every token stops within five minutes, and works again when you enable the agent.
Remove the agent	Remove	Its tokens and connections are removed.
Change what it may do	Change its role, or its own tool permissions	Applies to its next tool call.

When a platform refuses an agent's stored credentials, the platform disappears for the agent and Makini emails the people who manage connections. Open the agent's page and click Re-authorize.

Agents for your customers

In provider mode an agent belongs to one of your customers. Create it from the customer's Users tab, or through the Tenants API. See Provider mode.

Autonomous agents

Agents and MCP users#

Set up an agent#

Connect with the token#

Manage an agent#

Agents for your customers#

Agents and MCP users

Set up an agent

Connect with the token

Manage an agent

Agents for your customers