Implementing an MCP Client with Browser-based OAuth

@asibyl

代码仓库

基本信息

分类

开发工具

传输方式

stdio

作者

asibyl

关于 Implementing an MCP Client with Browser-based OAuth

web client to inspect transport and messages to and from MCP servers

Implementing an MCP Client with Browser-based OAuth 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块，请前往代码仓库查看安装说明。

代码仓库

Implementing an MCP Client with Browser-based OAuth 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Implementing an MCP Client with Browser-based OAuth?

A browser-based MCP client that implements end-to-end OAuth authorization with Streamable HTTP Servers, allowing developers to inspect the transport layer and messages exchanged with MCP servers. It is designed for developers working with MCP servers that require client authorization.

How to use Implementing an MCP Client with Browser-based OAuth?

Connect to a server through the Connect panel, which triggers the OAuth flow via the server's /authorize and /token endpoints. Once connected, list tools in the Tools tab, invoke them with input parameters in the Run panel, and inspect responses in the Inspect panel.

Key features of Implementing an MCP Client with Browser-based OAuth

OAuthClientProvider that stores auth tokens in session storage
Two-step connect: acquire token, then establish transport
Lists tools available on the connected MCP server
Calls tools with user-provided input parameters
Inspects server responses from tool execution
Simplified implementation inspired by MCP Inspector

Use cases of Implementing an MCP Client with Browser-based OAuth

Testing MCP servers that require OAuth authorization
Debugging the MCP transport and message flow
Developing Streamable HTTP servers with client authorization
Inspecting tool responses without a full Inspector setup

常见问题

What MCP servers does this client work with?

Only servers that implement client authorization, specifically the `/authorize` and `/token` endpoints.

Does this client support prompts and resources?

No, listing and using prompts or resources has not been implemented yet—those tabs provide no content.

How is OAuth handled in the browser?

The OAuthClientProvider saves and retrieves auth information in session storage, so tokens persist within the browser tab session.

How does this differ from MCP Inspector?

This project borrows heavily from MCP Inspector but aims for a simpler, more focused implementation for OAuth-based workflows.

Does it require a backend or proxy server?

The README describes a purely browser-based client; no backend or proxy is mentioned for the OAuth flow or transport.

开发工具分类下的更多 MCP 服务器

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

OpenMark

OpenMark AI

OpenMark is a remote MCP server available at https://openmark.ai. Benchmark your own prompt on 100+ models with real API calls.

Raccha AI

Shree Mandadi

MCP-first toolbox for agents: namespaced key-value storage, a FIFO queue, auth, and a handful of stateless utility tools (JWT decode, hashing, cert inspection, CIDR math). Free while in early access. This repository is a

Mcp-Warden

ermoluk

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.