Implementing an MCP Client with Browser-based OAuth

Name: Implementing an MCP Client with Browser-based OAuth
Author: asibyl

@asibyl

リポジトリ

Implementing an MCP Client with Browser-based OAuth について

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

基本情報

カテゴリ

開発者ツール

ランタイム

node

トランスポート

stdio

公開者

asibyl

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは 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

FAQ from Implementing an MCP Client with Browser-based OAuth

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.

「開発者ツール」の他のコンテンツ

TalkToFigma

sonnylazuardi

TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.

6.9K