---
title: MCP providers
group: Reference
order: 5
summary: Which providers the Escanor MCP server ships, which run on your workspace's stored connection, and which need more configuration.
updated: 2026-10-07
---
Ask `escanor_list_providers` for the live list. This page groups the providers the MCP server ships with today and says which ones run with **your workspace's stored connection**, as explained in [Escanor MCP](/docs/mcp).

## Run on your workspace's stored connection

For these, connecting the integration in the dashboard is enough. The operation runs with the workspace credential. Verify the live connection and the returned operation result.

| Area | Providers |
|---|---|
| Source control | `github`, `gitlab` |
| Deploy and hosting | `vercel`, `netlify`, `digitalocean`, `terraform` |
| Data | `neon`, `supabase`, `redis_cloud` |
| Monitoring and incidents | `sentry`, `pagerduty` |
| Work and communication | `slack`, `linear`, `notion`, `asana`, `docusign`, `sendgrid` |
| Payments | `stripe` |
| AI | `openai`, `anthropic` |

If you have not connected one of these, `escanor_connection_status` lists it as not connected and a call answers `not_connected`.

## Catalog providers with additional configuration requirements

These providers appear in the catalog, but your workspace can use them only after you connect them with the credentials each one needs. Check `escanor_connection_status`, then try a safe read. A `not_connected` result means you still need to connect it; never paste a credential into a prompt instead.

| Area | Providers |
|---|---|
| Cloud | `aws`, `gcp`, `azure`, `oci`, `cloudflare`, `firebase` |
| Containers and orchestration | `kubernetes`, `docker`, `portainer`, `argocd` |
| Databases | `postgresql`, `mysql`, `mongodb`, `redis`, `elasticsearch`, `planetscale`, `qdrant` |
| Identity and secrets | `okta`, `vault` |
| Productivity | `google_workspace`, `msgraph`, `box` |
| Payments and finance | `adyen`, `razorpay`, `plaid`, `xero` |
| Messaging | `twilio` |

## Scale

Some providers are very large (the big clouds have thousands of operations). That is why the server exposes five tools and lets the agent search: `escanor_list_tools` takes a `query`, a `limit` (default 100, up to 500) and an `offset`, and returns the operations' input schemas. See the schemas in [Escanor MCP](/docs/mcp#discovery-and-invocation-schemas).

## Adding more

The integration catalog lists many more providers than the MCP reaches today. They appear in the dashboard and the assistant; the MCP list grows as providers are added. Tell us from [Support](/support) which one you need next.