Alternatives to Zapier MCP
Zapier MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Mintlify MCP, Apify MCP, Browserbase MCP. Each entry below states one difference between it and Zapier MCP, with the evidence and a source link. Zapier MCP is operated by Zapier.
The 6 alternatives
Cloudflare
Hosts remote MCP servers on Workers through the Agents SDK, ships its own OAuth provider library, and fronts many servers behind one endpoint with MCP server portals.
Difference on oauth with client registration: Cloudflare reads "yes, DCR and CIMD" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents.
Vercel
Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com.
Difference on oauth with client registration: Vercel reads "bring your own AS; CIMD on Vercel MCP" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients.
Composio
A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs.
Difference on oauth with client registration: Composio reads "Composio holds app OAuth" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented.
Composio profile, Composio vs Zapier MCP
Mintlify MCP
Generates a search MCP server for every Mintlify docs site at /mcp, with an authenticated variant and published discovery files.
Difference on oauth with client registration: Mintlify MCP reads "client credentials at /authed/mcp/oauth/token" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added.
Apify MCP
Turns Apify Store Actors into MCP tools at mcp.apify.com, with OAuth or a bearer token and a keyless mode for search and docs tools only.
Difference on oauth with client registration: Apify MCP reads "OAuth" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). Browser opens on first connection.
Apify MCP profile, Zapier MCP vs Apify MCP
Browserbase MCP
A hosted browser-automation MCP server built on Stagehand, reached at mcp.browserbase.com with an API key in the query string.
Difference on oauth with client registration: Browserbase MCP reads "no, API key in URL" (source, 4 November 2026); Zapier MCP reads "OAuth for clients" (source, 4 November 2026). Query parameter auth.