MCP.so
ログイン

Implementing Streamable HTTP MCP Server with Browser-based OAuth

@asibyl

基本情報

カテゴリ

開発者ツール

トランスポート

stdio

作者

asibyl

Implementing Streamable HTTP MCP Server with Browser-based OAuth について

MCP Streamable HTTP Server with Standard Browser OAuth

Implementing Streamable HTTP MCP Server with Browser-based OAuth の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "streamable-http-oauth": {
      "command": "npx",
      "args": [
        "tsx",
        "server/index_streamable.ts"
      ],
      "env": {
        "GITHUB_CLIENT_ID": "",
        "GITHUB_CLIENT_SECRET": ""
      }
    }
  }
}

Implementing Streamable HTTP MCP Server with Browser-based OAuth のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Implementing Streamable HTTP MCP Server with Browser-based OAuth?

An MCP server that uses Streamable HTTP transport and browser-based OAuth with GitHub. It handles client authorization requests through custom OAuth endpoints, verifying access tokens and managing session-based transport connections. Built for developers who need an MCP server that delegates authentication to GitHub’s OAuth flow.

How to use Implementing Streamable HTTP MCP Server with Browser-based OAuth?

Clone the repository, run npm install, set GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET environment variables, then start the server with npx tsx server/index.ts. Clients interact via POST to /mcp, /authorize, and /token endpoints.

Key features of Implementing Streamable HTTP MCP Server with Browser-based OAuth

  • Streamable HTTP server with /mcp endpoint
  • Browser-based GitHub OAuth authorization
  • Custom PKCE challenge and verifier generation
  • Access token verification and session management
  • OAuthServerProvider implementation for extensibility

Use cases of Implementing Streamable HTTP MCP Server with Browser-based OAuth

  • MCP clients that need delegated authorization via GitHub
  • Prototyping OAuth flows within the Model Context Protocol
  • Building secure MCP services with third-party authentication

よくある質問

1

What is Streamable HTTP transport?

The server uses a single POST endpoint (`/mcp`) for all JSON-RPC messages instead of SSE or WebSocket, and manages sessions via a simple transport abstraction.

2

How does the OAuth flow work?

The client is redirected to GitHub’s authorization endpoint. After the user authorizes, GitHub returns an access token to the server, which stores it and issues a server‑owned access token to the client via `/token`.

3

What environment variables are required?

`GITHUB_CLIENT_ID` and `GITHUB_CLIENT_SECRET` must be set from a GitHub OAuth App created in your GitHub Developer Settings.

4

What are the runtime dependencies?

Node.js with npm. The server is started with `tsx` and depends on the packages installed via `npm install`.

5

Where are access tokens stored?

Access tokens are stored in memory on the server along with the client ID. No persistent storage is described.

コメント

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