STACK

Installation

Use STACK as a remote MCP server at https://mcp.getstack.run/mcp. For API-key based MCP clients, the documented Claude Code command is:

claude mcp add stack --transport http https://mcp.getstack.run/mcp --header "Authorization: Bearer sk_live_YOUR_KEY"

For OAuth-capable clients, connect to the same MCP endpoint and complete the browser-based OAuth flow.

Configuration

STACK's MCP server speaks Streamable HTTP. OAuth 2.1 with PKCE and Dynamic Client Registration are used for client sign-in, while legacy or self-hosted setups can use a bearer API key.

Direct API and SDK access use STACK_API_KEY. CLI sign-in is done with npx @getstackrun/cli auth login, and STACK_OAUTH_SCOPE can narrow CLI sign-ins to a read-only subset for monitoring.

Prerequisites

A STACK operator account, at least one upstream service connected in STACK, browser access for OAuth approval, and the relevant client runtime: Claude Code for the Claude workflow, Node.js/npm for the JS/TS SDK and CLI, or Python/pip for the Python SDK examples.

Capabilities

STACK provides agent identity, passport issuance, service connection and proxying, audit logging, audit-chain verification, scan/detector workflows, drop-offs, skills, and team-aware credential access.

Limitations

ChatGPT Plus/Pro are read-only in the documented setup, while Business/Enterprise/Edu can mutate. Standard-mode agents skip checkpoints and checkout review. The docs also note that Claude Desktop registry support was still pending at the time of review.