read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

Browse the Docs All Connectors
34 connectors documented // 6,712 tools referenced // setup, auth & platform guides
↓

No pages match that search. Clear it

← All documentation

Connect Claude.ai and Claude Desktop to StackJack

Claude.ai (web) and the Claude Desktop app add StackJack as a custom connector — a remote MCP server (MCP is the Model Context Protocol, the open standard AI tools use to call external tools). You paste one URL and sign in; there is no field for a Client ID or Secret, so sign-in is the only way to connect Claude.

Prerequisites

  • A Claude account on any plan — custom connectors are available on Free (limited to 1 connector), Pro, Max, Team, and Enterprise.
  • On Team or Enterprise, an organization Owner must add the connector for the workspace first (see below); members then connect individually.
  • A StackJack account that is a member of your workspace. Any team member can connect — no admin-created credentials needed.
  • Your StackJack MCP endpoint URL: https://mcp.stackjack.io/mcp (shown with a Copy button on the MCP Setup page in the portal).

Connect (individual accounts)

  1. In claude.ai, click Customize (bottom-left) → Connectors. In Claude Desktop: Settings → Connectors.
  2. Click Add custom connector (the + button) and paste only the URL: https://mcp.stackjack.io/mcp. Leave the Advanced OAuth Client ID/Secret fields blank.
  3. Click Add, then Connect. Claude registers itself with StackJack and opens a browser to sign in — use the same email, password, and MFA you use for the StackJack Portal.

Your StackJack tools then appear in Claude conversations.

Team and Enterprise workspaces

On Claude Team or Enterprise, only an organization Owner can add connectors, via Organization settings → Connectors → Add connector → Custom → add the StackJack URL. Once added, each member connects and signs in individually with their own StackJack account, so tool access and usage attribution stay per-person.

Claude connects with just a URL, and the way it identifies itself to StackJack can be either a private per-install registration or a single shared-app identity (CIMD). If Claude connects as a shared app, StackJack shows a branded consent screen right after you sign in — headed "Authorize Claude", with a "Verify before you approve" panel listing the app identity (client_id) URL and the host your authorization is sent to. Choose Allow access to finish connecting. This is expected the first time (and on later sign-ins); read How AI tools authenticate for what each line means.

Which surface your connection then shows up on follows the same split: a shared-app authorization appears as a Connected apps entry an admin manages per member on the Team page, and a per-install connection appears as a read-only AI session (in your own MCP Setup self-view, and per member on Team for admins).

Good to know

  • No keys here. Claude's connector dialog only takes a URL (plus optional OAuth fields). There is nowhere to paste a Basic-auth header, so StackJack Client ID/Secret credentials don't apply to Claude.ai or Claude Desktop.
  • Connections come from Anthropic's cloud. Even in Claude Desktop, the connector traffic originates from Anthropic's servers, not your machine. StackJack is publicly reachable, so this works without any setup — but don't expect the connection to appear from your office IP.
  • Your connection shows up in the portal so admins can see last-used time and call counts: a per-install connection becomes a read-only AI session after its first tool call, and a shared-app (CIMD) authorization becomes a Connected apps entry as soon as you approve the consent screen (see above). Admins see both per member on the Team page; you see your own in the read-only Your AI connections card on the MCP Setup page. See OIDC sessions and revoking access.

Tool limits

Claude Desktop caps a connector at 256 tools. When your catalog is larger, Claude Desktop re-sorts it alphabetically and then truncates — so the tools it keeps are simply the first 256 by name, and no ordering on StackJack's side can protect a specific tool from being dropped. claude.ai (web) publishes no fixed number, but large catalogs still degrade it: sessions get slow or fail as your connectors add up.

The fix is catalog mode. Switch StackJack to compact mode so it serves a small tool list and the AI finds any of your thousands of tools on demand (via stackjack_search_tools) instead of being handed the whole catalog — every tool stays reachable and every permission still applies. An admin must first enable catalog modes for your organization on Endpoints; until then StackJack serves the full tool list. Trimming your tool grants or connecting through a restricted client helps too, but catalog mode is what keeps a large catalog under the cap without hiding anything. See Choosing tools for each client and managing harness tool limits.

Claude caches the tool list. Changing catalog mode — in the Portal or via a ?tools= URL — will not reach a connector Claude has already added. To pick up the change, remove the StackJack connector and re-add it (or change its URL, which counts as a new connector).

Troubleshooting

  • Sign-in says no account was found — sign up in the portal first, or ask your team admin for an invite.
  • "Your access to this tenant has been revoked" — ask your admin to send a new invite.
  • For anything else, see Connection troubleshooting.