MCP for your team and your users.

Two addresses for two kinds of people. Each signs in its own way and sees only what it may use.

For developers

Build and run the fleet from your AI tool.

https://mcp.fleetless.dev
Who
Your team, with Fleetless accounts
Sign-in
Emailed code or passkey
Tools
Developer tools and app tools
Plans
Every plan

Add it in one click

Claude Cursor VS Code

For your app's users

Their assistant, your robot, the role you gave them.

https://mcp.fleetless.dev/your_app
Who
The users of that one app
Sign-in
Your app's configured login
Tools
App tools, every call checked against their role
Plans
Plus and above, switched on per app

You switch it on in the console and hand your users the address. They can withdraw their tool's access in your app; so can you.

MCP for app users

Three steps, no setup.

  1. 1

    Add the address

    In the AI tool, add a custom connector or MCP server and paste the address: the developer one, or the app's.

  2. 2

    Sign in

    The tool opens the sign-in that belongs to the address: Fleetless for developers, the app's configured login for its users.

  3. 3

    Ask

    Every call is checked against the person's role. Access removed in the console is gone at the next call.

How it works, in the docs

My tool asks for an OAuth client ID

Most tools register themselves (dynamic client registration). Choose that when your tool offers it.

For a tool without it, use the public client fleetless-central-mcp and leave the secret empty.

My tool insists on a full endpoint path

Use https://api.fleetless.dev/mcp. It is the same server under its canonical name, and the identifier every access token is checked against.

connectedmcp.fleetless.dev
  1. Discoveryoksign-in and tools, found from the address
  2. Registrationokthe tool registers itself (RFC 7591)
  3. Sign-inyou@company.comthe account that belongs to the address
  4. Toolsreadyevery call checked against the role