Setting up MCP Clients¶
The Model Context Protocol (MCP) specification defines that authorization is initiated by MCP clients. These clients handle authorization flows, manage tokens and sessions with MCP servers, and provide end-user experiences based on user permissions.
Asgardeo provides an MCP Client Application template with default configurations to register an MCP client with minimal effort. This template has been configured to create an OAuth application that adheres to the guidelines and best practices outlined in the MCP authorization specification.
Other Application Types
While the MCP Client Application template is optimized for MCP connections, MCP servers can also be accessed by most other application types in Asgardeo, including Single Page Applications, Traditional Web Applications, Mobile Applications, and M2M Applications. The only exception is Digital Wallet applications, which cannot access MCP servers.
Register an MCP Client Application¶
To regiser an MCP Client application,
-
On Asgardeo Console, go to Applications > New Application to navigate to the application template selection wizard.
-
Select MCP Client Application. The application creation wizard will appear.
The MCP application creation wizard includes the following fields.
Parameter Description Name A unique name to identify your application. Authorized redirect URL The URL to which the authorization code is sent upon user authentication and where the user is redirected upon logout. Public client Keep this enabled if your MCP client application cannot securely store client secrets. (Eg: mobile apps, single page web apps etc). Note
MCP Authorization specification recommends that MCP clients should be public clients with authorization code grant flow enabled. However, if your MCP client runs on a server side environment where you can keep a secret, you can untick the public client option.
-
Click Create to complete the registration.