MCP Server
AuthAction supports secure authorization for MCP (Model Context Protocol) servers through dynamic client registration and resource access management.
Available Guides
Section titled “Available Guides”- MCP Server Authorization: Configure dynamic client registration and access for MCP API Resource servers
- Dynamic Client Registration (DCR): Self-registration for MCP and similar use cases
Overview
Section titled “Overview”MCP servers often need to dynamically onboard clients and control API access. AuthAction provides:
- Dynamic Client Registration: Applications can register themselves automatically without manual configuration
- Dynamic Client Access: Registered clients are automatically granted access to designated MCP API Resource servers
- Connection Control: Fine-grained control over which authentication connections are available to dynamic clients
Calling other APIs as the user
Section titled “Calling other APIs as the user”The guides above protect your MCP server: it is registered as an API, and MCP clients get tokens for it. If your MCP server’s tools also call other APIs on the signed-in user’s behalf, register it as an agent too. It then exchanges the user’s token for a short-lived one naming both the user and the MCP server.
- Agents & Trusted Issuers: Register the agent, and let it authenticate without a client secret
- Token Exchange for AI Agents: The exchange itself, with an MCP server example