Advertise
MCP.so
Sign In

Simple MCP Server with upstream auth via local rest endpoint

@BarDweller

Repository

Basic information

Category

Developer Tools

Transports

stdio

Author

BarDweller

About Simple MCP Server with upstream auth via local rest endpoint

A sandbox for MCP server prototyping

#mcp-server#oauth2#prototyping

Simple MCP Server with upstream auth via local rest endpoint config

Add this server to your MCP-compatible client using the configuration below.

{
  "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 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 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

Frequently asked questions

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.

Comments

More Developer Tools MCP servers

ArtiBot Cloud MCP - Zhijiangyun 智匠云

bofob

ArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

1

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.

31

screenshotrun-mcp

screenshotrun

Give your AI agent the ability to see any webpage. Capture screenshots from Claude, Cursor, or any MCP client. Supports full-page, dark mode, mobile emulation, OG image generation, base64 output, custom viewport, ad bloc

GripForge

gripforgeai

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

1

Reelier

Maxime Houle

Agents make claims. Reelier writes receipts — record an agent's tool-call workflow once, replay it deterministically at 0 tokens, and diff runs to catch drift.

Advertise