MCP Gateway People, roles and connections.

/mcp-gateway/access

Every person signs in as themselves. Roles decide which tools their AI can call, and a connector can hold more than one connection.

[ 02 // team roles ]
[ 02 ]

Four roles.
Two separate dials.

A team role decides what someone can manage in the Portal. A tool role, below, decides only which tools their AI can call. An Administrator and a Member can hold the same tool role.

one

Primary Owner

The account’s anchor: billing contact and identity-provider owner. Exactly one, created with the account.

any number

Co-owner

Full account control, the same as the Primary Owner for day-to-day management, including billing and ownership changes.

any number

Administrator

Manages everything operational: connectors, subscriptions, AI-agent credentials and the team. Cannot manage account billing, credits and the Anthropic key, ownership, region moves or the organization data-deletion request.

any number

Member

No management access. Members connect their AI assistants and use only the tools an admin assigned to them.

An owner is never restricted by their own member record. Tool restrictions do apply to Administrators, not only to Members. Owners create and manage MCP client credentials with the Administrators. Full capability matrix in the docs.

[ 03 // tool roles ]
[ 03 ]

Each person gets
exactly what they need.

Per-user sign-in and custom tool restrictions are on every plan, including Free.

Reusable bundles of tools

A custom role is a named bundle you build once and hand to as many people, invites and AI-assistant endpoints as you like. It is made of standing rules, not a snapshot, so new tools that match a rule are included automatically.

  • Scope a rule to everything, or to one connector
  • Select all tools, all read-only, non-destructive, one category, or specific tools
  • Limit a rule to one connection of a connector
  • With Microsoft Entra directory sync, roles follow your Entra groups

Per-user sign-in and custom tool roles are on every plan, including Free. Custom roles in the docs.

// Team of 5, one Pro subscription
Sarah  → all tools
Mike   → read-only
DevOps → tickets + assets
CI/CD  → create tickets only
Intern → search only
→ one endpoint, five policies
[ 04 // personal vendor sign-ins ]
[ 04 ]

Whose name is in the
vendor’s audit log?

Each person signs in to StackJack as themselves. Whether they also use their own vendor account depends on the connector.

Most connectors share one credential

When a connector uses an organization API key or service account, every member’s calls go to the vendor through that one identity, and the vendor’s audit log shows one service account. That is the intended design.

Five connectors can name the person

HaloPSA, NinjaOne, N-able N-central, Microsoft Azure and Microsoft Graph can identify each team member with their own vendor sign-in, so actions appear in the vendor’s audit logs under the real person. HaloPSA and NinjaOne need their sign-in mode for this.

A sign-in is not a team fallback

A credential made by signing in carries one person’s own access. StackJack will not run another member’s calls under it. A member without their own connection gets a refusal that names their fix. The primary owner and co-owners keep the shared sign-in.

[ 05 // several connections ]
[ 05 ]

More than one connection
of the same connector.

MSPs run the same product for many customers. A connector can hold as many named connections as you run.

Name a connection after the customer

An organization can hold several named connections of one connector: one HaloPSA per acquired company, or one Jamf, CrowdStrike or SentinelOne console per customer. Your AI reads the names, so “Acme Manufacturing” says more than “Jamf 2”.

Your AI names the one it wants

A connector with two or more connections gains an optional connection argument on every tool, and the tool’s description lists the names. Leave it out and the call runs against the default connection. A tool lists every connection of every connector, which one is the default and how each is doing.

Pin an endpoint to one connection

On MCP Setup, a client can be pinned to one connection of a connector. A pinned client uses that connection for every call, and naming any other connection is refused. A pin points at a shared connection. 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.

Connections do not change what you pay

A connector has one subscription, one plan and one monthly call limit, shared by all of its connections. Ten Jamf Pro connections are one Jamf Pro subscription.

[ 06 // faq ]
[ 06 ]

Questions.

Can I restrict an Administrator?

Yes. Tool restrictions apply to Administrators, not only to Members. To narrow someone who holds a custom tool role, change the role. An owner is never restricted by their own member record.

Does each person use their own vendor account?

StackJack brokers every call to the right connector using your organization’s credentials. A person can use their own vendor account instead, with a personal sign-in on HaloPSA, NinjaOne (NinjaRMM), Microsoft 365, Azure and N-able N-central. Without one, the vendor’s audit log shows the shared service account. In StackJack’s activity log, 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. A shared key made for the organization is logged under its own name, with no person.

What happens when someone leaves?

If an admin removes a person from the team, every AI tool they connected by signing in stops working on its next request. An admin can also revoke one connected app for one member on the Team page.

[ 08 // start ]

Jack into your stack.

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