An MCP server gives an Agent access to tools in an external system — for example creating a Jira issue, reading Sentry errors, or searching Notion pages. MCP stands for Model Context Protocol, an open standard for connecting AI models to tools and data.
This page lists the MCP servers SAALT supports. Every server here is the provider's official, remotely hosted server: there is nothing to install, SAALT connects to it over HTTP. Most of them are in the SAALT catalog, so picking one fills in the server URL and sign-in settings for you. Any other MCP server can still be added manually by URL.
Where to find this: open the Agent → kebab menu (⋯, top-right) → Agent Settings → Tools → MCPs section → Add MCP
How to connect a server
- Open the dialog. Click Add MCP. The dialog lists every server in the catalog. Use Search servers to filter. If the server is not listed, choose Add manually (see Add your own server).
- Check the settings. The Name and Server URL are prefilled. You can rename the connection, e.g. Jira Support — the name is how it appears in the Tools overview. If the server needs extra values (a Client ID, an API key), fill them in; the entries below say what each server needs.
- Connect. For OAuth servers, click Connect with … (followed by the server name). A sign-in window from the provider opens; sign in and approve access. For other servers, click Test connection.
- Choose the tools. After a successful connection, SAALT loads the server's tools. Every tool can be switched on or off individually, or all at once with Enable all / Disable all. Tools that change data in the external system are marked Writes — switch these off if the Agent should only read.
- Save. Click Save connection. The Agent can now use the enabled tools in chat.
When a user chats with an Agent that uses an OAuth server they have not signed in to yet, the chat shows a sign-in prompt with a Connect button. If a sign-in expires, the chat asks the user to Reconnect.
Sign-in types
Each server uses one of four sign-in types:
| Sign-in type | What you do | Who the Agent acts as |
|---|---|---|
| None | Nothing — the server is public. | Nobody; only public data is available. |
| OAuth | Click Connect and sign in with your account at the provider. | Each user's own account. |
| OAuth with own client | Once per server: create an OAuth app at the provider, register SAALT's Redirect URI there, and enter its Client ID and Client secret. After that, users sign in like with OAuth. | Each user's own account. |
| API key | Create a key or token at the provider and paste it into the API key field. SAALT sends it as Authorization: Bearer <key>. | The account the key belongs to — shared by everyone using the Agent. |
From SAALT 1.6.0, catalog servers can also offer sign-in managed by SAALT (Managed app by SAALT), so nobody has to create an OAuth app or enter keys:
- Sign in with … — each user still signs in with their own account at the provider, but through an OAuth app that SAALT created and maintains. The Agent acts as each user's own account.
- Shared access — "Access is provided by your administrator. One shared account for all users, nothing to enter." The Agent acts as that one shared account.
A managed option only appears when it is enabled for your instance. For administrators: the credentials come from environment variables named after the server, see Environment variables.
Providers use different names for the same thing: personal access token (PAT), access token, bearer token and API key all mean API key here. OAuth with dynamic client registration (DCR) means plain OAuth.
For OAuth with own client, the provider needs SAALT's Redirect URI. The dialog shows it under Authentication. It has the form https://<your-saalt-domain>/api/mcp/oauth/callback and must be registered exactly as shown.
With API key, every user of the Agent acts with the permissions of that one key. Create the key with the smallest set of permissions the Agent needs, ideally for a service account.
Add your own server
Servers that are not in the directory can be added by URL. In the dialog, choose Add manually, then fill in:
- Name — a label for this connection.
- Server URL — the MCP endpoint, e.g.
https://example.com/mcp. - Authentication — None, API key or OAuth (see Sign-in types). For OAuth, Client ID, Client Secret and Scopes are optional — leave them empty if the server supports dynamic client registration.
- Custom fields (optional) — extra values sent as HTTP headers on every request.
Click Test connection to check the server and load its tools, then Save connection.
All MCP servers
Click a server to see its URL, sign-in type, documentation and setup notes.
AmplitudeOAuth
AmplitudeAnalyze user behavior, event metrics, funnels and product analytics in Amplitude.
- Server URL:
- US-hosted organizations:
https://mcp.amplitude.com/mcp - EU-hosted organizations:
https://mcp.eu.amplitude.com/mcp
- US-hosted organizations:
- Sign-in: OAuth
- Docs: Amplitude MCP
Use the server for the region your Amplitude organization is hosted in. An Amplitude admin can control MCP access in the organization's settings.
ApifyOAuth
Find and run Apify Actors (web scrapers and automations) and retrieve the extracted data.
- Server URL:
https://mcp.apify.com - Sign-in: OAuth
- Docs: Apify MCP server
Atlassian (Jira & Confluence)OAuth
Read and write Jira issues, Confluence pages and Compass components across your Atlassian sites.
- Server URL:
https://mcp.atlassian.com/v2/mcp - Sign-in: OAuth
- Docs: Atlassian Rovo MCP server
Tool calls use Rovo credits from your Atlassian organization.
AttioOAuth
AttioSearch contacts and companies, manage deals and read CRM data in your Attio workspace.
- Server URL:
https://mcp.attio.com/mcp - Sign-in: OAuth
- Docs: Attio MCP
ClickUpOAuth
Search, create and manage tasks, lists, spaces and docs in your ClickUp workspace.
- Server URL:
https://mcp.clickup.com/mcp - Sign-in: OAuth
- Docs: ClickUp MCP server
ClickUp limits the number of tool calls per day depending on your ClickUp plan.
CCloudflare WorkersOAuth
Manage Workers, KV, R2, DNS and other resources through the Cloudflare API.
- Server URL:
https://mcp.cloudflare.com/mcp - Sign-in: OAuth
- Docs: Cloudflare's MCP servers
DeepWikiNone
Ask questions about public GitHub repositories and read their generated documentation.
- Server URL:
https://mcp.deepwiki.com/mcp - Sign-in: None
- Docs: DeepWiki MCP
Works with public repositories only.
ddraw.ioNone
Create and edit draw.io diagrams.
- Server URL:
https://mcp.draw.io/mcp - Sign-in: None
- Docs: draw.io MCP server
Diagram content is sent to draw.io's server.
Fireflies.aiOAuth
Search meeting transcripts and summaries and retrieve action items.
- Server URL:
https://api.fireflies.ai/mcp - Sign-in: OAuth
- Docs: Fireflies MCP configuration
IntercomOAuth
IntercomSearch conversations, contacts and help-center articles in your Intercom workspace.
- Server URL:
- US-hosted workspaces:
https://mcp.intercom.com/mcp - EU-hosted workspaces:
https://mcp.eu.intercom.com/mcp
- US-hosted workspaces:
- Sign-in: OAuth
- Docs: Intercom MCP server
Use the server for the region your Intercom workspace is hosted in — with the wrong region, the connection fails after sign-in.
LinearOAuth
LinearCreate, search and update issues, projects and cycles in your Linear workspace.
- Server URL:
https://mcp.linear.app/mcp - Sign-in: OAuth
- Docs: Linear MCP server
NeonOAuth
NeonCreate and manage serverless Postgres projects and branches and run SQL queries.
- Server URL:
https://mcp.neon.tech/mcp - Sign-in: OAuth
- Docs: Neon MCP server
For read-only access, add ?readonly=true to the URL. Neon recommends the server for development and testing, not for production databases.
NNotionOAuth
Search, read and update pages and databases in your Notion workspace.
- Server URL:
https://mcp.notion.com/mcp - Sign-in: OAuth
- Docs: Get started with Notion MCP
PostHogOAuth
PostHogQuery product analytics, manage feature flags and inspect insights and dashboards.
- Server URL:
https://mcp.posthog.com/mcp - Sign-in: OAuth
- Docs: PostHog MCP
US and EU accounts use the same URL — PostHog routes to your region automatically. For read-only access, add ?readonly=true to the URL.
PPostmanOAuth (US) or API key (EU)
Work with Postman collections, environments, mocks, API specifications and workspaces — for example run collection tests, generate collections or API docs from code, sync environments, or generate client code for an API.
- Server URL:
- US-hosted teams:
https://mcp.postman.com/mcp - EU-hosted teams:
https://mcp.eu.postman.com/mcp
- US-hosted teams:
- Sign-in: OAuth (US) or API key (US and EU)
- Docs: Postman remote MCP server, Postman MCP server overview
Tool sets
Postman offers several tool sets, each at its own URL. Replace the last part of the URL to choose one — for EU-hosted teams, use mcp.eu.postman.com instead of mcp.postman.com:
| Tool set | URL (US) | What it covers |
|---|---|---|
| Full | https://mcp.postman.com/mcp | All 100+ tools. This is the URL the SAALT catalog uses. |
| Minimal | https://mcp.postman.com/minimal | Collections, specifications and test runs. Postman's default. |
| Code | https://mcp.postman.com/code | Finding APIs and generating client code. |
| Learn | https://mcp.postman.com/learn | Searching the Postman Learning Center docs. |
| Context Graph | https://mcp.postman.com/context-graph | Questions in plain language about your team's APIs. Needs Context Graph enabled for your Postman team. |
A smaller tool set keeps the Agent focused and makes it pick the right tool more reliably. Use Full only if the Agent needs the whole Postman platform.
Sign-in by region
- US-hosted teams can use OAuth — click Connect and sign in with your Postman account.
- EU-hosted teams must use an API key — the EU server does not support OAuth. Pick Postman (EU) from the catalog and paste a Postman API key.
To create an API key, open Postman API keys → Generate API Key. The Agent then acts with that Postman account's permissions.
Limits
Every tool call counts toward your Postman plan's monthly limit of Postman API calls.
PrismaOAuth
Manage Prisma Postgres databases, inspect schemas and search the Prisma docs.
- Server URL:
https://mcp.prisma.io/mcp - Sign-in: OAuth
- Docs: Prisma MCP server
SanityOAuth
SanityQuery content with GROQ, manage documents and inspect schemas in your Sanity project.
- Server URL:
https://mcp.sanity.io - Sign-in: OAuth
- Docs: Sanity MCP server
SentryOAuth
SentrySearch and triage errors, issues and performance data in your Sentry organization.
- Server URL:
https://mcp.sentry.dev/mcp - Sign-in: OAuth
- Docs: Sentry MCP
To limit the Agent to one organization or project, add it to the URL: https://mcp.sentry.dev/mcp/<organization>/<project>.
StripeOAuth
Look up customers, payments and subscriptions and create invoices in your Stripe account.
- Server URL:
https://mcp.stripe.com/ - Sign-in: OAuth
- Docs: Stripe MCP
SSuperhuman Docs (Coda)OAuth
Search, read and write docs, tables and rows in Superhuman Docs (formerly Coda).
- Server URL:
https://docs.superhuman.com/apis/mcp - Sign-in: OAuth
- Docs: Getting started with Coda MCP
Write access needs a paid plan; the free plan is read-only with a small request limit.
SupabaseOAuth
Query Postgres tables, manage migrations, edge functions and storage in your Supabase projects.
- Server URL:
https://mcp.supabase.com/mcp - Sign-in: OAuth
- Docs: Supabase MCP
You control the Agent's permissions through URL parameters, combined with &:
read_only=true— runs all queries as a read-only database user.project_ref=<ref>— limits the Agent to one project.features=<list>— enables only the listed tool groups, e.g.features=database,docs.
Example: https://mcp.supabase.com/mcp?project_ref=abc123&read_only=true. Supabase recommends connecting development projects, not production data.
Related pages
- Apps — the other way to give an Agent tools, and where the MCPs section lives.
- Agents — configuring an Agent.