Zapier today announced that its connector is now available in Meta's Muse agent. Once authorized, users can connect Muse to more than 9,000 apps and 40,000 actions through Zapier MCP.
With Zapier MCP, Muse can take action across the tools your team already uses, but only the specific apps and actions you approve. That gives everyone from individuals to enterprises a secure way to run Muse as an always-on agent. For example, give Muse read-only access to your CRM and permission to post in Slack, then ask it to tell the team which customers need a follow-up.
"AI becomes dramatically more useful when it can take action across the tools people rely on every day," said Dan Slagen, Chief AI Transformation Officer and CMO at Zapier. "Having recently launched Muse Spark 1.3 into AI by Zapier, and now being a named connector inside Muse, we're excited by the momentum with Meta for Zapier customers."
Zapier MCP is a hosted Model Context Protocol endpoint that connects AI clients to Zapier's app and action ecosystem. Through a single connection, agents can discover and run configured tools while Zapier manages app authentication, credentials, and the underlying integrations. This gives teams a way to build agents that work across multiple services without building and maintaining a separate API integration for each one.
For users with access to Next Gen Zaps, that connection can also support a longer-running form of work. Instead of asking an agent to repeat the same set of actions, a user can describe an automation in plain language and have an MCP-enabled agent build and deploy it to Zapier. Next Gen Zaps is currently available through a separate early access program, so its availability will depend on each user's Zapier account.
Each user connects through a Zapier account. Access to apps and actions is governed by the user's connections and permissions, with workspace controls and activity history available through Zapier MCP. The service operates under Zapier's SOC 2 Type II certification. Connected apps continue to apply their own permissions and API limits.
"AI has to work with the systems and controls companies already use," said Slagen. "Zapier MCP lets teams start with an action an agent can take today, then build repeatable workflows around the work they want to run tomorrow."
Zapier MCP uses Streamable HTTP. Teams can configure separate servers and connection tokens for development, testing, and production. Sharing access to a server requires a Zapier Team or Enterprise plan; users on any plan can share a copy of a tool configuration through a tool bundle.
The integration is staged for deployment. Availability to Meta users will depend on Meta's rollout and user authorization.
