--- title: "Apify MCP alternatives | Agent MCP Directory" description: "6 alternatives to Apify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026." canonical: https://agentmcpdirectory.com/hosts/apify-mcp/alternatives site: "Agent MCP Directory" last_updated: 2026-11-04 section: "Hosts and registries" --- # Apify MCP alternatives | Agent MCP Directory > 6 alternatives to Apify MCP for hosting MCP servers, each with one sourced difference. Scored on the same published rubric, read 4 November 2026. Source: https://agentmcpdirectory.com/hosts/apify-mcp/alternatives Site: Agent MCP Directory Last reviewed: 2026-11-04 # Alternatives to Apify MCP Apify MCP has 6 alternatives on this directory's rubric: Cloudflare, Vercel, Composio, Zapier MCP, Mintlify MCP, Browserbase MCP. Each entry below states one difference between it and Apify MCP, with the evidence and a source link. Apify MCP is operated by Apify. ## 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](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Workers OAuth Provider v1 supports DCR and Client ID Metadata Documents. [Cloudflare profile](https://agentmcpdirectory.com/hosts/cloudflare/) ### 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](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). mcp-handler verifies tokens and publishes resource metadata; Vercel MCP accepts CIMD clients. [Vercel profile](https://agentmcpdirectory.com/hosts/vercel/) ### 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](https://docs.composio.dev/docs/mcp-quickstart), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Users authenticate toolkits through auth configs; DCR not documented. [Composio profile](https://agentmcpdirectory.com/hosts/composio/) ### Zapier MCP Exposes Zapier actions across 9,000+ apps to MCP clients through one server at mcp.zapier.com, with Zapier holding the app credentials and charging tasks per tool call. Difference on oauth with client registration: Zapier MCP reads "OAuth for clients" ([source](https://docs.zapier.com/mcp/home), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Most clients sign in with OAuth; DCR not stated. [Zapier MCP profile](https://agentmcpdirectory.com/hosts/zapier-mcp/), [Zapier MCP vs Apify MCP](https://agentmcpdirectory.com/compare/zapier-mcp-vs-apify-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](https://www.mintlify.com/docs/ai/model-context-protocol), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Claude, ChatGPT, Cursor and Devin always allowed; others need redirect domains added. [Mintlify MCP profile](https://agentmcpdirectory.com/hosts/mintlify-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](https://docs.browserbase.com/integrations/mcp/setup), 4 November 2026); Apify MCP reads "OAuth" ([source](https://docs.apify.com/platform/integrations/mcp), 4 November 2026). Query parameter auth. [Browserbase MCP profile](https://agentmcpdirectory.com/hosts/browserbase/), [Apify MCP vs Browserbase MCP](https://agentmcpdirectory.com/compare/apify-mcp-vs-browserbase/) Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/hosts/apify-mcp/alternatives/index.md) ## Sources - [Apify MCP home](https://docs.apify.com/platform/integrations/mcp), read 4 November 2026 - [Cloudflare: developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x](https://developers.cloudflare.com/changelog/post/2026-10-01-workers-oauth-provider-1x/), read 4 November 2026 - [Vercel: vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents](https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents), read 4 November 2026 - [Composio: docs.composio.dev/docs/mcp-quickstart](https://docs.composio.dev/docs/mcp-quickstart), read 4 November 2026 - [Zapier MCP: docs.zapier.com/mcp/home](https://docs.zapier.com/mcp/home), read 4 November 2026 - [Mintlify MCP: www.mintlify.com/docs/ai/model-context-protocol](https://www.mintlify.com/docs/ai/model-context-protocol), read 4 November 2026 - [Browserbase MCP: docs.browserbase.com/integrations/mcp/setup](https://docs.browserbase.com/integrations/mcp/setup), read 4 November 2026 Last reviewed 4 November 2026