Connect
Optimize
Secure
MCP gateway for Perplexity Comet
The MCP Gateway
for Perplexity Comet
Let your Comet assistant act across 270+ enterprise SaaS — without leaving the browser. No auth hassle. Token-efficient by design. Security and governance built-in.
What is an MCP gateway?
MCP gateways are real-time integration infrastructure connecting AI
agents to the SaaS apps they need to use. They expose one MCP server
instead of many to the AI agent. They are built on the open Model Context Protocol (opens in new tab), and
are also called MCP aggregators.
MCP gateways use whatever communication protocol each MCP server requires
(stdio, SSE, streamable HTTP), maximize the action coverage agents can
call, and handle authentication, agent action scoping, tool-call
optimization, agent security, and tool-call observability.
StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — brings this infrastructure to 270+ pre-built SaaS integrations exposing 18,000+ actions, reachable from your Comet assistant through one URL.
Act across all your apps
from inside Comet
One MCP gateway, every enterprise SaaS your Comet assistant
could ever need to act on.
Coverage
270+ connectors.
18,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 Comet assistant'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 Perplexity Comet
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 Perplexity.
In your Perplexity account (Pro / Max / Enterprise), open Settings → Connectors → + Custom connector → Remote, paste the StackOne gateway URL, pick auth, and click Add. Available immediately to your Comet assistant.
Settings → Connectors
Custom connector — Remote
Name
StackOne Gateway
MCP Server URL
https://api.stackone.com/mcp/{...}
Authentication
OAuth
Add
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.
Search documents (enabled)
List records (enabled)
Read related (enabled)
Update record (disabled)
Delete record (disabled)
4
Ask Comet in plain English.
StackOne maps the assistant's tool call to the right action in the right system. Done.
"Summarise this week's open Intercom tickets and prep a follow-up brief in the assistant."
intercom_list_conversations
Completed
linear_list_issues
Completed
filter: linked to support tickets
team: Product
result: 8 issues open
24 open Intercom tickets, 8 linked to active Linear issues. Brief ready in the Support Triage assistant thread.
Get Comet
to do more across your stack
Cross-app workflows your Comet assistant now runs in seconds instead of click-throughs.
Customer Support & Success
> Summarise this week's Zendesk tickets and prep the response plan in Comet's assistant.
HR, Recruiting & People
> Pull Greenhouse candidates in offer stage and brief Comet on each profile.
Finance, Billing & Ops
> Reconcile Stripe MRR against the NetSuite GL for the monthly close.
Data, BI & Analytics
> Pull a Databricks query into a Tableau-ready table from Comet's assistant.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 270+ MCP servers. Same agent context. Pick yours.
Frequently Asked Questions
Custom Remote MCP connectors went GA on Perplexity Pro, Max, and Enterprise on March 13, 2026, and Comet consumes them through Perplexity's account-level connector layer. Setup: sign in at perplexity.ai (Pro/Max/Enterprise), open Settings → Connectors → + Custom connector → Remote, paste the StackOne gateway URL, pick OAuth / API key / None for auth, accept the disclaimer, and click Add. The connector is then callable from inside Comet's assistant pane and Perplexity Computer. 270+ pre-built SaaS connectors are reachable through that single MCP server. Full walkthrough in the Perplexity changelog. Available on Pro, Max, and Enterprise plans.
An MCP gateway is real-time integration infrastructure connecting AI agents to the SaaS apps they need to use. It exposes one MCP server instead of many to the AI agent, and handles authentication, agent action scoping, tool-call optimization, agent security, and tool-call observability. Also called an MCP aggregator.
Comet's assistant can access enterprise SaaS like Zendesk, Intercom, Freshdesk, Workday, Greenhouse, Lever, NetSuite, Stripe, Xero, Databricks, Tableau, and Looker through the StackOne MCP gateway — 270+ pre-built connectors in total. StackOne extends Comet beyond Perplexity's first-party app connectors (Gmail, Slack, Notion, GitHub, Linear, Salesforce, HubSpot, Snowflake). New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
Perplexity ships native app connectors covering Gmail, Slack, Notion, GitHub, Linear, Salesforce, HubSpot, Snowflake, and a handful of others — but the long tail of operational SaaS is on you. StackOne adds the other 270+ — every app reachable through one Custom connector 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 Perplexity Settings → Connectors, governed by your Perplexity account), 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:
- Perplexity's first-party connectors (Gmail, Slack, Notion, GitHub, Linear, Salesforce, HubSpot, Snowflake) 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 Comet.
One MCP gateway, 270+ pre-built SaaS connectors. Set up in 5 minutes.