MCP OAuth Client Web
by asibyl
This project implements an MCP Client with browser-based OAuth support, enabling inspection of transport and messages exchanged with the MCP Server. It facilitates end-to-end OAuth support with a Streamable HTTP Server.
Last updated: N/A
What is MCP OAuth Client Web?
This is an MCP client implemented for web browsers that supports OAuth authentication. It allows users to connect to MCP servers that require authorization and inspect the communication between the client and the server.
How to use MCP OAuth Client Web?
The client first requires the user to connect to a server in the 'Connect' panel. This triggers an OAuth flow if no access token is available, acquiring one from the server's /authorize endpoint. Once connected and server capabilities are retrieved, users can list tools in the 'Tools' tab and execute them with input parameters in the 'Run' panel. Responses can be inspected in the 'Inspect' panel.
Key features of MCP OAuth Client Web
OAuth authentication flow
Connection to MCP servers
Tool listing and execution
Request/Response inspection
Streamable HTTP Server support
Use cases of MCP OAuth Client Web
Testing and debugging MCP servers
Inspecting MCP communication
Developing MCP clients
Demonstrating MCP OAuth flow
FAQ from MCP OAuth Client Web
Does this client work with all MCP servers?
Does this client work with all MCP servers?
No, it specifically works with servers that implement client authorization via /authorize and /token endpoints.
What is the purpose of the 'Tools' tab?
What is the purpose of the 'Tools' tab?
It allows users to list the available tools provided by the connected MCP server.
How does the OAuth flow work?
How does the OAuth flow work?
The client triggers the OAuth flow through the server's /authorize endpoint, acquiring an access token upon receiving an authorization code from the server.
Can I use this client to test different MCP servers?
Can I use this client to test different MCP servers?
Yes, you can connect to different MCP servers as long as they implement the required OAuth endpoints.
Is this project related to the MCP Inspector?
Is this project related to the MCP Inspector?
Yes, this project borrows concepts and ideas from the MCP Inspector but aims to maintain simplicity.