広告掲載
MCP.so
ログイン

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

よくある質問

1

What MCP servers does this client work with?

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

2

Does this client support prompts and resources?

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

3

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.

4

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.

5

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.

コメント

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

Foremerge

naw103

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

50

Vibgrate MCP

Vibgrate

Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

3

The Bridge

The Bridge

Complete, hosted login, teams, billing and feature flags for your SaaS app, set up by your AI assistant: sign-in and SSO, customer teams and roles, plans and usage limits on Stripe, and feature flags. OAuth sign-in, no A

Eased

easedui

Eased is a library of motion-first React components for shadcn, installed with the shadcn CLI.

Modelglass

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

1
広告掲載