Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
Use cases
- Discover and inspect Apify Store Actors (`search-actors`, `fetch-actor-details`) before approving spend
- Let coding agents summarize Apify tutorials using `search-apify-docs` / `fetch-apify-docs`
- Operationalize repeatable crawl jobs referencing datasets, KV stores, logs through storage tools lists
- Prototype agentic scraping without writing bespoke REST glue for every storefront template
- Gate production rollouts behind explicit URL tool allow-lists mandated by enterprise security reviewers
Key features
- Cursor
- VS Code
- Claude Desktop
- Claude remote connectors
- Codex
Frequently Asked Questions
- Do I always need manual API tokens?
- No—hosted clients can complete OAuth flows on first launch, but Bearer headers remain supported for scripted clients per Apify MCP documentation.
- What happens if telemetry should be disabled?
- Append `telemetry-enabled=false` to the HTTPS URL when using remote mode; CLI users can pass `--telemetry-enabled=false` or set `TELEMETRY_ENABLED=false` for local stdio.
- How aggressive are rate ceilings?
- Apify states the hosted MCP tier enforces roughly 30 HTTPS operations per second per user; bursts above that return HTTP 429 and require exponential backoff logic.
Related
Related
3 Indexed items
Mem0 MCP Server
Mem0 documents a hosted Model Context Protocol server at https://mcp.mem0.ai/mcp that exposes Platform memory tools (`add_memory`, `search_memories`, `get_memories`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, `get_event_status`) to Claude, Claude Code, Codex, Cursor, Windsurf, VS Code, and OpenCode. Setup uses `npx mcp-add` with HTTP transport or manual JSON/TOML client configs; Codex requires `MEM0_API_KEY` as bearer token per docs.mem0.ai/platform/mem0-mcp. The cloud server needs a Mem0 Platform API key from the dashboard and Node.js for the installer—no local vector database required for the hosted path.
Langfuse MCP Server
Langfuse documents two MCP surfaces: a hosted Prompt Management server at `https://cloud.langfuse.com/api/public/mcp` (streamable HTTP, built into the platform per langfuse.com/docs/prompt-management/features/mcp-server) with tools such as `createTextPrompt`, `createChatPrompt`, `getPrompt`, and `updatePromptLabels`; and a public Docs MCP at `https://langfuse.com/api/mcp` for semantic search over Langfuse documentation (`searchLangfuseDocs`) without authentication. The legacy `langfuse/mcp-server-langfuse` Node server remains for local command-based setups with LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY. Langfuse positions MCP for agentic onboarding—IDE agents can add tracing to OpenAI, Anthropic, or LangChain codebases from the Get Started agentic tab.
n8n MCP Server Trigger
The MCP Server Trigger is a first-party n8n core node that turns an n8n workflow into a Model Context Protocol server endpoint. Instead of chaining conventional trigger nodes, it connects only to tool nodes so remote MCP clients can list tools and invoke them over long-lived Server-Sent Events or streamable HTTP transports (stdio is explicitly unsupported). Each node exposes separate test and production MCP URLs, optional bearer or header authentication, and documentation explains how to proxy Claude Desktop through `npx mcp-remote` plus queue-mode caveats for multi-replica webhook deployments.