What problem does it solve? Connecting an MCP client to the SAP Developers hosted MCP server is confusing because there is no aggregate /mcp root, three separate access tiers with different authentication, and XSUAA's lack of Dynamic Client Registration breaks native OAuth flows. This Skill provides the exact endpoints, client configurations, and workarounds needed to get connected. ## Core Features & Use Cases - Anonymous read-only access: Configure clients against /mcp/search, /mcp/homepage, and /mcp/graph to search tutorials, list missions, read news, and query the knowledge graph without credentials. - Authenticated personal progress: Set up Personal Access Token (bearer header on /mcp-pat/api) or OAuth via mcp-remote (on /mcp-auth/api) to read tutorial progress, complete steps, and get personalized recommendations. - Troubleshooting guidance: Resolve common failures such as the "does not support dynamic client registration" error, empty tools/list responses, redirect_uri mismatches, and per-IP throttling. - Use Case: Add the SAP Developers search service to Claude Code with one command, then ask your agent to find tutorials on SAP BTP and mark steps complete using a PAT with write scope. ## Quick Start Connect my MCP client to the SAP Developers server so I can search tutorials anonymously and then set up token-based access to read my personal tutorial progress.
