An MCP server is a project type for Model Context Protocol endpoints. Agents must authenticate before they can call a tool. Create one from Projects by choosing MCP server.
MCP Auth appears in the sidebar only for that project type.
Playground
Open MCP Auth. Connect with SSO to mint a short-lived bearer for the environment, then import tools. Tokens are scoped to the selected environment — use dev while iterating.
After registration
| Job | Where |
|---|---|
| Clients and scopes | Authentication |
| Which tools an agent may call | Authorization |
| Call history | Audit |
| Abuse on the auth surface | Lidar |
| Server credentials | Vault |
Each project can hold several environments, so staging tools never resolve in production.
Controls in `@authdog/mcp-sdk`
These run inside your server. Each is opt-in.
- Trust store — verified non-human identities only, when enforcement is on. Revoke one and it stops immediately.
- Per-tool authorization — AuthZEN check before the tool runs.
- Audit — invocation, denial, failure. No raw arguments.
- Threat detection — Lidar signals for poisoning, injection, exfil, rate abuse.
Start each control in monitor mode before enforce. See MCP security and machine identity.
Related
| Read | To learn how to |
|---|---|
| Projects | Register an MCP server |
| Authorization | Scope tools |
| Lidar | Detect abuse |
| Machine identity | Client credentials grant |