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 Cohere North

One MCP gateway to connect Cohere North 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 Cohere North agent through one URL.

Act across all your apps
from inside Cohere North

One MCP gateway, every enterprise SaaS your North 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 your Cohere North 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 Cohere North
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 North Agent Studio.

In your North workspace, open Agent Studio → Tools → Add MCP server, paste the StackOne gateway URL (StreamableHTTP transport), and enable for your agent. Exact admin labels may vary by tenant.

Agent Studio → Tools

Add MCP server

Display name
StackOne
Server URL
https://api.stackone.com/mcp/{...}
Transport
StreamableHTTP
Save server
View Cohere Agent Studio 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.

salesforce
workday
jira
github
confluence
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)
Search documents (enabled)
Update record (disabled)
Delete record (disabled)
Agent Auth
4

Ask your Cohere North agent in plain English.

StackOne maps the agent's tool call to the right action in the right system. Done.

"Search Confluence policies for SOC 2 controls and draft a compliance memo against this quarter's findings."

Cohere North
confluence_search_pages
Completed
jira_list_issues
Completed
label: soc2-control
status: open, in_progress
result: 6 open findings

Drafted the Q3 SOC 2 Memo citing 12 Confluence policies and 6 open Jira findings.

Get Cohere North
to do more across your stack

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

Customer & Sales

> Pull Salesforce pipeline and surface deal risks ahead of the quarterly close.

SalesforceZoho CRMPipedriveFreshsalesHubSpotPardotCloseJustCall
HR & Recruiting

> Query Workday org charts and surface candidate status from Greenhouse.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Engineering & Roadmap

> Pull every Jira ticket blocking the release and link the impacted PRs.

Azure DevOpsCloudflareLinearBitbucketSupabaseGitLabTerraformOneLogin
Knowledge & Docs

> Search Confluence policies and draft a compliance memo your auditors can sign off.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa

Connect any Enterprise AI Agent
to the StackOne MCP Gateway

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

Frequently Asked Questions

Cohere North agents (GA since August 2025) consume external MCP servers through Agent Studio. In your North workspace, open Agent Studio → Tools → Add MCP server, paste the StackOne gateway URL with your StackOne token in the auth header, and save. 310+ pre-built SaaS connectors are reachable through that single MCP server. North supports the StreamableHTTP transport. Exact admin labels may vary by tenant — see the Cohere North Agent Studio docs. Enterprise plan required.
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.
Cohere North agents can access enterprise SaaS like Salesforce, HubSpot, Workday, Greenhouse, BambooHR, Jira, GitHub, Linear, Notion, Confluence, and Microsoft 365 through the StackOne MCP gateway — 310+ pre-built connectors in total. StackOne extends North beyond its small first-party connector list (Gmail, Slack, Salesforce, Outlook, SharePoint, Linear). New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
Cohere North ships 6 first-party connectors (Gmail, Slack, Salesforce, Outlook, SharePoint, Linear) plus announced partners (Omnea, Atlassian). StackOne adds the other 310+ — every app reachable through one 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: your StackOne API token (embedded in the gateway URL configured in your North Agent Studio, governed by your Cohere identity provider), 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:
  • Cohere North's first-party connectors (Gmail, Slack, Salesforce, Outlook, SharePoint, Linear, Atlassian) 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 Cohere North.

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