Implementing an MCP Client with Browser-based OAuth

@asibyl

Repository

Basic information

About 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 config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Implementing an MCP Client with Browser-based OAuth tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

Frequently asked questions

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.

Comments

More Developer Tools MCP servers

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

Termany

thinkany-ai

Agent-Native Terminal

174

Nebelus

Nebelus is an enterprise agentic-AI platform for regulated industries. This MCP server exposes the Nebelus Construction API: ~48 tools that give an MCP client full agent build parity — create/update/probe agents, edit ag

Cronwatch

cronwatchdev

CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.

Eddyter AI Rich Text Editor MCP

EddyterAI

Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R