mcpField
S
Simple MCP Server with upstream auth via local rest endpoint

Simple MCP Server with upstream auth via local rest endpoint

Local
github.com/BarDwellerDeveloper Tools0Updated 81w ago

About Simple MCP Server with upstream auth via local rest endpoint

A prototype MCP server that gates tool access on session authentication. It uses Quarkus OIDC with GitHub OAuth and stores each user's GitHub access token for the session; intended for MCP server prototyping.

Key features

  1. 01Session-based tool access control
  2. 02GitHub OAuth authentication
  3. 03Session-scoped access-token storage

Use cases

  1. 01Prototype authentication-gated MCP tools
  2. 02Require GitHub authorization before listing repository issues

MCP support

Exposes MCP tools whose availability depends on session authentication. Users authenticate through a local URL backed by Quarkus OIDC and GitHub OAuth.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Simple MCP Server with upstream auth via local rest endpoint

This is a prototype where an MCP server offers tools, but limits their access based on internal state, requiring the user to authenticate via an external url.

In this case, the external url is wrappered with quarkus oidc, requiring authentication via github

The resulting access token for github is then stored within the mcp for the sessionid used by the user

Note: you must edit application.properties to add your client-id and secret for your GitHub OAuth app.

Requirements

  • JBang
  • OAuth2 App with GitHub
  • MCP Client like claude

Creating an OAuth2 App with GitHub

Navigate to https://github.com/settings/developers

Select OAuth Apps from the left nav

Click 'New OAuth App'

Give it a name, and set the callback url to be http://127.0.0.1:8080/auth

Copy the client ID to application.properties Click 'generate a new client secret' and copy the secret to application.properties

Update claude desktop config json...

For windows...

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

For mac...

{
    "mcpServers": {
        "ozzynet": {
            "command": "jbang",
            "args": [
                "--quiet",
                "org.ozzy:stiletto:1.0.0-SNAPSHOT:runner" ]
        }
    }
}

Testing..

Ask claude to list the issues for a repository ..

eg, list the issues for quarkusio's quarkus repo

Claude will ask permission to invoke the getSessionId tool Claude will then invoke the listIssues tool, and report it cannot use it, because you need to be authenticated, and will offer you a link of the form http://127.0.0.1/auth?sessionId= .. when you click that, you will be redirected to github, to authorize via the OAuthApp you created. When auth is complete, you can return to claude, and retry the list operation =)

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.