# Zapier MCP server [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/zapier/zapier-mcp  
**GitHub Stars:** 454  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/zapier-mcp-server

## Description
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.

## Tools
Capabilities this server exposes over MCP:

- **search_zapier** — Search across the Zapier knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Zapier, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
- **query_docs_filesystem_zapier** — Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Zapier documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.

This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.

**Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered.

**Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.

Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.

Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call.

Examples (replace the placeholder paths with real ones from `tree` or search):
- `tree / -L 2` — see the top-level directory layout
- `rg -il "rate limit" /` — find all files mentioning "rate limit"
- `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit
- `head -80 /some/page.mdx` — read the top 80 lines of a specific page
- `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call
- `cat /some/page.mdx` — read a full page when you need everything
- `cat /openapi/package.json | jq '.paths | keys'` — list OpenAPI endpoints

OpenAPI specs for this site are mounted at: `'/openapi/https://api.zapier.com/schema'`, `/openapi/white-label/trigger-inbox-openapi.yaml`, `/openapi/api-reference/specs/trigger-inbox.yaml`, `/openapi/white-label/actions-openapi.yaml`, `/openapi/api-reference/specs/actions.yaml`, `/openapi/api-reference/specs/agentic-management.yaml`, `/openapi/powered-by-zapier/api-reference/promotions-openapi.yaml`, `/openapi/api-reference/specs/connections.yaml`, `/openapi/package.json`, `/openapi/tsconfig.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.

Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.

When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.
- **submit_feedback** — Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "zapier-mcp-server": {
    "url": "https://docs.zapier.com/mcp/home"
  }
}
```

## Documentation

## What Zapier MCP server does

Zapier MCP server gives MCP-compatible AI clients access to Zapier’s app ecosystem, which covers more than 9,000 apps and 40,000 actions. Through the hosted service, an assistant can send messages, retrieve information, and trigger workflows using connected Zapier capabilities. The repository also distributes an optional client plugin that adds onboarding, a first-use demonstration, and role-oriented skills in clients that support it.

The server is also a reference tool for Zapier itself. It exposes documentation search, access to documentation pages and OpenAPI specifications, and a way to report problems with documentation content.

## How it works

Clients connect to the hosted MCP endpoint at `https://mcp.zapier.com/api/v1/connect` using HTTP. The assistant can start with `search_zapier` for broad or conceptual questions. Search results include contextual text, page titles, and links. To inspect a complete page, the assistant uses the returned path with the documentation filesystem tool and adds the `.mdx` extension.

`query_docs_filesystem_zapier` provides a read-only, in-memory filesystem rooted at `/`. It contains Zapier documentation pages and OpenAPI specifications only; commands do not execute on the user’s computer, the server host, or an external network. The tool supports shell-like inspection and text-processing commands such as `tree`, `ls`, `rg`, `cat`, `head`, `jq`, and `grep`.

Each filesystem call is stateless: the working directory resets to `/`, and shell state is not retained between calls. Paths should be discovered with `tree`, `ls`, or search rather than guessed.

## Setup and configuration

Connect an MCP client with the hosted URL and HTTP transport. VS Code can connect directly using the installation badge or by adding the endpoint manually. Cursor provides a server installation link, and Gemini CLI can install the repository extension with:

```text
gemini extensions install https://github.com/zapier/zapier-mcp
```

After installation in Gemini CLI, authenticate with `/mcp auth zapier`. Claude Code, Cursor, OpenAI Codex, GitHub Copilot CLI, Claude Cowork, Kiro, and Gemini CLI can also use the distributed plugin or extension paths described by the project. Some clients receive guided onboarding and role-specific skills through that layer; VS Code connects directly to the hosted server.

## Tools and capabilities

- `search_zapier` searches Zapier’s knowledge base for documentation, code examples, API references, guides, and implementation details.
- `query_docs_filesystem_zapier` reads and searches the virtual documentation filesystem with read-only commands.
- `submit_feedback` reports incorrect, outdated, confusing, incomplete, or broken documentation content.
- OpenAPI specifications in the mounted documentation filesystem support research into endpoints, schemas, parameters, and authentication.
- The hosted connection exposes Zapier-connected app actions for tasks such as sending messages, retrieving data, and triggering workflows.

## Limitations and notes

The documentation filesystem is not a general shell and cannot modify files, run processes, access a real machine, or make network requests. Documentation paths are site-specific, so broad search or filesystem discovery should precede page reads. The feedback tool is intended for problems with Zapier documentation, not product support requests or feedback about the MCP client itself. The plugin distribution is separate from the hosted MCP connection: clients can connect directly when they support the HTTP endpoint.

_Full upstream README: https://allmcps.com/mcp/zapier-mcp-server/readme_