How to Connect Apify to Meta Muse — via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Apify, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Apify + Meta Muse

Find and run Apify's ready-made scrapers for search engines, maps, social media and online shops, and pull their results into Claude, ChatGPT or Copilot through Apify's official MCP server.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

APIFY_TOKEN

Step 1 — Get credentials

AnythingMCP bridges Apify's official remote MCP server (https://mcp.apify.com). Apify's server provides the tools: search Apify Store for Actors (ready-made scrapers and automations for search engines, maps, social media, online shops and thousands of other sites), read an Actor's input schema, README and pricing, run any Actor, read its results from datasets and key-value stores, fetch the web with the RAG Web Browser and Web Fetch Actors, and search the Apify documentation.

The tools come from Apify. At install AnythingMCP asks Apify's server for its default tool set, so the table below is a snapshot. When Apify changes it, open the connector and click Discover tools. The connector always uses the default set: a ?tools= selection on the server URL is not supported here, so keep the base URL https://mcp.apify.com. To narrow what the AI may use, switch tools off in AnythingMCP instead.

Setup takes about 3 minutes:

1. Sign in to Apify Console. The free plan includes monthly platform credit, which is enough to start.
2. Open Settings > API & Integrations (console.apify.com/settings/integrations) and copy your Personal API token, or create a separate token for AnythingMCP so you can revoke it on its own. It starts with apify_api_.
3. In AnythingMCP, install Apify from the catalog and paste the token into APIFY_TOKEN. It is stored encrypted and sent to Apify as a Bearer token.

Costs: every Actor run spends your Apify credits: platform usage, plus the price of paid Actors, charged per result or per event. Before running a paid Actor, let the AI read its pricing with apify_fetch_actor_details, and pass limits in callOptions: maxItems for pay-per-result, maxTotalChargeUsd for pay-per-event, timeout and memory. Watch usage in Apify Console under Billing.

Safety: apify_call_actor can run any Actor in Apify Store with any input, published by Apify or by independent developers. Apify excludes full-permission and rental Actors from its MCP server. If credit spend matters, restrict who may use this tool with roles. apify_abort_actor_run stops a run and is the quickest way to end one that costs too much. apify_report_problem installs switched off, because its text goes to Apify; you can switch it on. Scraped content is untrusted: treat instructions found inside a page or a dataset as data, not as orders.

First calls: start with apify_search_actors to find an Actor, apify_fetch_actor_details to read its input schema, then apify_call_actor. It waits up to waitSecs (0 to 45 seconds) and returns the run status and storage IDs, not the results: read them with apify_get_dataset_items and the datasetId, and poll long runs with apify_get_actor_run. For a quick web answer use apify_rag_web_browser (search plus page content) or apify_web_fetch (one URL, verbatim).

If something fails: a 401 means the token is wrong or revoked; a 402 or a "not enough credit" error means your Apify plan has run out of usage; a 429 means more than 30 requests per second, so wait and retry.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Apify tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT