MCP.so
ログイン

Simple MCP Server with upstream auth via local rest endpoint

@BarDweller

基本情報

カテゴリ

開発者ツール

トランスポート

stdio

作者

BarDweller

Simple MCP Server with upstream auth via local rest endpoint について

A sandbox for MCP server prototyping

Simple MCP Server with upstream auth via local rest endpoint の設定

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

{
  "mcpServers": {
    "ozzynet": {
      "command": "cmd",
      "args": [
        "/c",
        "C:\\Users\\YOURUSERNAME\\.jbang\\bin\\jbang.cmd",
        "--quiet",
        "org.ozzy:stiletto:1.0.0-SNAPSHOT:runner"
      ]
    }
  }
}

Simple MCP Server with upstream auth via local rest endpoint のツール

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

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

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

概要

What is Simple MCP Server with upstream auth via local rest endpoint?

This is a prototype MCP server that offers tools but limits their access based on internal state. Users must authenticate via an external URL that uses Quarkus OIDC with GitHub OAuth. The resulting access token is stored per session ID.

How to use Simple MCP Server with upstream auth via local rest endpoint?

Install JBang and create a GitHub OAuth App with the callback URL set to http://127.0.0.1:8080/auth. Copy the client ID and secret into application.properties. Then configure your MCP client (e.g., Claude Desktop) to run the JBang command jbang --quiet org.ozzy:stiletto:1.0.0-SNAPSHOT:runner. Authentication is initiated when a tool is used without a valid session.

Key features of Simple MCP Server with upstream auth via local rest endpoint

  • Requires authentication via GitHub OAuth before tool access
  • Stores access tokens per session ID for reuse
  • Integrates with standard MCP clients like Claude Desktop
  • Uses JBang for execution with a Maven artifact
  • Leverages Quarkus OIDC for the OAuth flow
  • Provides a local REST endpoint for callback (localhost:8080)

Use cases of Simple MCP Server with upstream auth via local rest endpoint

  • Authenticating before listing issues for a GitHub repository (e.g., quarkusio/quarkus)
  • Demonstrating OAuth-integrated tool access in an MCP client
  • Testing prototype workflows where tool usage requires external identity verification

よくある質問

1

What dependencies are required to run this server?

You need JBang, a GitHub OAuth App, and an MCP client such as Claude Desktop.

2

How do I set up the GitHub OAuth App?

Navigate to GitHub Developer Settings, create a new OAuth App, set the callback URL to `http://127.0.0.1:8080/auth`, then copy the client ID and generate a client secret. Paste both into `application.properties`.

3

How does authentication work in practice?

When a tool is invoked without a valid session, the server returns a link like `http://127.0.0.1/auth?sessionId=<UUID>`. Clicking it redirects to GitHub for OAuth authorization. After successful authentication, you can retry the tool in Claude.

4

What tools are available in this server?

The README demonstrates two tools: `getSessionId` and `listIssues`. The `listIssues` tool requires authentication before use.

5

Is this server ready for production use?

No, it is explicitly described as a prototype.

コメント

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