Introducing Mastra Connect. Your agents can now use Linear, Notion, Slack, and 20 other services with a single key. Oct 7, 2026 You can now connect providers like Linear, Notion, or Slack to your Mastra project with Mastra Connect. Deploy agents that connect to your services from the CLI with a single auth flow. Every connection gives your agents and workflows ready-made tools, such as linear_list_issues, notion_create_page, and slack_post_message. You can manage credentials with mastra connect add, or from the dashboard, and the running app picks up the new tools within seconds. Mastra continues to support direct integrations via MCP, as well as integrations through integration platforms like Composio, Nango, Arcade, and so on. But Mastra wanted to build the simplest possible way to get started, giving an agent all the tools it needs to search real knowledge and take real action. Today, Connect launches with 23 providers and almost 900 tools, plus 7 hosted MCP providers. More providers are coming, including Figma, GitLab, and Google Analytics. If Mastra connect to your provider but don't have the tool you need, you can use credential to get the stored credential and call the provider's SDK directly. With a Mastra platform project set up, install Connect and the latest Mastra CLI: Requires @mastra/[email protected] and @mastra/[email protected] or later, added in PR #26084. Connect providers to your project. OAuth providers open a consent screen in the browser; API key providers prompt for the key in the terminal: You can also add connections from the Connect page in the Mastra platform dashboard. The same page lists your connections and every request your agents make through them: Your app reads connections with a platform access token and your project ID. Add both to .env: When you deploy to Mastra platform, platform access token and your project ID are set for you. Pass tools to your agent. By default, the agent gets tools for every provider connected to the project; you can limit which providers and tools it uses. This example limits the agent to Notion, Linear, GitHub, and Slack, and removes delete, archive, and merge tools: Tool entries accept * globs, and new connections show up in the running app without a redeploy. Connections can also put your agents in Slack, Discord, or Telegram. Pass channels to the Mastra constructor and the platform supplies each channel's bot credential: Discord and Telegram still need a bot created in the vendor's console before you connect it. See Channels for setup steps per platform. When Connect doesn't have a tool, credential returns the stored credential so you can call the provider's SDK directly: Requests made with a raw credential skip the platform proxy, so they aren't recorded on the platform. * Clerk * Discord (tools + channels) * Fireflies.ai * GitHub * Gmail * Google Calendar * Google Docs * Google Drive * Google Sheets * HubSpot * incident.io * Jira * Linear * Notion * OpenAI * PostHog * Resend * Slack (tools + channels) * Snowflake * Supabase * Telegram (channels only) * WorkOS Patrycja Jenkner-Sar is a product marketer and content engineer at Mastra. Previously, she was a product marketer at neptune.ai, an experiment tracker for machine learning teams, and is focused on translating complex functionality into clear value for developers and technical audiences.

Arcjet launches agent runtime security for production AI agents. New product helps teams discover agent activity, apply controls before and after consequential actions, and preserve evidence for security reviews and compliance SAN FRANCISCO, Sept. 17, 2026 /PRNewswire/ - Arcjet, the security platform that ships in your AI code, today launched agent runtime security, a new product that helps engineering teams secure the AI agents they are building while giving security teams the governance and compliance evidence they need. Arcjet brings observability, enforcement, and audit capabilities across agent workflows so teams can discover which agents are running, control what they can do, and understand what happened and why. AI agents are moving beyond chat interfaces and into production workflows, where they can read and write to databases, respond to support tickets, refund payments, call tools and APIs, and take other actions on behalf of users. Those workflows can start from a chat interface, an email, a text message, a code commit, or another event, and can continue autonomously across multiple systems. As agents take on longer-running workflows, security teams need to answer three questions across the full sequence of activity, which agents are running, whether a particular action should be allowed, and what happened and why. Arcjet's agent runtime security addresses those questions through observe, enforce, and audit capabilities. Teams can discover agent activity and connect actions across sessions, apply deterministic security policies before and after calls to LLMs, tools, databases, and APIs, and preserve the execution context needed for security reviews and compliance. "Agents are now taking real actions inside production systems, which means security teams need to know which agents are operating and what they have done, and apply controls at machine speed," said David Mytton, CEO at Arcjet. "A risky outcome can develop across a series of steps that look perfectly reasonable on their own. Arcjet connects those steps and gives teams policy controls to detect them." Arcjet's agent runtime security centers on three parts of securing agents in production, observe, enforce, and audit. Observe: Discover all your agents Arcjet supports ingesting agent activity without application code changes or deploying another agent. Platform and security teams can use existing OpenTelemetry observability tooling to send activity directly to Arcjet for real-time visualization and analysis. For teams using Claude, Arcjet can also pull activity from the Claude Compliance API. Arcjet connects activity across sessions so teams can see an agent's sequence of actions as one workflow rather than a collection of unrelated events. Activity can include prompts, tool call parameters, session metadata, identity, security decisions, and other application context, giving teams a view of what each agent is doing across a run. Agent identity and inventory are part of that visibility. Arcjet gives teams an inventory of the agents and applications operating inside their environment, with activity and individual runs associated with each agent so teams can inspect actions and security decisions step by step. Enforce: Apply controls before and after every action Once teams can see their agents and activity across sessions, Arcjet lets security teams define controls for prompt injection detection, PII and sensitive information leak prevention and redaction, automation and bot detection, rate limits, and quota controls. Arcjet guards apply deterministic policies to tools, APIs, database calls, and other inputs and outputs. Powered by Rego and Open Policy Agent, teams can create versioned, immutable policies through Arcjet's web UI, API, CLI, or MCP without redeploying application code. Policies can define the actions an agent is allowed to take, such as restricting recipients or attachments in an email tool, setting acceptable bounds for refund values, or limiting web fetch tools to trusted API URLs. Arcjet returns a decision to the application before the action executes, allowing the application to stop the operation, request human approval, or return an explanation to the agent. Applied before and after calls to LLMs, tools, databases, and APIs, these controls can mitigate risk before consequential actions and verify results before the workflow continues. For enforcement, Arcjet has native integrations with major agent frameworks, including Claude Agents SDK, Claude Managed Agents, OpenAI Agents SDK, LangChain, LangFuse, Strands, Mastra, and Microsoft's Agent Framework. This in-code context allows Arcjet to track recorded actions, their inputs, and policy decisions across the workflow. Audit: Evidence and proof of compliance Arcjet collects the context of each execution so teams can reconstruct what happened, understand why a policy decision was made, and provide evidence for security reviews and compliance audits. Correlated traces preserve actions, inputs, security decisions, and policy evaluations across the work SOURCE Arcjet