works with your AISupported AI clients.
One endpoint, mcp.stackjack.io, and every major AI client jacks in. If it speaks remote MCP, it works with StackJack. No SDK, no plugin, no lock-in.
The big ones, first-class.
These are the clients our users connect every day. The docs have a setup guide for each one.
Claude
Anthropic’s clients are the reference MCP experience. Add StackJack as a remote server and Claude discovers every tool you’re allowed to use: in the browser, on desktop, or in the terminal.
ChatGPT
Connect StackJack as a custom connector and ask ChatGPT about your tickets, fleet, tenants and docs, with the same per-user policy as everyone else. Needs a paid ChatGPT plan with Developer mode, on the web. Choose OAuth and sign in inside the create dialog.
Microsoft 365 Copilot
A Microsoft 365 admin adds StackJack as a Copilot connector once. Each person then signs in with their own StackJack account, so everyone gets only the tools they hold. Microsoft built Copilot connectors for search and fetch, so use a Copilot Studio agent for write work.
Microsoft Copilot Studio
Add StackJack as an MCP tool in your agent with OAuth 2.0 and dynamic discovery. Use the compact address, because Copilot Studio limits tools per server.
Microsoft Foundry
Add StackJack as a custom MCP tool with a Client ID & Secret or an API key. Give each Foundry project its own credential and use the compact address.
GitHub Copilot
Bring your IT stack into the editor. Copilot’s MCP support means your scripts, runbooks, and tickets are one prompt away while you work.
Cursor
Point Cursor’s MCP config at StackJack and its agent mode can pull real data from your PSA and RMM while it builds your automations. Cursor counts tools across all of your MCP servers, so use compact or minimal mode.
Windsurf
Add StackJack as a remote MCP server: one URL, sign in, tools discovered. Other MCP-capable editors connect the same way.
Gemini CLI and OpenAI Codex
Add StackJack as a remote server and sign in in the browser.
Amazon Q and Cline
Paste a generated Client ID & Secret to connect. Recent builds can also sign in with OAuth in the browser.
n8n, Make and Zapier
Tools that run without a person at the keyboard use a generated Client ID & Secret or an API key. n8n 1.119 and later can also sign in with OAuth2, so calls are attributed to a person.
Custom agents
Building your own? Any agent framework that speaks remote MCP over Streamable HTTP plugs straight in, with scoped credentials and tool allowlists as guardrails.
Let’s be plain about it: StackJack works with absolutely any client that supports remote MCP, via any auth method the standard supports. The tiles above are highlights, not a whitelist. If your client speaks Streamable HTTP MCP, it already works.
Clients with a tool limit
Cursor, Windsurf, VS Code with GitHub Copilot and Microsoft Copilot Studio cap how many tools they load, and StackJack has 42,041 tools. Use the compact address for those clients: https://compact.stackjack.io/mcp (EU: https://compact-eu.stackjack.io/mcp). It serves a short list, and the AI finds any other tool on demand. For the smallest budgets, such as Cursor, choose minimal mode in Settings. Every permission and plan limit still applies.
Three ways in. all standard.
Sign in as yourself, or paste a credential. Sign-in works with clients that register themselves (DCR) and clients that publish a metadata document (CIMD).
OAuth 2.0 PKCE
Every teammate signs in as themselves, on every plan. PKCE (S256) is required. Clients that support Dynamic Client Registration register themselves, and clients that use Client ID Metadata Documents identify themselves with a hosted document, so there is nothing to set up in the Portal.
Client ID & Secret
Classic HTTP Basic. Create an MCP client in the portal, get a 256-bit secret (shown once, stored as a BCrypt hash), and drop both into any client config. Works everywhere. It is a shared credential with its own tool list.
API Key
Single-header simplicity for scripts, CI/CD and custom agents. The key starts with sjk_ and creating one needs an explicit risk acknowledgment. Scope it, rotate it, revoke it from the portal.
Whatever the method, same pipeline
Every flow lands in the same fail-closed pipeline: tenant resolution, authorization, tool allowlists, monthly call allowances. Auth choice is convenience, never a security downgrade. Read the security brief →
Bring any model your client can drive.
StackJack sits behind the client, not the model, so model choice is yours. Whatever your harness runs, the tools are the same.
Chat & IDE use: the model is your call
For interactive use, StackJack is model-agnostic by design. The client harness owns the conversation and the model; StackJack answers tool calls with the vendor’s own data, and with a typed error when a call fails. Switch models tomorrow. Nothing on the StackJack side changes.
Automations: Claude, or a model on your Azure Foundry
Scheduled and webhook-driven Automations run on Anthropic’s Claude models, or on Claude or another model in your own Azure Foundry. On a flat BYOK plan they run on your Azure Foundry or your own Anthropic key and use no credits. Or pay per run with credit packs.
One URL. that’s the integration.
Client not listed above?
It almost certainly works anyway: the list is highlights, not limits. If your client speaks remote MCP and any standard auth method, it connects. Stuck on a config? We’ll walk you through it. Real humans, one business day.