Providers
A provider is a service you can connect to your project, identified by a provider ID such as linear or google-mail. Providers can supply tools, channels, or both.
Provider directoryDirect link to Provider directory
This directory covers the generated toolsets and channel setup documented here, rather than every provider in the platform catalog. Run mastra connect list to see providers available to your project and their connection status.
| Provider ID | Provider | Gives you |
|---|---|---|
clerk |  Clerk | Tools |
discord |  Discord | Tools, Channels |
fireflies |  Fireflies.ai | Tools |
github |  GitHub | Tools |
google-calendar |  Google Calendar | Tools |
google-docs |  Google Docs | Tools |
google-drive |  Google Drive | Tools |
google-mail |  Gmail | Tools |
google-sheet |  Google Sheets | Tools |
hubspot |  HubSpot | Tools |
incident-io |  incident.io | Tools |
jira |  Jira | Tools |
linear |  Linear | Tools |
microsoft-teams |  Microsoft Teams | Tools, Channels |
notion |  Notion | Tools |
openai |  OpenAI | Tools |
posthog |  PostHog | Tools |
resend |  Resend | Tools |
slack |  Slack | Tools |
slack-channels | Slack channels | Channels |
snowflake |  Snowflake | Tools |
supabase |  Supabase | Tools |
telegram |  Telegram | Channels |
workos |  WorkOS | Tools |
Generated toolsets are included in @mastra/connect. Upgrading the package gives you toolsets added in newer releases, but provider availability depends on the platform catalog. The provider toolsets reference lists the generated tools.
MCP providersDirect link to MCP providers
These providers serve their tools from a hosted Model Context Protocol (MCP) server. The tools come from the provider at runtime, so check each provider's MCP documentation for what it offers. See the MCP tools reference for tool naming and Require approval for sensitive tools for approval setup.
| Provider ID | Provider | Provider MCP docs |
|---|---|---|
attio-mcp |  Attio | Attio MCP |
canva-mcp |  Canva | Canva MCP |
clay-mcp |  Clay | MCP in Clay |
neon-mcp |  Neon | Neon MCP server |
render-mcp |  Render | Render MCP server |
robinhood-mcp |  Robinhood | Agentic Trading |
sanity-mcp |  Sanity | Sanity MCP server |
Troubleshoot a connectionDirect link to Troubleshoot a connection
Most provider call failures come from the connection's credential or configuration. A proxy_error carries the provider's response in its status and detail properties.
- Status
401: Check whether the credential has expired, been revoked, or been rotated. If it needs replacing, reauthorize the connection. - Status
403: Check the provider's response for missing scopes, resource-access restrictions, or account requirements. Grant only the access the agent needs. You can exclude unsupported operations withallowTools, but filtering tools doesn't change the credential's permissions. - No tools from a provider: Run
mastra connect listto check the project and connection status. Check provider selection and tool filters, and confirm that your installed@mastra/connectversion includes the toolset. Connection changes follow the resolver's caching behavior. Check app logs for[@mastra/connect] Skippingwarnings when a connection can't be resolved. - Resend won't connect: Use an API key with Full access permission. A Sending access key fails to connect because Mastra checks a new key by listing your domains, which sending access keys can't do.
See errors for every error code.