Connect
Optimize
Secure
MCP Gateway
MCP Gateway
for Databricks Agent Bricks agents
One MCP gateway to connect Agent Bricks to 320+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.
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 320+ 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 320+ pre-built SaaS integrations exposing 21,000+ actions, all reachable from your Agent Bricks agent through one URL.
Act across all your apps
from inside Databricks
One MCP gateway, every enterprise SaaS your Agent Bricks agent
could ever need to act on.
Coverage
320+ connectors.
21,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 Agent Bricks 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 Agent Bricks 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 Agent Bricks.
Open Settings → Agent Bricks → AI connectors, enable Custom MCP servers, then paste the StackOne gateway URL. Available immediately to every AI Agent in your workspace.
Settings → Agent Bricks → AI connectors
Add Custom MCP server
Display name
StackOne
Server URL
https://api.stackone.com/mcp/{...}
Authentication
API Key
Save connection
2
Connect each SaaS integration in StackOne.
OAuth or API key per app, done once in your dashboard. Tokens stay server-side.
3
Scope agent actions.
Read-only, specific objects, or per-role exposure. Toggle from the StackOne dashboard.
Query feature store (enabled)
Read MLflow run (enabled)
Append to Delta table (enabled)
Modify production model (disabled)
Drop table (disabled)
4
Ask your Agent Bricks agent in plain English.
StackOne maps your prompt to the right action in the right system. Done.
"Pull this quarter's churn signals from HubSpot deal stages and the latest PostHog product-usage drop-offs, then write an enriched feature row into the prod.churn.features Delta table and log to MLflow."
Databricks hubspot_list_deals
Completed
posthog_query_events
Completed
event: $pageview, $session_dropoff
window: last 30 days
result: 8,400 sessions joined to 312 HubSpot deals
Wrote 312 enriched rows to prod.churn.features. Logged as MLflow run churn_v0.7_features.
Get your Agent Bricks agent
to do more across your stack
Cross-app workflows your Agent Bricks agent now runs in seconds instead of click-throughs.
Model Output Activation
> Push the churn-score from MLflow into HubSpot contact properties so reps see it in their workflow.
Feature Pipeline Enrichment
> Pull live PostHog product events into a Delta table feeding the Online Feature Store.
ML Experiment & Run Context
> Open a Linear ticket when MLflow detects model drift, with the run ID linked.
Lakehouse → GTM Activation
> Push a Unity-Catalog-governed account cohort to Salesforce for a targeted campaign.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 320+ MCP servers. Same agent context. Pick yours.
Frequently Asked Questions
Agent Bricks agents reach enterprise SaaS through a custom MCP server hosted on Databricks Apps. In your workspace, open Compute → Apps → Create app → MCP Server template (Agents category), name the app starting with mcp- (e.g. mcp-stackone), point it at the StackOne gateway URL with OAuth, and create. Wire it into Supervisor Agent or test directly in AI Playground. Available to every Agent Bricks agent in your workspace, and 320+ pre-built SaaS connectors are reachable through that one app. Full walkthrough in the Host a custom MCP server docs. Requires a Unity-Catalog-enabled workspace.
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 320+ 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.
Agent Bricks agents can access enterprise SaaS like Salesforce, HubSpot, PostHog, Linear, Workday, Greenhouse, Stripe, Intercom, and Slack through the StackOne MCP gateway — categories that complement Databricks's first-party MCP partners (data vendors like S&P Global, FactSet, You.com, Glean). 320+ pre-built connectors total. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
Databricks Agent Bricks ships 6 first-party MCP partners — all data vendors (You.com, Glean, S&P Global, FactSet, D&B, Moody's). StackOne adds the other 320+ operational SaaS — every app reachable through one Custom MCP Server 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: the StackOne MCP Databricks App (OAuth on the app config, controlled by Databricks workspace admins via Unity Catalog permissions), 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:
- Databricks's 6 first-party data-vendor MCP partners (You.com, Glean, S&P Global, FactSet, D&B, Moody's) 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 Databricks.
One MCP gateway, 320+ pre-built SaaS connectors. Set up in 5 minutes.