MCP.so
ログイン

Implementing Streamable HTTP MCP Server with Browser-based OAuth

@asibyl

リポジトリ

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

MCP Streamable HTTP Server with Standard Browser OAuth

#mcp#oauth#http-server

基本情報

カテゴリ

開発者ツール

ランタイム

node

トランスポート

stdio

公開者

asibyl

設定

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

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

ツール

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

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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

FAQ from Implementing Streamable HTTP MCP Server with Browser-based OAuth

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.

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.

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.

What are the runtime dependencies?

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

Where are access tokens stored?

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

コメント

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

Code Index MCP

johnhuang316

A Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup

979

nuxt-mcp / vite-plugin-mcp

antfu

MCP server helping models to understand your Vite/Nuxt app better.

910

MCP-Bridge

SecretiveShell

A middleware to provide an openAI compatible endpoint that can call MCP tools

928

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

MCP Containers

metorial

Connect any AI model to 1200+ integrations (MCP, CLI, API)

3.3K