Who is connectors for?

Developers building or using AI agents who know basic Node and TypeScript and have heard of MCP; expect prototype-level stability.

What can you build with connectors?

Give a coding agent a Notion search tool by installing the Notion connector as a skill. Run a connector from cron or GitHub Actions by piping JSON into the npx CLI. Expose app actions to any MCP client by starting a connector's local MCP server. Call an app's API from your own Node code using the connector's typed run functions. Read a connector's scripts and references to learn how to write agent-friendly tools.

zapier /

connectors

Agent-callable tools for Zapier's 9k+ apps, usable as skills, MCP tools, or a CLI

180 stars
6 stars since 3 Oct
TypeScript
Updated 2 months ago
Some experience
Agent skills & plugins

Open on GitHub (opens in a new tab)

AI agents need a reliable way to call the apps people already use. Zapier Connectors packages each app as one folder of scripts, plus a SKILL.md and reference notes that an agent can read. The catalog targets the 9k+ apps Zapier integrates with.

Each connector fits two standards at once: an agentskills.io skill and an MCP Tool-shaped TypeScript module. You can install it as a skill in clients like Cursor, Claude Code, Codex or Copilot. You can also import it in Node code, run it as a CLI that reads JSON on stdin, or start it as a local MCP server.

Zapier is the easy path for auth, but not required. Each connector can instead read your own token from an environment variable. The README marks the project as a prototype: pre-1.0, breaking changes in minor versions, and nothing is a stable contract yet. The license is Elastic License 2.0.

What it does

Skill and MCP tool in one
Each connector follows the agentskills.io skill layout and exposes MCP-style tools, so one folder serves both kinds of client.
Four ways to use it
Install as a skill, import as a TypeScript dependency, call from a CLI with JSON input, or run a local MCP server over stdio.
Flexible authentication
Pass a connection string such as env:NOTION_TOKEN to use your own credentials, or zapier:<connection-id> to use Zapier-managed auth. The string names the secret and does not hold it.
Self-describing scripts
Running a script with --help shows its input schema and the available auth resolvers.
Standalone connector folders
Each apps/<slug> folder installs on its own, and a sparse git clone fetches only the connectors you want.

What you could build

Give a coding agent a Notion search tool by installing the Notion connector as a skill.
Run a connector from cron or GitHub Actions by piping JSON into the npx CLI.
Expose app actions to any MCP client by starting a connector's local MCP server.
Call an app's API from your own Node code using the connector's typed run functions.
Read a connector's scripts and references to learn how to write agent-friendly tools.

Get started

Pick a connector such as Notion and either install it as a skill in your AI client or run it with npx. Set the app's token in an environment variable and pass it with --connection env:NAME, or use a Zapier connection ID.

echo '{"query":"foo"}' | npx @zapier/notion-connector run search --connection env:NOTION_TOKEN

npx @zapier/notion-connector mcp

Commands are copied from the project's README. Read it on GitHub for the full setup.