STACK with MCP
Why this matters
MCP isn't a framework. It's the wire protocol that lets AI clients discover and call tools without knowing anything about the server's implementation. Claude Code speaks MCP. Cursor speaks MCP. ChatGPT Workspace Agents, the Anthropic SDK, the OpenAI Agents SDK, and a growing list of others speak MCP. That makes MCP the convergence point: write a tool server once, every compliant client gets it. Run an MCP client, every compliant tool surface is reachable.
STACK lives at that convergence point. Many tools support MCP as an extra surface bolted onto a primary REST API. STACK was built MCP-first: the entire surface (around 80 tools across passports, proxy, audit, revocation, drop-offs, skills, identity, services) is published as a single MCP server, accessible to any compliant client through the standard handshake. OAuth 2.1 with PKCE and Dynamic Client Registration ship at the protocol level. No client-specific glue, no static API key swap.
What it unlocks
- STACK is MCP-native, not MCP-supporting. Most products that “support MCP” expose a subset of their API through it. STACK was built MCP-first: every capability the dashboard exposes is a tool the protocol exposes. Same auth, same audit, same scope model whether you're reaching STACK from Claude Code, Cursor, a custom Python client, or a future MCP client that doesn't exist yet. Spec-compliant means spec-portable.
- OAuth 2.1 with Dynamic Client Registration, at the spec level. Most MCP servers in the wild today still require you to hand over a long-lived API key. STACK publishes the full OAuth 2.1 stack at the standard discovery endpoint, including Dynamic Client Registration (RFC 7591). MCP clients self-register, the user clicks “approve scopes” once in their browser, and the client gets a scoped, expiring token tied to that user's session. Production-grade auth at the protocol level, not bolted on.
- Wrap your stuff in MCP, lean on STACK underneath. Want your internal CRM, data warehouse, deploy pipeline, or any domain-specific tool surface reachable from any AI client? Build a small MCP server that exposes the operations you want. STACK handles the rest: credential injection at the proxy, runtime detectors at the boundary, hash-chained audit on every action, sub-60-second revocation, identity verification for sensitive calls, drop-offs for hand-offs across servers, human-in-the-loop checkpoints, and pre-built capabilities from the skills marketplace. Your MCP server stays a small wrapper over your domain. The production layers around it are already built.
Wiring it up
STACK's MCP server is at https://mcp.getstack.run/mcp. Connect from any MCP client over Streamable HTTP. OAuth 2.1 with PKCE and Dynamic Client Registration are published at the standard discovery endpoint. Step-by-step setup, the OAuth flow, and the pattern for building your own MCP server on top of STACK:
Last reviewed 2026-05-08.