Authentication
The MCP endpoint needs to know who is calling, because every tool acts as that person: you see your projects, and the audit log records you.
Today: a bearer token
Send an Authorization header on every request:
Authorization: Bearer <token>
Today the MCP server accepts the local dev token only. dev-token is the admin dev user; dev-token:<email> acts as that directory user, which is handy for trying the platform as an owner or a non-admin. Dev tokens work only when the server operator turns them on with TC_DEV_TOKEN (the local stack does). They are for local and evaluation installs, never production.
Without a valid token the server answers 401 with WWW-Authenticate: Bearer realm="tc".
Coming: OAuth
Production sign-in for MCP clients will go through a small OAuth authorization server run by vastframe. It supports client ID metadata documents (the current MCP spec's preference) and dynamic client registration (for Copilot Studio), and hands the actual sign-in to your company identity provider. Your agents will then act as you, with your normal permissions, and there will be no token to copy.
OAuth for MCP and the CLI isn't built yet. Until it ships:
- Clients that only support OAuth (claude.ai custom connectors, Claude Desktop's Connectors settings, Copilot Studio) can't connect directly.
- Clients that let you set a header (Claude Code, VS Code with GitHub Copilot, Cursor) work now. Claude Desktop works through a local bridge. See Connect your client.
Roles still apply
The token identifies a person; it doesn't grant anything extra. Tool calls follow the same project permissions as the console:
| Role | Can |
|---|---|
| Owner | Everything on their projects, including delete |
Developer (app role developer) | Deploy, logs, database, storage, env, access; not transfer or delete |
| Org Admin | Everything on every project |
| Delegated Admin | Everything on projects in their part of the org |
| Auditor | Read only |
See Access & security for the full model.