Oauth Connect MCP server
{
"mcpServers": {
"gfbytes-oauth-connect": {
"type": "http",
"url": "https://mcp.gfbytes.com/mcp"
}
}
}{
"mcpServers": {
"gfbytes-oauth-connect": {
"type": "http",
"url": "https://mcp.gfbytes.com/mcp"
}
}
}{
"mcpServers": {
"gfbytes-oauth-connect": {
"type": "http",
"url": "https://mcp.gfbytes.com/mcp"
}
}
}{
"servers": {
"gfbytes-oauth-connect": {
"type": "http",
"url": "https://mcp.gfbytes.com/mcp"
}
}
}{
"mcpServers": {
"gfbytes-oauth-connect": {
"type": "http",
"url": "https://mcp.gfbytes.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.2.0
What it does
A diagnostic tool that checks whether an MCP server is properly configured for OAuth connections in Claude, Cursor, Desktop, and Grok. It verifies login challenges, registration endpoints, and PKCE S256 support before attempting integration.
- Validate your MCP server meets OAuth requirements before purchasing a full integration report.
- Diagnose why an MCP server fails to connect in Claude, Cursor, Desktop, or Grok Connectors.
- Prepare your MCP server URL for use in Connector UIs by confirming it passes basic OAuth checks.
Tools this server exposes
| Tool | Does |
|---|---|
| diagnose | Checks a given MCP server URL for proper login challenge, registration endpoint, and PKCE S256 support. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.