An MCP server is a project type in Authdog for Model Context Protocol servers — the endpoints AI agents call to use your tools. Registering one gives the server OAuth-based authentication, so an agent has to prove who it is (and who it is acting for) before it can call a tool.
Create one from the Projects hub by choosing MCP server in the Create application dialog: "Expose tools and resources to AI agents securely."
What you get
- Register a Model Context Protocol server for AI agents
- Secure, authenticated tool and resource access
- Manage scopes and access control after creation
MCP projects appear in the Projects hub with an MCP type badge and their transport as a subtitle, for example SSE transport. They filter under the MCP tab in the rail.
The MCP Auth module
Selecting an MCP project adds an MCP Auth entry to the Products group in the sidebar. It does not appear for web or M2M projects.
The module opens on the MCP Auth Playground, which lets you exercise the auth path end to end without writing a client.
Playground
| Element | Purpose |
|---|---|
| Server selector | Picks which registered MCP server to test against. |
| Status badge | Idle until you connect. |
| Connect with SSO | "Use SSO to mint short-lived bearer for this environment." |
| Endpoint & Bearer | The resolved endpoint and the minted bearer token. |
| IDENTITY | Who the token represents — your console user, the environment, and whether an MCP token has been issued. |
| TOOL ACCESS | Import tools discovers the server's tool list. Disabled until you connect: "Connect with SSO first." |
| Advanced | Additional request options. |
The order matters: Connect with SSO first to mint the bearer, then Import tools to enumerate what the server exposes. Until then the identity panel reads No MCP token.
Configuring an MCP server
The rest of the console works the same for MCP projects as for any other:
| To configure | Go to |
|---|---|
| Clients and scopes | Authentication > Clients |
| Which agents may call which tools | Authorization |
| Tool-call history | Audit |
| Abuse detection on the auth surface | Lidar |
| Server credentials | Vault |
| Environments and transport URL | Project settings |
Each MCP project can carry several environments, so a server can expose a staging tool set separately from production.
Authdog's own MCP server
Authdog also publishes an MCP server for managing Authdog itself — reading users, counting them, setting the active user, and updating profiles from an agent. Actions taken through it are attributed distinctly from console actions in the audit trail, so you can tell agent-driven changes from human ones.
Related
| Read | To learn how to |
|---|---|
| Projects | Register an MCP server project |
| Authentication | Manage the OpenID clients agents authenticate with |
| Authorization | Scope which tools an agent may call |
| Audit | Review agent activity |
| Machine identity | Understand the client credentials grant |