Keeping Agents in Check: Apollo MCP Authentication
summary
Demo shows a running Apollo MCP Server and router protecting a GraphQL subgraph backed by the Metropolitan Museum API, validated end to end using WorkOS as the identity provider and an MCP Inspector debug client. The flow uses OAuth 2.1 protected resource metadata, dynamic client registration, JWKS/audience checks and scope-based permissions; a curator token successfully calls setHighlighted and the router enforces role scopes. The result is a working, configurable auth+authorization chain with four clear stages: discovery, registration, login, token validation.
AI-written summary · about
chapters (13)
- 0:00MCP auth with Work OS
- 1:03Why auth is critical in MCP
- 3:33MCP auth actors landscape
- 4:59MCP auth primitives and flow
- 7:08Demo setup and config
- 10:19Enabling auth in MCP server
- 11:21Config OIDC protected server
- 13:07Step-by-step auth flow demo
- 16:58Authorized MCP access
- 17:19Role-based access with scopes
- 18:01End-to-end MCP workflow
- 19:47Next steps and config
- 20:30Q&A
related talks
26mSecure Your MCP Servers with OAuth, JWT, SPIFFE and More
01h 23mWorkshop: Apollo Router & MCP: A Modern Agentic Development Approach
25mSecure Your MCP Servers With OAuth, JWT, SPIFFE and More
21mGraphQL Authorization with Open Policy Agent
25mOAuth Gets You In, Zero Trust Keeps You Safe
26mWho Let the Agent In? Securing MCP Servers in Production
40mAuthentication and Authorization in GraphQL
26mOrchestrating APIs for LLMs - Agentic Workflows for GraphQL