$ loading_
Reproduce GitHub OAuth locally to debug MCP OAuth provider configurations.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Local OAuth + MCP Test Server" yet — see the docs or source repo.
I’m hitting callback and token flow issues while configuring an MCP OAuth provider. Explain how to use Local OAuth + MCP Test Server to reproduce GitHub OAuth behavior locally and list the key configuration items I should verify.
A local debugging plan showing how to use the test server to verify OAuth configuration, callback flow, and token exchange steps.
Help me design a test plan using Local OAuth + MCP Test Server to verify whether my MCP client handles refresh tokens correctly, including expiry refresh and error handling.
A refresh-token-focused test checklist covering normal refresh, expiry scenarios, and error response validation.
I want to confirm whether my MCP OAuth provider auto-discovery is configured correctly. Using Local OAuth + MCP Test Server, give me a step-by-step local checklist to validate auto-discovery.
A step-by-step validation guide to confirm discovery endpoints and related configuration work as expected.
When integrating an MCP OAuth provider, developers can use it to reproduce GitHub’s OAuth behavior locally and quickly locate configuration or flow issues. It is especially useful for debugging callbacks and token exchange without depending on a live environment.
If a client needs to handle refresh tokens, this test server can be used to verify whether the refresh flow works correctly. It helps catch token renewal issues early during development.
When configuring an MCP OAuth provider with discovery support, teams can use it to check whether auto-discovery works as expected. This helps surface discovery endpoint or metadata configuration problems earlier.
It is a local test server that reproduces GitHub’s OAuth behavior for debugging MCP OAuth provider configurations. The description also explicitly says it supports refresh tokens and auto-discovery.
Yes. The original description explicitly states that it supports refresh tokens, so it can be used to debug and validate token renewal flows.
The provided material does not include installation or runtime steps. For exact usage, dependencies, and startup instructions, see the source repository.
A simple MCP server for testing OAuth 2.0 support in mcp-cli.
Connect securely to a remote MCP server with GitHub OAuth.
Securely manage OAuth 2.0 tokens for MCP applications.
Test MCP OAuth login and retrieve the authenticated user's identity and plan.
Run a lightweight local MCP mock server for predictable testing.
Deploy a secure MCP OAuth 2.1 server with monitoring and analytics.