What problem does it solve? Setting up an OAuth-protected HTTP MCP connector in Claude Code involves many error-prone details: choosing the right config scope, exporting the client secret correctly, pinning the callback port, discovering scopes dynamically, and editing ~/.claude.json without corrupting it. This Skill walks through the entire registration and authentication flow step by step, asking the user for each value instead of assuming defaults. ## Core Features & Use Cases - Guided configuration gathering: Prompts for server name, MCP endpoint URL, OAuth client ID/secret, callback port, discovery URL, and config scope one at a time. - Correct connector registration: Runs claude mcp add with the right transport, scope, client credentials, and callback port, and adds the authServerMetadataUrl to ~/.claude.json. - Dynamic scope discovery: Queries the server's RFC 9728 protected-resource metadata for scopes_supported, diffs against existing config, confirms with the user, and writes scopes with targeted edits. - Verification and troubleshooting: Validates JSON config, checks registration with claude mcp get, and covers common failures like client secret validation errors, 404 URLs, and scope changes. - Use Case: You need to connect Claude Code to an Indicium/sf_mcp-style OAuth-protected MCP endpoint for the Thinkwise Software Factory. The Skill collects your credentials, registers the connector at user scope, pins the advertised scopes, and guides you through the browser OAuth login. ## Quick Start Ask Claude to install and authenticate a new OAuth-protected HTTP MCP connector in Claude Code, providing the server name, endpoint URL, and OAuth client credentials when prompted.
