Connect Zapier to Andromity with the Zapier MCP server

Zapier runs an official MCP server that lets an MCP client call Zapier actions through the app connections already on your Zapier account. With it, Andromity can trigger actions such as sending a message or creating a task after it finishes a change.

Sign-in is OAuth in your browser. Zapier creates a server for the client during sign-in, and Zapier holds the credentials for the connected apps, so the agent never handles their API keys.

What the agent can do with Zapier

• Discover available apps and actions (discover_zapier_actions).
• Enable and disable actions for the agent (enable_zapier_action, disable_zapier_action).
• See which actions are currently enabled (inspect_zapier_actions).
• Run enabled actions, including write actions, in the apps connected to your Zapier account.
• Open your MCP configuration page (get_configuration_url) and change an app's default connection (manage_zapier_connections).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Zapier MCP server”.

• Once the tests pass on this branch, use Zapier to post a summary of the changes to our team's Slack channel.
• Create a task in our project tracker through Zapier for each failing test in the last run.
• Check which Zapier actions are enabled, and enable one that appends a row to our release log spreadsheet. Then add a row for this release.

Connect Zapier

1. Make sure the apps you want to use are connected in your Zapier account. Your organization may require an admin to approve the Zapier connector first.
2. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Zapier and select Connect.
3. Approve the connection in your browser. Zapier creates the server for the client during sign-in.
4. Andromity saves Zapier to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• By default Zapier uses agentic mode: the agent finds and enables its own tools during the conversation. You can ask it to add or remove actions.
• Managed mode lets you choose the tools in advance at mcp.zapier.com. Each action becomes its own tool, the agent cannot enable new ones, and you can lock specific field values.
• Calls run through your own Zapier app connections. Zapier applies workspace-level access controls, user permissions and audit history, and tool calls appear in the History tab at mcp.zapier.com.
• Andromity's permission modes apply to every Zapier tool call.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Each successful tool call uses two tasks from your Zapier plan. Failed calls do not count.
• The server needs Streamable HTTP. SSE-only clients cannot connect.
• Sharing a server requires a Zapier Team or Enterprise plan.

Questions

Does Zapier have an official MCP server?

Yes. Zapier runs an MCP server that exposes actions from the apps connected to your Zapier account.

How do I choose which Zapier actions the agent can use?

In the default agentic mode, ask the agent to enable or disable actions. In managed mode, select the tools yourself at mcp.zapier.com and the agent cannot add more.

Does using Zapier MCP cost tasks?

Yes. Zapier says each successful tool call uses two tasks from your plan.

Sources

This guide is based on Zapier’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Zapier MCP overview
• How connections work
• How tools work

Zapier is a trademark of its owner. Andromity is not affiliated with or endorsed by Zapier.