MCP servers
MCP servers give your agents tools — the ability to read email, query a CRM, search the web, and more. Sema4.ai makes MCP servers available to builders from three sources:
- Vendor remote MCPs — a curated set of third-party, vendor-hosted remote MCP servers (Linear, GitHub, Notion, Stripe, and more) that are preconfigured and available out of the box. Nothing to deploy; users just authenticate when they add one to an agent.
- The Sema4.ai MCP Gallery — Sema4.ai-provided MCP servers (Google Workspace, Microsoft 365, web search, and others). The gallery is deployed automatically with the application, so these servers are available with no setup on your part.
- Custom MCPs — your own MCP servers. You provide the orchestration to host and run them, then connect them to the platform. See Set up MCP orchestration.
The application combines these sources into one gallery that builders pick from.
This is the first-time (self-hosted) setup. For the day-to-day reference — the Catalog and Connected views and connection status — see MCP servers in Administration.
Vendor remote MCPs
These are hosted by the vendor and ship preconfigured. Builders add them to an agent and authenticate (OAuth or an API key) at that point — there's nothing for you to deploy or maintain. The current set includes:
Linear · GitHub · Atlassian · Notion · HubSpot · Asana · monday.com · Box · Egnyte · Slack · Stripe · PayPal · Square · Ramp · Intercom · Supabase · Neon · Airtable · Wix · Ahrefs · Morningstar · ThoughtSpot
Because these run on the vendor's infrastructure, your network must allow outbound HTTPS to the vendor endpoints for any MCP your teams use. See Add networking rules.
Sema4.ai MCP Gallery
The Sema4.ai MCP Gallery bundles Sema4.ai-provided servers such as Google Workspace (Gmail, Docs, Drive, Sheets, Calendar), Microsoft 365 (Outlook Mail, Calendar, OneDrive, SharePoint, Teams, Excel), and web search. It's deployed and kept up to date automatically with the application — there's nothing to install or configure to make these servers available.
The Google and Microsoft gallery servers act on behalf of a signed-in user, so they need an OAuth client set up before your users can connect them. See Set up OAuth for MCPs.
Custom MCPs
To make your own MCP servers available, host them on your own infrastructure and connect them to the platform. See Set up MCP orchestration.