Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

MCP Gateway

MCP Gateway
for Now Assist agents

One MCP gateway to connect Now Assist to 310+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.

DrataGPLocalyzeFlipMindtoolsScreenloop

What is an MCP gateway?

An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple MCP servers via the open Model Context Protocol (opens in new tab). Some gateways act as proxies, routing traffic to MCP servers customers operate themselves. Others provide the underlying MCP servers as a managed service.

StackOne is the managed kind. We provide pre-built MCP servers for 310+ enterprise SaaS apps, including ones with no official MCP server today. For each app you connect, StackOne provides the MCP protocol layer, the SaaS API integration, action coverage, and the auth orchestration framework. Authentication is configured per app per organization — your team registers OAuth credentials with the SaaS provider, links them in StackOne, and end users then authorize access through that flow. Once set up, the agent reaches every connected app through one URL, with token storage, refresh, and per-user scoping handled by StackOne.

StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — bundles 310+ pre-built SaaS integrations exposing 20,000+ actions, all reachable from your Now Assist agent through one URL.

Act across all your apps
from inside ServiceNow

One MCP gateway, every enterprise SaaS your Now Assist agent
could ever need to act on.

Coverage

310+ connectors.
20,000+ tested actions.

Every action is built and maintained by StackOne, tested against the live API, and updated when vendors change their endpoints.

Browse all connectors

Trust

Auth & governance,
simplified.

StackOne handles OAuth, API keys, refresh, and scopes for every connector, giving enterprise IT full control through auth configs in a multi-tenant setup.

Agent Auth

Performance

Agent context window,
managed.

Tool Discovery and Code Mode keep the Now Assist agent's context lean — only relevant actions, no raw response noise. Sharper agents, lower token costs.

Tools Discovery

Security

Agent security,
built in.

Defender scans every MCP tool response for prompt injection in real time. Up to 97.44%¹ detection, 0.2% false positives. SOC2, HIPAA, CCPA, GDPR compliant.

Prompt Injection Defense

¹ Jayavibhav test, 65,000 samples.

Connect the Now Assist agent
to more apps in 4 steps

From auth config to first agent tool call in 5 minutes.

1

Add StackOne as a Custom MCP server in ServiceNow.

Open AI Agent Studio → Settings → Tools and Connectors, click Add MCP server, choose the OAuth 2.1 flow, paste the StackOne gateway URL, and save. Available immediately to every Now Assist agent in your instance.

AI Agent Studio → Settings → Tools and Connectors

Add MCP server

Name
StackOne
Server URL
https://api.stackone.com/mcp/{...}
Authentication type
OAuth 2.1
Save
View setup guide (opens in new tab)
2

Connect each SaaS integration in StackOne.

OAuth or API key per app, done once in your dashboard. Tokens stay server-side.

workday
okta
salesforce
jira
slack
Browse all connectors
3

Scope agent actions.

Read-only, specific objects, or per-role exposure. Toggle from the StackOne dashboard.

List incidents (enabled)
Get HR case (enabled)
Add work note (enabled)
Resolve incident (disabled)
Delete record (disabled)
Agent Auth
4

Ask your Now Assist agent in plain English.

StackOne maps your prompt to the right action in the right system. Done.

"Employee filed an HR case about a missing laptop. Check Workday for start date + manager, Okta for account provisioning, then comment on the case and reassign to the right group."

ServiceNow
workday_get_employee
Completed
okta_list_user_apps
Completed
user: e.delorme@acme.com
filter: assignment_status = active
result: 3 of 12 apps provisioned (Slack ✓, Jira ✓, Salesforce ✗)

Workday says start date 2026-05-15, manager K. Patel. Okta shows 3/12 apps provisioned. Commented on HR case HRC0012394 and reassigned to IT-Provisioning.

Get your Now Assist agent
to do more across your stack

Cross-app workflows your Now Assist agent now runs in seconds instead of click-throughs.

IT Service Operations

> Cross-reference Jira incident history with the open ServiceNow ticket and surface duplicates.

Azure DevOpsCloudflareLinearBitbucketSupabaseGitLabTerraformOneLogin
Employee Lifecycle & HR Cases

> Pull Workday start date and manager and enrich the open HR onboarding case.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Identity, Access & Asset Posture

> Check Okta group membership before approving the access request.

Vendor, Procurement & Spend

> Look up the supplier in SAP SuccessFactors and attach to the purchase request.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify

Connect any Enterprise AI Agent
to the StackOne MCP Gateway

Same 310+ MCP servers. Same agent context. Pick yours.

Frequently Asked Questions

Now Assist agents act across enterprise SaaS through StackOne's MCP gateway. Setup happens in AI Agent Studio: open Settings → Tools and Connectors, choose Add MCP server, pick the OAuth 2.1 flow, paste the StackOne gateway URL, and save. Available immediately to every Now Assist agent in your instance, and 310+ pre-built SaaS connectors are reachable through that single connection. Full walkthrough in the Add MCP server with OAuth 2.1 docs. Requires Now Assist Pro Plus or Enterprise Plus.
An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple MCP servers via the Model Context Protocol. Some gateways route traffic to MCP servers customers operate themselves; others provide the MCP servers as a managed service. StackOne is the managed kind — we provide pre-built MCP servers for 310+ enterprise SaaS apps, including ones with no official MCP server today. Authentication is configured per app per organization: your team registers OAuth credentials with the SaaS provider, links them in StackOne, and end users authorize access through that flow. Once set up, the agent reaches every connected app through one URL.
Now Assist agents can access enterprise SaaS like Workday, Okta, Salesforce, HubSpot, Greenhouse, SAP SuccessFactors, Jira, Slack, and Microsoft Teams through the StackOne MCP gateway — 310+ pre-built connectors in total. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
ServiceNow Now Assist ships a short list of first-party MCP partners centered on Microsoft, Workday, and Adobe. StackOne adds the other 310+ — every app reachable through one Custom MCP server registration instead of one per app, auth managed once in the dashboard, and tool definitions loaded only when relevant to the prompt.
Credentials sit at three layers: the StackOne MCP server record (OAuth 2.1 in AI Agent Studio Settings, controlled by ServiceNow platform admins), SaaS connector credentials (server-side in your StackOne dashboard), and per-user OAuth or session tokens (server-side, scoped per user). StackOne stores OAuth tokens and API keys, refreshes them automatically, and only exposes the actions you've authorized to the agent.
Skip the StackOne MCP gateway when any of these is true:
  • ServiceNow's first-party Now Assist integrations (Microsoft 365, Workday, Adobe) already cover your apps
  • You only use a handful of actions across a few apps
  • You don't need multi-tenancy, per-user permissions, or per-action scoping
  • Indirect prompt injection isn't a concern
  • Your MCP provider already does tool discovery and server-side execution to keep the agent context lean

Connect All Your Apps to ServiceNow.

One MCP gateway, 310+ pre-built SaaS connectors. Set up in 5 minutes.