Mastra Connect lets agents tap Linear, Notion and Slack with one auth flow

What Mastra Connect does

Each connection gives agents and workflows ready-made tools, according to Mastra. Examples named in the announcement are linear_list_issues, notion_create_page and slack_post_message. Credentials can be managed with the mastra connect add command or from the dashboard, and the running app picks up the new tools within seconds.

Connect launches with 23 providers and almost 900 tools, plus 7 hosted MCP providers, Mastra says. More providers are coming, including Figma, GitLab and Google Analytics. The current list includes Clerk, Discord, Fireflies.ai, GitHub, Gmail, Google Calendar, Google Docs, Google Drive, Google Sheets, HubSpot, incident.io, Jira, Linear, Notion, OpenAI, PostHog, Resend, Slack, Snowflake, Supabase, Telegram and WorkOS.

Mastra says it continues to support direct integrations via MCP, as well as integration platforms such as Composio, Nango and Arcade. Connect is meant to be the simplest possible way to get started, giving an agent the tools it needs to search real knowledge and take real action.

Setting it up

With a Mastra platform project in place, developers install the package and the latest CLI using npm install @mastra/connect and npm install -g mastra@latest. The setup requires @mastra/[email protected] and @mastra/[email protected] or later.

Providers are then added per project, for example with mastra connect add linear --project your-project-name. OAuth providers open a consent screen in the browser, while API key providers prompt for the key in the terminal. Connections can also be added from the Connect page in the dashboard, which lists them along with every request agents make through them.

The app reads connections with a platform access token and a project ID, set in the .env file as MASTRA_PLATFORM_ACCESS_TOKEN and MASTRA_PROJECT_ID. When deploying to Mastra platform, both are set automatically.

In code, developers pass tools() to an agent. By default the agent receives tools for every provider connected to the project, but this can be narrowed. Mastra's example limits an agent to Notion, Linear, GitHub and Slack and removes delete, archive and merge tools. Tool entries accept * globs, and new connections appear in the running app without a redeploy.

Channels and raw credentials

Connections can also place agents in Slack, Discord or Telegram. Developers pass channels() to the Mastra constructor, and the platform supplies each channel's bot credential. Discord and Telegram still require a bot to be created in the vendor's console before connecting.

If Connect lacks a tool for a connected provider, credential() returns the stored credential so the provider's SDK can be called directly. Mastra notes that requests made with a raw credential skip the platform proxy, so they are not recorded on the platform.

What it means for developers

For teams building agents on Mastra, Connect reduces the work of wiring up third-party services: one CLI flow handles authentication, tools appear automatically, and the dashboard shows the requests agents make. Filtering options let developers keep destructive actions away from agents. Because the product is in public beta, details may change, though Mastra says it is free on its platform during that period.