StackJack MCP Gateway.

/mcp-gateway Available now

One MCP endpoint connects Claude, ChatGPT, Cursor, Copilot and your own agents to the PSA, RMM, Microsoft 365, security and documentation tools you run. Each person signs in as themselves, and you decide which tools they can call.

132 connectors live // 21,269 tools free, every plan // Metadata only in the audit log // OAuth PKCE on every plan
↓
[ 03 // for your role ]
[ 03 ]

For your role.

What it changes for each person on your team. Each screen is a recreated example with sample data.

Owner / CEO

The problem

I find out a client lost us money after the quarter is over.

  • Ask which agreements lose money, what your effective hourly rate is and where recurring revenue stands. The answer comes from your PSA.
  • You pay per connector. Every connector has a free tier, and you upgrade only the ones that need more.
  • It works in the AI your team already uses: Claude, ChatGPT, Copilot and Cursor.
  • You decide who can call which tools, and every call is logged.

The profitability report is one of the HaloPSA reporting tools on Pro.

Your AI assistant + StackJack
Which client agreements lost us money this quarter?
halo_unprofitable_agreements_report
Two agreements ran below your cost rate of $100 an hour over the last three months, worst first:
AgreementHoursEffective rateMargin
Northwind: managed services86.5$72.83 an hour−37.3%
Contoso: server care46.0$91.30 an hour−9.5%

Every other agreement billed more than its hours cost.

Service manager and techs

The problem

Six tabs open to answer one question about one client.

  • Ask in plain English. The AI reads your PSA, RMM and Microsoft 365 and gives one answer.
  • It adds the note and logs the time on the ticket when you tell it to.
  • Each tech signs in as themselves, with the tools their role allows.
  • It works in the AI your team already uses.
Your AI assistant + StackJack
Which P1 tickets will breach SLA today, and is anything wrong with those devices?
halo_list_high_priority_ticketsninja_get_deviceninja_get_device_alerts
Three P1 tickets are due before 5 pm:
TicketClientSLA dueDevice
#48231Acme1:30 pmACME-FS01: disk 97% full
#48240Northwind3:00 pmNW-DC02: offline for 2 hours
#48244Acme4:45 pmNo alerts

vCIO / account manager

The problem

A day of exports before every quarterly review.

  • Tickets, hardware and Microsoft 365 for one client, in one answer.
  • Warranty dates come from your lifecycle tool, not from a spreadsheet.
  • MFA status comes from the client’s own Microsoft 365 tenant, through CIPP.
  • Ask the same question for the next client. Only the name changes.
Your AI assistant + StackJack
Prepare Acme’s quarterly review: tickets, devices out of warranty, users with no MFA.
halo_list_ticketsscalepad_lm_list_hardware_lifecyclescipp_list_mfa_users
Acme, last quarter:
AreaFindingDetail
Tickets112 closed18% fewer than the quarter before
Hardware9 devices out of warranty3 servers and 6 laptops
Microsoft 3654 users with no MFA2 of them are administrators

Security and compliance

The problem

The AI can reach our PSA and RMM. Who did what, and with which tool?

  • Every tool call is logged: the tool, the connector, the client, the person, the time and the result. The log does not keep the request parameters or the data a successful call returned.
  • Sign-ins and personal keys are logged under their person. A shared key is logged under its own name, with no person.
  • Tools are limited by role on every plan. A person’s AI can call only the tools you assigned.
  • Connector credentials stay in a dedicated secrets vault, encrypted at rest.
StackJack Portal
Activity logCall metadata only: the tool, connector, client, member, timing and outcome.
Export CSV
Time (UTC)ToolClientMemberStatus
Nov 12, 14:02:11halo_list_ticketsSign-in (Claude)Sam Cartersam@example.comOK
Nov 12, 14:02:13ninja_get_device_alertsSign-in (Claude)Sam Cartersam@example.comOK
Nov 12, 14:05:40halo_add_actionPriya Shah’s HaloPSA keyPriya Shahpriya@example.comOK
Nov 12, 14:10:02cipp_list_mfa_usersReporting script keyNo personOK
Nov 12, 14:11:27ninja_get_deviceSign-in (Cursor)Jordan Leejordan@example.comError
[ 04 // how it works ]
[ 04 ]

Plug in once.
Work the whole stack.

Your AI client connects to one endpoint. StackJack brokers every request to the right connector, with your credentials and the tools you allow.

1

Sign up for StackJack

Free tier on every connector. No credit card, no time limit.

2

Set up your connectors

Paste an API key or sign in with OAuth: HaloPSA, NinjaOne (NinjaRMM), CIPP, whatever you run. Credentials go to a dedicated secrets vault, encrypted at rest.

3

Connect your AI

Add your MCP URL to Claude, ChatGPT or any MCP client. Sign in. Done.

4

Start asking

Questions that used to mean an afternoon of tab-hopping across three platforms are now one prompt.

An endpoint in the StackJack Portal, showing the address an AI client connects to and the tools it may use.
One address for your AI client, and the tools it may use.
[ 05 // plans and prices ]
[ 05 ]

Priced per connector.
Free on every one.

You pay per connector, on the plan each one needs. Each connector page shows its own price.

Free

$0

never expires, no card

The core read tools on every connector, 21,269 free tools across the catalog. 100 calls a month per connector.

Recommended

Pro

$19 to $99

per connector per month

Every tool, including write and action tools. 5,000 calls a month per connector.

Business

$29 to $199

per connector per month

The same tools as Pro. 50,000 calls a month per connector.

Enterprise

Custom

for builders and vendors

A custom call allowance and every tool. Contact us

Each connector card shows its own price. Two or more paid connectors save 15% to 40% on the whole subscription. Per-user sign-in and custom tool roles are on every plan.

[ 06 // faq ]
[ 06 ]

Questions.

Will 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. Catalog modes

Does StackJack store any of my business data?

Not on the gateway path. Interactive tool calls pass through StackJack. The audit log keeps metadata: who called which tool, when, how long it took and how it ended. It does not keep the parameters or the data a successful call returned. A failed call also keeps its error text, which can include text from the vendor. If a result is too large to send back to the AI, StackJack saves it to a temporary download link for you. Automations and AI Governance keep the data their own pages describe. Credentials live in a dedicated secrets vault, encrypted at rest.

Does each person use their own vendor account?

StackJack brokers every call to the right connector using your organization’s credentials. On HaloPSA, NinjaOne (NinjaRMM), Microsoft 365, Azure and N-able N-central, each person can use their own vendor account instead. Everyone signs in to StackJack as themselves, on every plan. Calls made with a sign-in, or with the personal key a member gets when they connect their own account on Connectors, are attributed to that person in the activity log. A shared key made for the organization is logged under its own name, with no person. People, roles and connections

Which AI clients work?

Any client that supports remote MCP over Streamable HTTP, with any standard auth method. See the supported clients.

Is there a limit on calls?

Each connector subscription has a monthly allowance of successful calls, and the Portal always shows the limit that applies to you. Usage, limits and audit log

[ 07 // start ]

Jack into your stack.

Start free. Every connector includes a free tier that never expires, and every plan includes per-user sign-in.