Your MCP endpoint

StackJack exposes your entire MSP stack to AI tools through a single MCP endpoint. MCP (Model Context Protocol) is the open standard AI assistants use to call external tools — when your AI tool "connects to StackJack," it is connecting to this endpoint.

The one URL

Your workspace has exactly one standard MCP endpoint. Copy it from MCP Setup in the portal — that card shows the address for your workspace, and it is the address to paste into every AI tool. A US workspace sees this one:

https://mcp.stackjack.io/mcp

That is the whole address. There is:

• One URL for your whole workspace — every connector you have set up (HaloPSA, ConnectWise, NinjaOne, and so on) is served through the same endpoint. Optional per-connector endpoints exist for AI tools that can only load a handful of tools, but they are an extra way to serve the same catalog, never a replacement: the URL above always serves everything you are entitled to.
• One URL for every team member — who you are is determined by how you sign in or which credential you use, never by the URL.
• One URL for every AI tool — Claude, ChatGPT, Cursor, VS Code, n8n, and any other MCP-capable tool all point at the same address.

Where to find it in the portal

1. Sign in to the portal and open MCP Setup in the left sidebar (the /endpoints page).
2. The top of the page shows two endpoint cards. The Standard endpoint card holds the URL above with a Copy button — that's the one most tools use.

The same URL also appears on the Dashboard and inside the first-login setup wizard.

Your region and your endpoint

Every workspace has one storage home region, and the region decides your hostname. The URLs in this documentation are written out as US examples so the shape is readable. They are not the only valid addresses.

Three rules follow from that, and they matter whenever you copy a URL out of a guide:

• Copy the address from your own MCP Setup page rather than from a guide. The card renders your workspace's real endpoint. A URL typed from the wrong region reaches a StackJack server that does not hold your organization, so the connection fails at sign-in or at credential check rather than with a helpful message.
• The compact and per-connector endpoints are regional too. Each has its own hostname on the same regional domain, and each is copied from the same page.
• Which region you are in is not something you choose per tool. It is set for the whole workspace. See Data residency, and Moving your organization to another region if you need to change it.

Standard and compact endpoints

The MCP Setup page shows two endpoint cards side by side:

• Standard endpoint — the URL above (https://mcp.stackjack.io/mcp in the US). It serves your full tool catalog. This is the right choice for almost every tool. It is what the rest of this documentation calls the primary endpoint: Primary endpoint. Your full tool catalog. Use it for most clients.
• Compact endpoint — a slimmed tool list for AI tools that cap how many tools they load (Microsoft Copilot Studio, Cursor, VS Code Copilot). In the US it reads https://compact.stackjack.io/mcp; other regions use their own compact hostname, so copy it from the card rather than typing it. It serves the meta search/run tools plus any tools you pin. It is also the Base URL of the Microsoft 365 Copilot connector. In one line: Compact endpoint. A folded catalog for clients with a small tool budget. Use it when a client caps tools.

The compact endpoint needs no setup: every connection to it is served the folded catalog, whatever your organization has chosen under Catalog defaults on the Settings page. That setting decides what the standard endpoint serves. Copy the compact address and paste it into a tool that caps its tool list, and that tool gets the short list on its first connection. See Catalog modes for the full explanation and per-tool guidance.

Beneath those two cards there may be a third option — one endpoint per connector. It comes last deliberately. The standard endpoint is the answer for almost everybody, the compact endpoint is the answer when a tool caps its list, and per-connector endpoints are for the narrower case where you want one AI client to see one connector and nothing else.

Per-connector endpoints

If you want to break your connectors out into per-connector endpoints, here are all the connector endpoints. Each one serves a single connector's tools plus the StackJack platform tools, instead of your whole catalog — useful when an AI client can only hold a few dozen tools, or when you simply want a "HaloPSA client" and a "NinjaOne client" that stay out of each other's way.

Where to get them. When per-connector endpoints are available to your workspace, MCP Setup lists them below the standard and compact cards — one copyable URL for each connector you are subscribed to — and the same list appears in the first-login setup wizard. If you do not see that list, per-connector endpoints are not published for your workspace yet. Nothing is broken and nothing is missing: the standard endpoint continues to serve every connector's tools exactly as it always has.

What the URLs look like. Each one is your region's MCP hostname with the connector's short name in front of it: https://{slug}.mcp.stackjack.io/mcp for the US region and https://{slug}.mcp-eu.stackjack.io/mcp for the EU region, where {slug} is the connector's short name — halo, cipp, ninjarmm, connectwise, msgraph, and so on. Copy the URL from MCP Setup rather than typing one by hand: a hostname that has not been published for your region does not resolve at all, so a guessed address fails as a network error rather than as a StackJack message.

How to use one:

Point one MCP client at this URL to get only this connector's tools. Your tool selection and subscriptions are unchanged.

Everything else about the connection is the same as the standard endpoint. The transport is Streamable HTTP, the same sign-in or credential works, your monthly plan caps are the same caps, and the StackJack platform tools (search, docs, support, session info) are served alongside the connector's own tools so the client can still find its way around.

What a per-connector endpoint is not:

The connector host is a serving profile, not a credential restriction; AllowedTools + subscriptions remain the only restriction boundary.

Choosing a per-connector URL changes what StackJack shows a client, not what that client is permitted to call. The same credential, signed-in session, or token works unchanged on the standard endpoint and gets the full catalog there — so a per-connector URL is a convenience for a client you control, never a fence around one you do not. If you need a real boundary, restrict the MCP client credential's tool selection or the person's tool roles; see How do I narrow a connection? for which control does which.

Transport: Streamable HTTP

The endpoint speaks Streamable HTTP, the current standard MCP transport. Any tool that supports "MCP over Streamable HTTP" (sometimes just labeled "HTTP") can connect. If your tool asks you to choose a transport, pick Streamable HTTP — not SSE, not stdio.

When a tool connects successfully, it identifies the server as StackJack ("Jack into your MSP stack with AI") with the StackJack logo.

What your AI tool sees after connecting

The tool list your AI assistant receives is filtered for you specifically:

• Only tools from connectors your workspace has active subscriptions for.
• Only tools included in each connector's plan tier.
• Only the tools you personally hold — the union of any tool roles assigned to you plus any extra tools picked for you individually. Owners and co-owners are not restricted this way on a sign-in connection: they see every tool.
• If the connection uses a manual credential, the credential has its own tool set (its roles plus its extras), and the result is the overlap of the two — a credential's limit applies to an owner as well.

Two people connecting the same AI product to the same endpoint can therefore see different tool lists — that is by design.

If you have not started using tool roles, nothing here changes for you: a person or credential holding no roles is served exactly the tools picked for them, as before.

Health check

The MCP server publishes an unauthenticated health endpoint. Use it as the first step when you are checking a connection from a particular machine. The US address is:

https://mcp.stackjack.io/health

Use your own region's hostname with /health on the end. A plain HTTP GET (browser or curl) returns a healthy or unhealthy status.

Read the result narrowly. A healthy response proves that this one request, from this machine, reached the server and the server answered. It does not prove that MCP transport is working, that your credential or sign-in is accepted, that your connector credentials are valid, or that every service the endpoint depends on is up. In particular, do not rule out a service or network-path problem on the strength of a healthy /health alone: a different port, a proxy that only allows some paths, or a fault behind the MCP route can all leave /health green.

If /health is healthy and your AI tool still cannot connect, keep going: check session information from the tool, check the connector's health on the Connectors page, and collect the error message and correlation ID. See Connection troubleshooting.

Rate limits

There is no per-minute or burst rate limit on the endpoint today. The enforcement point is your monthly plan cap — each connector subscription has a monthly tool-call allowance based on its plan tier. Usage against those caps is visible on the Dashboard and Billing pages.

Next steps

• How AI tools authenticate to StackJack — pick the right connection method.
• Building and Maintaining Automations from Your AI Assistant — beyond calling your connectors, a connected assistant can build an automation and keep it up to date, under your own permissions.
• On the MCP Setup page, the Connect your AI tool card has an Open the setup guide button that takes you straight to these step-by-step guides for every supported tool (ChatGPT, Claude, Cursor, VS Code, Copilot Studio, n8n, and more). The per-tool tabs that used to live on that page have been replaced by these guides so the steps stay in one place and current.