Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery
StackOne
Connectors
Pricing
Login
Book Demo Start Free
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

Explore More Use-Cases
Next up: Meet us at Glean:GO 2026
StackOne
Connectors
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

Use-Cases
Pricing
Book Demo Start Free

MCP Gateway

MCP Gateway
for SAP Joule

One MCP gateway to connect SAP Joule to 470+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.

Start Free
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 470+ 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 470+ pre-built SaaS integrations exposing 28,000+ actions, all reachable from your SAP Joule agent through one URL.

Act across all your apps
from inside SAP Joule

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

Coverage

470+ connectors.
28,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 your Joule 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 SAP Joule
to more apps in 4 steps

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

1

Add StackOne as an MCP Server in Joule Studio.

Register the StackOne gateway as a BTP Cockpit → Destinations entry (with sap-joule-studio-mcp-server=true), then add it from your agent's Tools panel in Joule Studio → Agent Builder.

Joule Studio → Agent Builder → Tools

Add MCP Server

Toolkit name
StackOne
BTP Destination
stackone-mcp-gateway
Authentication
OAuth2ClientCredentials
Save toolkit
View SAP setup docs (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
greenhouse
hubspot
jira
intercom
Browse all connectors
3

Scope agent actions.

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

List records (enabled)
Get record (enabled)
Run workflow (enabled)
Update record (disabled)
Delete record (disabled)
Agent Auth
4

Ask your SAP Joule agent in plain English.

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

"Reconcile this week's HubSpot pipeline against open Workday reqs and draft the Q3 hiring readout."

SAP Joule
hubspot_list_deals
Completed
workday_list_open_positions
Completed
department: Sales, Engineering
stage: approved, posted
result: 14 reqs open

Reconciled 47 HubSpot deals to 14 open Workday reqs. Drafted the Q3 Hiring Readout in Joule Studio.

Connect SAP Joule to
any Enterprise MCP server

One MCP gateway, 470+ pre-built SaaS connectors SAP Joule can act on right away.

Need another connector? Build one with the AI Connector Builder

Get SAP Joule
to do more across your stack

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

HR & Talent Ops

> Sync open Workday requisitions with the Joule hiring agent's next-step plan.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Modern CRM & Sales Engagement

> Pull HubSpot deal stages into the Joule pipeline-review brief.

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
Customer Support & Service

> Cluster Zendesk escalations from this week and update the Joule service playbook.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa
Dev & Project Ops

> File Jira tickets for every change blocking your S/4HANA rollout.

Azure DevOpsCloudflareBitbucketGitLabLinearTerraformSupabaseOneLogin
Explore more AI agent use cases

Connect any Enterprise AI Agent
to the StackOne MCP Gateway

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

Notion AI Agent
Glean
Microsoft 365 Copilot
Atlassian Rovo
ServiceNow Now Assist
IBM watsonx Orchestrate
Snowflake Cortex
Databricks Agent Bricks
AWS Bedrock AgentCore
Google Vertex AI
Intercom Fin
Zendesk
Retool Agents
Cohere North
Perplexity Comet

Frequently Asked Questions

Joule agents built in Joule Studio consume external MCP servers through SAP BTP Destinations. Two stages: (1) In BTP Cockpit → Subaccount → Connectivity → Destinations → New Destination, register the StackOne gateway URL as an HTTP destination (do NOT append /mcp — Joule Studio adds it) and set the additional property sap-joule-studio-mcp-server to true. (2) In SAP Build Lobby → Joule Studio Agent Builder, open your agent's Tools panel and click Add MCP Server, then pick the destination from step 1. Full walkthrough in the SAP Help docs. Requires SAP BTP + SAP Build entitlement.
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 470+ 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.
You can connect SAP Joule to 470+ live MCP servers through StackOne — one managed MCP server for every enterprise app in the catalog, spanning CRM, HRIS, ATS, ticketing, finance, and more (Salesforce, Workday, Greenhouse, ServiceNow, NetSuite, HubSpot, and Zendesk among them). Each is reachable through the single gateway URL, so you add them all with one connection instead of wiring up servers app by app. Browse and search the full list in the directory on this page, or build one with the AI Connector Builder.
SAP Joule Studio ships 4 first-party MCP partners (Salesforce, ServiceNow, Microsoft 365, Slack) plus SAP-native systems. StackOne adds the other 470+ — every app reachable through one BTP Destination registration instead of N separate ones, auth managed once in the dashboard, and tool definitions loaded only when relevant to the prompt.
Credentials sit at three layers: your StackOne API token (embedded in the gateway URL stored in your SAP BTP Destination, governed by your Cloud Identity Services tenant), 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:
  • An existing SAP first-party Joule Studio partner already covers your apps (Salesforce, ServiceNow, Microsoft 365, Slack)
  • 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 SAP Joule.

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

Start Free Book Demo