MCP Gateway One endpoint for every AI client.
Copy one address from the Portal and paste it into any AI tool that speaks remote MCP. Who you are comes from how you sign in, never from the address.
One address.
Everyone, every tool.
Your workspace has exactly one standard MCP endpoint. Copy it from MCP Setup in the Portal and paste it into every AI tool.
One URL for your whole workspace
Every connector you set up, HaloPSA, ConnectWise, NinjaOne and the rest, is served through the same endpoint.
One URL for every team member
Who you are comes from how you sign in or which credential you use, never from the address.
One URL for every AI tool
Claude, ChatGPT, Cursor, VS Code, n8n and any other tool that speaks remote MCP point at the same address.
Your region sets the host
A US workspace uses mcp.stackjack.io. An EU workspace uses mcp-eu.stackjack.io. Copy the address from your own MCP Setup page rather than typing it, because the region is set for the whole workspace.
The standard one is the answer
for almost everybody.
The other two exist for the narrower cases. All three serve the same catalog and apply the same permissions.
Standard endpoint
Your full tool catalog. Use it for most clients. It is the address the rest of this site means by “the MCP URL”.
Compact endpoint
A slim tool list for AI tools that cap how many tools they load, such as Microsoft Copilot Studio, Cursor and VS Code Copilot. It serves the search and run tools plus any tools you pin, and the AI finds any other tool on demand. US: https://compact.stackjack.io/mcp. EU: https://compact-eu.stackjack.io/mcp. It needs no setup. Catalog modes.
Per-connector endpoints
One connector’s tools plus the StackJack platform tools, for an AI client that can only hold a few dozen tools or that should see one product and nothing else. MCP Setup lists them when they are available to your workspace.
An endpoint is a serving profile, not a permission. Which tools a connection may call is decided by the person’s roles, an API credential’s tool list and your connector subscriptions. See people, roles and connections.
Paste the URL.
Sign in. Done.
There are three first-run paths. Which one you see depends on the AI tool, and you do not choose between them.
| Path | Clients | What the first run needs |
|---|---|---|
| Paste the URL, sign in | ChatGPT, Claude.ai, Claude Desktop, Claude Code, Cursor, VS Code with Copilot | Paste the URL, then complete the StackJack sign-in when the tool asks. No keys to copy. |
| Browser sign-in | Windsurf, Gemini CLI, OpenAI Codex, Copilot Studio | Add the remote server. If prompted, register or configure the OAuth client once, then sign in in the browser. |
| Paste a credential | Amazon Q, Cline, n8n, Make, Zapier, other | A generated Client ID and Secret, or an API key. Owners, co-owners and administrators create it on MCP Setup. |
As you, with the tools you hold
A sign-in connects the tool as you, with exactly the tools your roles and extras give you, and your activity is attributed to you. There is no StackJack secret to copy or rotate. If an admin removes you from the team, every AI tool you connected this way stops working on its next request.
Shared credentials are shared
A Client ID and Secret or an API key made for the organization has its own tool list. It does not say who is using it, so calls made with it carry no member attribution: the activity log shows the key under its own name, with no person. Use it for scripts and tools that cannot sign in. A personal key is different: the personal key a member gets when they connect their own account on Connectors is bound to that member and uses their own connection, and its calls are attributed to that person in the activity log.
Microsoft 365 Copilot is added once by a Microsoft 365 admin with StackJack’s published registration ID. The full client list, the five auth methods and the models behind them are on Supported AI clients. Setup guides for each client are in the docs.
Questions.
Which AI clients work?
Any client that supports remote MCP over Streamable HTTP, with any standard auth method. The named clients are highlights, not a whitelist. See the supported clients.
Is the address different for each person?
No. One address serves the whole workspace. What each person can do depends on how they sign in and on their roles.
Does my AI client load all 42,041 tools?
No, and it does not need to. Clients such as Claude Desktop, Cursor and Copilot cap the tool list, so StackJack can serve a compact catalog instead. The AI searches for the tool it needs and runs it, and every permission still applies. Use the compact address, or turn on catalog modes in Settings.
Keep reading.
Jack into your stack.
Start free. Every connector includes a free tier that never expires, and every plan includes per-user sign-in.