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

SAP Joule MCP Server

Turn SAP Joule into an enterprise agent

Let your employees delegate real work to SAP Joule across all their apps, under their own identity and permissions.

DrataGPLocalyzeFlipMindtoolsScreenloop

Get SAP Joule to work.
Not just chat.

One connection to StackOne, and SAP Joule gets scoped access to every app your employees use, to act on their behalf.

Connect

Make every system AI-ready

Give your AI access to 470+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Secure

Keep AI under control

Enforce identity-based access, screen every response for prompt injection, and audit every action.

Optimize

Trust what AI delivers

Keep your agent sharp with lean tool loading and boost reliability with the Falcon execution engine. Pre-synced data for faster context is coming soon.

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)
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, 450+ 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

Not everyone on SAP Joule?
Your integration layer stays the same.

The same setup works across SaaS agents like Atlassian Rovo, Notion, and every other MCP client.

Explore MCP clients

Frequently Asked Questions

You connect SAP Joule to the StackOne MCP gateway in two stages: register the gateway URL as an HTTP destination in BTP Cockpit → Connectivity → Destinations (no /mcp suffix), then in Joule Studio Agent Builder, click Add MCP Server and pick it. See SAP Help.
You can connect SAP Joule to 470+ live MCP servers through StackOne, spanning CRM, HRIS, ATS, ticketing, and finance — Salesforce, Workday, Greenhouse, and more. Each is reachable through one gateway URL instead of wiring up servers app by app. Browse the full list in the directory on this page, or build your own.
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 tokens scoped to what each person authorized.
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 use only a handful of actions across a few apps
  • You don't need multi-tenancy or per-action scoping
  • Prompt injection isn't a concern
  • Your provider already does tool discovery and server-side execution

Connect All Your Apps to SAP Joule.

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