Automette

Nothing is installed. This is a remote server: no package, no download, nothing running on your machine. Your client stores a name, a URL and a credential, and every tool call is an HTTPS request to us.

https://automette.com/api/mcp

Which method

	Sign in with Automette	API key
Setup	Approve in a browser	Copy a key
Belongs to	You	The team
Revoked from	Settings → Connections	API Keys
Good for	Your own assistant	A shared or headless setup

Signing in is the better default. Nothing is stored on your machine that someone could copy, and you can cut it off yourself without affecting anyone else on the team.

Claude Desktop, or any app with a connector list

Open the app's connector or integration settings.

Add a custom connector with the URL https://automette.com/api/mcp.

It opens a browser. Sign in to Automette and approve.

The connector appears as connected, with tools available.

Claude Code

Claude Code does not ask which method you want. It decides by whether you pass --header: with one it uses that credential, without one it discovers OAuth by itself.

Add it with --scope user. Without it, the connection is saved for the current project directory only — move to another folder and it is gone. claude mcp list from elsewhere is how you find out.

claude mcp add --scope user --transport http automette https://automette.com/api/mcp

add does not connect or validate anything — it writes the configuration and returns. Start Claude Code and open the panel:

/mcp

automette shows as ! Needs authentication. Select it, and a browser opens on its own. Sign in, approve, and it becomes ✔ Connected with a tool count.

Or from the shell, without opening a session:

claude mcp login automette
claude mcp login automette --no-browser   # SSH or headless: prints the URL

Check it worked

/mcp

automette should be listed as connected. Then ask for something read-only:

List my Automette templates

If templates come back, the whole path works — transport, authentication and team scoping.

Which team it acts on

A connection acts on one team, and which one is decided when you connect. It cannot be changed afterwards: the team travels inside the token, and a token that has already been issued cannot be re-scoped.

Signing in. If you belong to one team, nothing is asked — a picker with one option teaches nothing. If you belong to several, you are asked to choose before approving. Either way the approval screen names it:

Acting on Acme A connection is tied to one team. To use a different one, connect again and choose it.

An API key acts on the team it was created in. There is nothing to choose; create the key in the team you want.

To change teams later, connect again and pick the other one, or use a key from that team. You can keep both connections at once under different names.

If your assistant creates something and you cannot find it, check which team is active in the dashboard before assuming it failed. It is far more often the wrong team than a real failure.

Cutting it off

A sign-in: Settings → Connections → revoke. Personal to you; a teammate's connection is theirs to revoke.

An API key: API Keys → delete. That also stops every REST caller using it.

Last updated on

Connecting