Apify MCP Server
Current Spec Verified Confidence: Good (0.85)Apify MCP Server is an MCP server published by Apify with verified support for the current MCP specification revision (2026-07-28). It is the first-party server from Apify. Last verified 2026-08-18.
Does Apify MCP Server support the current MCP specification (2026-07-28)?
Yes. Apify MCP Server has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-18).
Is Apify MCP Server a first-party (official) MCP server?
Yes. Apify MCP Server is the first-party MCP server published by Apify (last verified 2026-08-18).
How do I connect to Apify MCP Server?
Apify MCP Server is available via a hosted remote endpoint at https://mcp.apify.com/, the package npm:@apify/actors-mcp-server, the official MCP Registry under com.apify/apify-mcp-server, the source repository at https://github.com/apify/apify-mcp-server. Authentication: oauth. Transports: streamable-http, stdio.
Does Apify MCP Server support MCP revision 2026-07-28?
Yes. Apify MCP Server supports MCP revision 2026-07-28 (checked 2026-08-18).
When were Apify MCP Server's facts last verified?
2026-08-18. Each fact on this page links to the sources used to verify it.
Apify's MCP server fronts the Apify platform: the Store of prebuilt scrapers and automations, the datasets those runs produce, and the documentation search. Its distinguishing behaviour is that it can also load an individual Actor's own MCP tools, so one endpoint proxies tool surfaces that other people published.
The hosted endpoint is https://mcp.apify.com/ over streamable HTTP. An
unauthenticated request returns 401. Apify documents OAuth as the
recommended flow, with an Authorization: Bearer <APIFY_TOKEN> header as
the alternative, and offers a local stdio option through npx for clients
that prefer to run it themselves. The registry record for
com.apify/apify-mcp-server lists version 0.14.3, published 2026-08-12,
and marks the Authorization header as required and secret.
No Apify surface names a supported MCP revision, so spec support is recorded as unverified rather than inferred from the SDK the project depends on.
Which MCP spec revisions does Apify MCP Server support?
Apify MCP Server has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Supported | Source |
How widely adopted is Apify MCP Server?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record com.apify/apify-mcp-server version 0.14.3 (published 2026-08-12, isLatest) - repository apify/apify-mcp-server, one streamable-http remote at https://mcp.apify.com/ requiring a secret Authorization header described as "Apify API token for authentication with Apify platform services"; the com.apify namespace is domain-verified - accessed
- Apify MCP documentation - names the endpoint https://mcp.apify.com, gives OAuth as the recommended auth ("redirected to your browser to sign in to Apify and authorize the connection") with an "Authorization: Bearer <APIFY_TOKEN>" alternative, states Streamable HTTP is the current transport and that "Server-Sent Events (SSE) transport will be removed on April 1, 2026", offers a local stdio option via npx, and documents tools including search-actors, search-apify-docs, get-dataset-items and call-actor - accessed
- Direct request to https://mcp.apify.com/ returned HTTP 401, confirming the endpoint is live and requires credentials - accessed
- apify GitHub organization - GitHub-verified, site apify.com, owns the apify/apify-mcp-server repository (4110 stars); the npm package name @apify/actors-mcp-server is the one named in the project's own security advisory GHSA-6gr2-qh89-hxwm - accessed
- Endpoint probe of https://mcp.apify.com/ - answered server/discover at 2026-07-28 - accessed
- Endpoint probe of https://mcp.apify.com/ - answered server/discover at 2026-07-28 - accessed