Apify Official Remote MCP Server
Apify's hosted MCP (mcp.apify.com) is a gateway to the Actor Store โ agents discover scrapers and automations, read their input schemas and execute them as MCP tools.
- Provider
- Apify โ
- Source
- https://github.com/apify/apify-mcp-server โ
- Categories
- ๐ Multi-App Gateways & Automation๐ Documentation, Search & Context
ไธญๆ็ฎไป
Apify ๅฎๆน่ฟ็จ MCP ็ฝๅ ณใAI ไปฃ็ๅฏ้่ฟ OAuth ๆ็ดข 10000+ ไธช Actor๏ผ็ฝ้กตๆๅไธ่ชๅจๅๅทฅๅ ท๏ผใๆฅ็ๅ ถ่พๅ ฅๆจกๅผๅนถ่ฟ่กๅฎไปฌใ
Maintainer of Apify Actors MCP Gateway? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com"
}
}
}claude mcp add --transport http apify https://mcp.apify.com
Or add to .vscode/mcp.json:
{
"servers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.apify.com - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.apify.com"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"apify": {
"serverUrl": "https://mcp.apify.com"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.apify] url = "https://mcp.apify.com"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"apify": {
"type": "streamableHttp",
"url": "https://mcp.apify.com"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"apify": {
"httpUrl": "https://mcp.apify.com"
}
}
}๐งฐ Apify Actors MCP Gateway MCP Tools & Schema (15)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search-actors ~30 tok | ๐ข Read | Search Apify Store for Actors. | โ |
| fetch-actor-details ~34 tok | ๐ข Read | Get details and input schema of an Actor. | โ |
| call-actor ~30 tok | ๐ Write | Run an Actor and get its output. | โ |
| get-actor-output ~31 tok | ๐ข Read | Retrieve output of an Actor run. | โ |
| add-actor ~31 tok | ๐ Write | Add an Actor to the available toolset. | โ |
| remove-actor ~31 tok | ๐ Write | Remove an Actor from the toolset. | โ |
| get-actor-run ~30 tok | ๐ข Read | Get details of an Actor run. | โ |
| get-actor-log ~29 tok | ๐ข Read | Get logs of an Actor run. | โ |
| scrape-single-url ~32 tok | ๐ข Read | Scrape a single URL into markdown. | โ |
| fetch-apify-docs ~30 tok | ๐ข Read | Fetch Apify documentation. | โ |
| search-apify-docs ~30 tok | ๐ข Read | Search Apify documentation. | โ |
| get-dataset-items ~32 tok | ๐ข Read | Get items from an Apify dataset. | โ |
| list-actor-runs ~29 tok | ๐ข Read | List runs of an Actor. | โ |
| get-dataset ~28 tok | ๐ข Read | Get details of a dataset. | โ |
| get-key-value-store ~31 tok | ๐ข Read | Get a key-value store record. | โ |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Hosted gateway multiplexing multiple backends
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Protected resource metadata
- https://mcp.apify.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Apify Actors MCP Gateway MCP Endpoint Overview & Security Guide
Apify Actors MCP Gateway โ Remote MCP Server
Apify's MCP gateway is the widest scraping surface in the directory โ 10,000+ published Actors for Google Maps, Instagram, Amazon, LinkedIn and more, each dynamically exposed as an MCP tool with its own input schema, run under your Apify OAuth grant.
Official Apify Actors MCP Gateway Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.apify.com - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Apify Actors MCP Gateway does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Apify Actors MCP Gateway uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Of the 5 cataloged tools, 4 are read-only and 1 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - Actor runs bill to your Apify account โ watch compute-unit usage on large crawls.
- Tool discovery is dynamic: search Actors first, then call them via call-actor.
๐ How to Connect
- Copy the Apify Actors MCP Gateway endpoint URLThe remote endpoint is https://mcp.apify.com.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http apify https://mcp.apify.com. Cursor: add"apify": { "url": "https://mcp.apify.com" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Apify consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.apify.com into remotemcp.net/inspector, run initialize and tools/list, and confirm Apify Actors MCP Gateway's 5 tools respond.
โ FAQ
What is the Apify Actors MCP Gateway remote MCP endpoint?
The primary endpoint is https://mcp.apify.com. It is a hosted gateway server operated by Apify, speaking the Streamable HTTP transport.
How do I authenticate with Apify Actors MCP Gateway?
Apify Actors MCP Gateway uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Apify Actors MCP Gateway โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Apify Actors MCP Gateway?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http apify https://mcp.apify.com`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Apify Actors MCP Gateway expose?
5 tools are cataloged in this directory โ including `search_actors`, `get_actor_details`, `call_actor` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Browserbase's hosted remote MCP server. Browserbase's hosted MCP gives agents cloud headless-browser sessions powered by Stagehand โ navigate pages, extract structured data, take screenshots and automate web workflows at scale. It is public and unauthenticated โ connect and call tools immediately.
Zapier's MCP gateway โ one endpoint that proxies thousands of app actions (Gmail, Slack, Sheets...) as MCP tools with your Zapier-connected accounts.
HubSpot's official remote MCP server. Agents can search CRM objects โ contacts, companies, deals โ read properties and create or update records over OAuth.
Composio's remote MCP gateway exposing 250+ SaaS toolkits (GitHub, Slack, Notion...) with managed OAuth โ one endpoint for multi-app agent workflows.