Connect
Optimize
Secure
MCP Gateway
MCP Gateway
for Intercom's Fin AI Agent
One MCP gateway to connect Fin AI Agent 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 Fin AI Agent through one URL.
Act across all your apps
from inside Intercom
One MCP gateway, every enterprise SaaS your Fin 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 Fin 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 Fin AI 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 connector in Fin.
Open Settings → Integrations → Data connectors, click the Custom MCP tile, paste the StackOne gateway URL, save as Draft, then Set live.
Settings → Integrations → Data connectors
Custom MCP
Display name
StackOne
MCP server URL
https://api.stackone.com/mcp/{...}
Let Fin decide when to use this tool
Enabled
Set live
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.
List tickets (enabled)
Get customer (enabled)
Read account context (enabled)
Update record (disabled)
Process refund (disabled)
4
Ask Fin in plain English.
StackOne maps your prompt to the right action in the right system. Done.
"Check this customer's Stripe refund history and pull their HubSpot account tier before drafting a reply."
stripe_list_refunds
Completed
hubspot_get_company
Completed
domain: acme.com
tier: Enterprise
renewal: 2026-09-14
Drafted reply in the Intercom conversation: "I see one Stripe refund last quarter — applying credit to your Enterprise renewal."
Get Fin AI
to do more across your stack
Cross-app workflows your Fin agent now runs in seconds instead of click-throughs.
Customer Context
> Pull Salesforce account tier into the Intercom conversation before Fin responds.
Billing & Payments
> Check this customer's Stripe refund history before Fin escalates the ticket.
Engineering & Bug Tracking
> File a Jira bug from this Intercom ticket and return the ticket ID to the customer.
Knowledge & Internal Docs
> Search internal Confluence wikis when the Help Center misses an answer.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 320+ MCP servers. Same agent context. Pick yours.
Frequently Asked Questions
Fin AI Agents act across enterprise SaaS through StackOne's MCP gateway. Setup takes a few clicks: in your Intercom workspace open Settings → Integrations → Data connectors, find the Custom MCP tile, paste the StackOne gateway URL with your account ID and token, save as Draft, then click Set live. Available immediately to your Fin agent and 320+ pre-built SaaS connectors are reachable through that single connection. Full walkthrough in the Intercom MCP connectors docs. Available where Fin MCP is supported in your 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.
Fin can access enterprise SaaS like Salesforce, HubSpot, Attio, Jira, GitHub, Chargebee, Confluence, Notion, and PostHog through the StackOne MCP gateway — 320+ pre-built connectors in total. StackOne extends Fin's reach beyond Intercom's first-party MCP partners (Stripe, Shopify, Linear) into CRM, billing, dev tools, and internal knowledge. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
Fin ships 3 first-party MCP partners (Stripe, Shopify, Linear). StackOne adds the other 320+ — every app reachable through one Custom MCP connection instead of 3+ 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 Intercom's Data connectors settings, controlled by workspace 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:
- Intercom's first-party MCP connectors for Stripe, Shopify, or Linear 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 Fin.
One MCP gateway, 320+ pre-built SaaS connectors. Set up in 5 minutes.