Claude Code

Add STACK to Claude Code as an MCP server. STACK speaks OAuth 2.1 with PKCE and Dynamic Client Registration (RFC 7591), which is what Claude Code's MCP add command requires. No API-key copy-paste; you approve scopes in your browser the first time the CLI connects.

For the broader why-this-matters framing — what STACK adds on top of Claude Code, why this is especially useful for engineering teams sharing credentials, and how the cross-runtime hand-offs work — read /with/claude-code. This page is the technical guide.

1. Prerequisites

  • Claude Code installed (https://docs.claude.com/en/docs/claude-code).
  • A STACK operator account. Sign up at https://getstack.run (free tier, no credit card).
  • At least one upstream service connected on the STACK side (Slack, GitHub, Stripe, etc.) at https://getstack.run/services. Claude Code will reach those through STACK.

2. Add STACK as an MCP server

From your terminal, run:

bash
claude mcp add stack --transport http https://mcp.getstack.run/mcp

On first connection, Claude Code discovers STACK's OAuth metadata at /.well-known/oauth-authorization-server, registers itself as an OAuth client via /oauth/register, and opens your browser to getstack.run to approve the scopes.

If you want STACK available across all your Claude Code projects, add --scope user. To scope to one project only, use --scope project (the default in current versions; check claude mcp add --help).

3. Verify the connection

bash
claude mcp list

You should see stack with status connected. Inside a Claude Code session, the model can now call STACK tools just like any other MCP-registered tool.

4. Usage from Claude Code

Once connected, Claude can invoke any STACK tool by name. The most useful ones in a coding session:

  • stack_list_services — see which services are connected and what scopes you have.
  • stack_proxy_request — make an authenticated call to any connected service through the credential-injecting proxy.
  • stack_issue_passport — mint a short-lived passport for a specific intent.
  • stack_invoke_skill — run a published skill in a sealed sandbox (LLM steps, code steps, the works).
  • stack_audit_list — read the hash-chained audit log of what every agent on your team has done.
  • stack_create_dropoff / stack_collect — schema-validated agent-to-agent hand-off across runtimes.
  • stack_revoke_passport / stack_revoke_all_passports — kill switch, propagates in under 60 seconds.

Full tool reference at /docs/mcp-tools.

5. Team sharing

When you connect STACK to Claude Code with your operator account, every service connected on the STACK side becomes available to the agent through the same shared vault. Invite team members at getstack.run/team and they connect Claude Code with their own STACK login; everyone draws from the same credentials, with per-member audit and per-member revocation.

6. Revocation

Disconnect or revoke from the STACK dashboard at getstack.run/team or programmatically via POST /v1/passports/revoke. Sub-60-second propagation: the next request from Claude Code fails with a 401, in-flight requests fail mid-call.

Next

stack | docs