Manage authentication, tool routing, and API keys for demo_mcp_gateway.
npx skills add https://github.com/curtismu7/AI-demo --skill mcp-gateway-curtismu7
Please help me install this Agent Skill. Skill: mcp-gateway Source: https://github.com/curtismu7/AI-demo/tree/main/.claude/skills/mcp-gateway Command: npx skills add https://github.com/curtismu7/AI-demo --skill mcp-gateway-curtismu7
This Skill provides comprehensive control and troubleshooting capabilities for the demo_mcp_gateway, which is responsible for the authentication pipeline, tool routing, and API key management.
Use the mcp-gateway skill to debug a 403 error for a specific tool in the demo_mcp_gateway.
High-intent search queries and answers about installing and using this skill.
To debug a 403 error when calling a tool through an API gateway, you need to inspect the authentication pipeline, verify token exchange processes, and check API key configuration. This ensures authorization decisions and scope enforcement are functioning correctly.
RFC 8693 token exchange in tool routing authorization works by swapping an existing token for a new one with different scopes or audiences. This process ensures that API key management and PingOne authorization decisions enforce correct scope access for specific tool routes.
You configure and manage tool routes within a gateway by adding, removing, or modifying route configurations. This requires understanding the gateway architecture and related configuration files to ensure proper tool routing and API key disposition across different services.
Before managing authentication and API key disposition, you need to understand the gateway architecture, related configuration files, and the authentication pipeline. This prerequisite knowledge is required to properly handle PingOne authorization decisions and scope enforcement.
Scope enforcement fails during PingOne authorization decisions when API key configuration is incorrect or the RFC 8693 token exchange does not properly map required scopes. Troubleshooting involves inspecting the authentication pipeline and verifying token exchange parameters.
navraj007inGenerate .env.example, .env.local, and validate-env.sh from architecture blueprints.
jpoutrinImplement OAuth 2.0 and OpenID Connect authorization code flows with PKCE.
bbrowningAutomate security reviews of JWT, OAuth 2.0/2.1, PKCE, and token exchange code.
yfyang86Apply Dennis Ritchie's mental models to system design and language architecture decisions.
