🔒 Minimal GitHub OAuth-enabled MCP Server

Created By
denda year ago
Quick demo MCP server that uses GitHub OAuth to authenticate users.
Overview

What is the Minimal GitHub OAuth-enabled MCP Server?

This project is a minimal server implementation that demonstrates how to integrate GitHub OAuth for user authentication in an MCP (Model Context Protocol) server.

How to use the Minimal GitHub OAuth-enabled MCP Server?

To use this server, you need to register a GitHub application, obtain the client ID and secret, and set them in a .env file. After that, install the dependencies and run the server using npm commands.

Key features of the Minimal GitHub OAuth-enabled MCP Server?

  • Demonstrates GitHub OAuth integration for user authentication.
  • Provides a minimal setup for testing purposes.
  • Includes instructions for registering a GitHub application.

Use cases of the Minimal GitHub OAuth-enabled MCP Server?

  1. Testing GitHub OAuth authentication in a development environment.
  2. Learning how to implement OAuth in MCP servers.
  3. Serving as a reference for best practices in OAuth implementation.

FAQ from the Minimal GitHub OAuth-enabled MCP Server?

  • Is this server suitable for production use?

No, this server is not intended for production use and should only be used for testing and educational purposes.

  • How do I register a GitHub application?

You can register a GitHub application in your GitHub settings under the 'Developer settings' section.

  • What should I do if I encounter issues?

Refer to the archived repository for the latest samples and best practices.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dend
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

an hour ago