works withyour AI.
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 — same tiles you’ll see in the portal. Each one connects in minutes with the auth flow it likes best.
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 remote MCP connector and ask ChatGPT about your tickets, fleet, tenants, and docs — with the same per-user policy as everyone else.
GitHub Copilot
Bring your MSP 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.
Windsurf & Continue
The whole family of MCP-capable coding assistants connects the same way — one URL, sign in, tools discovered.
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.
Five ways in. all standard.
Whatever auth your client prefers, we speak it — from paste-a-key simplicity to fully automatic registration. Fully compliant with the MCP authorization spec, including DCR and CIMD.
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.
API Key
Single-header simplicity for scripts, CI/CD, and custom agents. Scope it, rotate it, revoke it — live from the portal.
OAuth 2.0 PKCE
The full authorization-code flow, PKCE required (S256), RSA-signed JWTs, single-use rotating refresh tokens. Every teammate signs in as themselves — on every plan.
DCR · fully compliant
Dynamic Client Registration (RFC 7591): clients like Claude Desktop register themselves automatically — no portal step, no manual credentials. Rate-limited, expiring, same security pipeline.
CIMD · fully compliant
Client ID Metadata Documents: the newest MCP auth pattern, where the client identifies itself with a hosted metadata document — zero registration, cryptographically verifiable identity.
Whatever the method — same pipeline
Every flow lands in the same fail-closed pipeline: tenant resolution, authorization, tool allowlists, rate limits. 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 typed, validated data from your stack. Switch models tomorrow — nothing on the StackJack side changes.
Agent Runners: Claude-powered, BYOK-ready
Scheduled and webhook-driven Agent Runners execute on Anthropic’s Claude models with per-run credit billing — or bring your own Anthropic key on Enterprise and skip credits entirely.
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.