# Facebook Comments Scraper (`fetch_cat/facebook-comments-scraper`) Actor

Export public Facebook post comments for social listening, moderation analysis, campaign reporting, and creator intelligence workflows.

- **URL**: https://apify.com/fetch_cat/facebook-comments-scraper.md
- **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community)
- **Categories:** Social media, Marketing, AI
- **Features:** Limited permissions
- **Stats:** 8 total users, 3 monthly users, 93.6% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.23 / 1,000 comment extracteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Export visible public Facebook post comments to a structured dataset for social listening, moderation review, campaign reporting, and research. Facebook Comments Scraper accepts post URLs and returns comment text, author names, displayed dates, and available engagement details for CSV, JSON, Excel, or API export.

The Actor runs logged out. Facebook may hide comments or require login even on a public post, so results can be partial. A requested limit is not a completeness guarantee. Numeric reel URLs are opened through Facebook's public watch view for the same video. Permalink URLs with an explicit owner ID and post ID are opened through the equivalent public post path, which can expose comments hidden by the permalink's logged-out redirect. `sourcePostUrl` retains your original input URL. Neither transformation signs in or guarantees complete comment access.

### Quick start

1. Paste a public Facebook post URL into **Public Facebook post URLs**.
2. Start with `maxCommentsPerPost: 20`, then select **Save & Start**.
3. Open the dataset to review or download the results. If it is empty, inspect the run's `RUN-SUMMARY` key-value record for warnings.

```json
{
  "startUrls": [{ "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl" }],
  "maxCommentsPerPost": 20
}
```

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

https://youtu.be/1OW8gOqlZbY?t=25

### Ready-to-run examples

Choose a public example to see its settings before starting a run:

- [Compare Facebook Comments Across Public Posts](https://apify.com/fetch_cat/facebook-comments-scraper/examples/compare-facebook-comments-across-posts)
- [Facebook Comments API Example](https://apify.com/fetch_cat/facebook-comments-scraper/examples/facebook-comments-api-example)
- [Scrape Facebook Comments from a Public Post](https://apify.com/fetch_cat/facebook-comments-scraper/examples/scrape-facebook-comments-from-public-post)

### What you get

- **Primary job**: Export Facebook comments data from public post URLs.
- **Input**: One or more public Facebook post URLs plus a per-post comment limit.
- **Output**: One dataset row per saved comment with author name, comment text, relative date, likes, source post URL, raw visible text, and scrape timestamp.
- **Best for**: Social listening, engagement analysis, moderation triage, creator intelligence, dashboards, alerts, and research exports.

#### What data can you extract?

| Field | Description |
| --- | --- |
| `commentId` | Facebook comment ID when available. Otherwise a derived identifier that can change when the displayed text or date changes. |
| `sourcePostUrl` | Facebook post URL that produced the comment. |
| `postTitle` | Visible post/page label or title captured from the public page. |
| `authorName` | Publicly visible comment author name. |
| `authorUrl` | Public author/profile URL when Facebook exposes it in the logged-out view. |
| `commentText` | Cleaned visible comment text. |
| `relativeDate` | Visible Facebook relative date label, such as `2w` or `1y`. |
| `likeCount` | Visible comment-like count when present. |
| `replyDiagnostics` | Visible reply count/label when present. |
| `commentPermalink` | Comment permalink when Facebook exposes it publicly. |
| `rawText` | Raw visible row text used for audit and parser diagnostics. |
| `scrapedAt` | ISO timestamp when the row was saved. |

### Who is it for?

- **Social listening teams** tracking public reactions to brand, creator, media or campaign posts.
- **Moderation and community teams** reviewing visible comment text, authors and source URLs in downstream tools.
- **Analysts and researchers** preparing Facebook comment exports for their own reports or archives.

### How you can use the data

- **Review reactions to a known campaign post.** Supply its public post URL with a small per-post cap. Keep `commentText`, `sourcePostUrl`, `relativeDate` and `scrapedAt` together before comparing themes in your own reporting.
- **Prepare a moderation-review sheet.** Export visible comment text, author names and source links to your own review queue. Treat each row as material for human review rather than an automated moderation decision.
- **Research a creator's visible audience responses.** Inspect comment text and available likes or reply labels from a supplied public post. Reply labels do not provide the full nested reply tree, and sentiment analysis belongs in a separate downstream step.
- **Compare separate post exports carefully.** Retain source post URLs and capture times alongside IDs. A derived comment ID can change when Facebook changes displayed text or date labels, and the Actor does not track new comments between runs.

### Input settings

| Setting | JSON key | Use it for | Example |
| --- | --- | --- | --- |
| Public Facebook post URLs | `startUrls` | Required post or reel URLs. Unavailable views may produce no rows; unresolved login gates fail with diagnostics. Inspect the run summary. | `[{"url":"https://www.facebook.com/humansofnewyork/posts/..."}]` |
| Maximum comments per post | `maxCommentsPerPost` | Cap saved comments per post and control spend. | `20` |
| Legacy alias | `maxItems` | Backward-compatible alias for older integrations. Prefer `maxCommentsPerPost`. | `20` |

#### Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

### Output data

Illustrative shape only, not an observed comment or a promise of available data:

```json
{
  "commentId": "derived_example",
  "sourcePostUrl": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl",
  "postTitle": "Humans of New York",
  "authorName": "Example author",
  "authorUrl": null,
  "commentText": "Example comment text.",
  "relativeDate": "2w",
  "likeCount": 12,
  "replyDiagnostics": "1 reply",
  "commentPermalink": null,
  "rawText": "Example author Example comment text. 2w 12 1 reply",
  "scrapedAt": "2026-07-31T18:42:04.000Z"
}
```

#### Download your results

Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options.

### Pricing

The `start` event is charged once after valid post input and run-limit preflight, including runs that later save no comments. The `comment` event is charged once per saved comment row. Warnings and diagnostic records are not comment rows. If your maximum charge cannot cover startup plus one comment, the Actor stops before browsing or explicitly charging. Rows already saved are preserved when a customer cost or shorter timeout limit is reached; inspect `limitStop` in `RUN-SUMMARY` (also saved as `RUN_SUMMARY`). Allow at least 45 seconds for useful work and safe shutdown.

Current rates and account-tier discounts are shown on the live [Apify Pricing tab](https://apify.com/fetch_cat/facebook-comments-scraper/pricing). Check it before collecting larger batches.

### Tips for best results

- **Choose posts visible without login.** Public status alone does not guarantee that Facebook exposes comments in a logged-out view.
- **Start with a small per-post cap.** Inspect the visible fields before increasing later exports.
- **Split large post lists into smaller batches.** A blocked or unavailable target should not dominate your review of unrelated posts.
- **Keep source links and capture times in downstream records.** Relative dates and derived IDs can change between exports.
- **Inspect warnings after an empty export.** Read `RUN-SUMMARY` and any diagnostic record before interpreting unavailable comments.

### Limits and caveats

- The Actor does not offer sorting or date filters. It uses Facebook's displayed order, not a guaranteed newest-first or exhaustive order.

- Reply labels are not a complete nested reply tree. Sentiment analysis, alerts, and cross-run comparisons require downstream tools.

- HTTP 404/410 responses and explicit no-comments views succeed with an empty dataset, warnings in `RUN-SUMMARY`, and a `diagnostics-N` record. Inaccessibility alone does not establish whether a post is private or deleted. A login gate is not proof that comments are absent: a zero-output gate or unrecognized view is retried once in a fresh anonymous page. Persistent failures remain fatal while preserving useful rows from other targets. Storage, billing and network exceptions are not retried.

- Blocking, unrecognized empty responses, and unfinished extraction fail the run while preserving already saved comments. Explicit customer cost or shorter timeout stops instead succeed with a limit warning, status and summary. An independent five-minute cap remains enforced; exceeding our own cap is still a failure. Up to two targets are processed concurrently only when the effective budget covers the batch's maximum possible output; smaller budgets stay sequential. Output writes and charges are always serialized. The verified default allocation is 4 GiB to provide sufficient CPU for multi-post comment expansion; lower memory overrides may not finish larger batches. Split larger lists into smaller batches.

- The Actor runs against public, visible Facebook post pages. It does not log in, bypass privacy settings, or return private comments.

- Facebook can hide, reorder, or limit comments in public views. The dataset reflects what was visible during the run.

- Some optional fields, especially author URLs and comment permalinks, are only saved when Facebook exposes them publicly.

- Relative dates are captured as displayed by Facebook. Use `scrapedAt` with `relativeDate` for freshness analysis.

### Automation and integrations

#### Save your settings for next time

Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch.

#### Run on a schedule

Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

#### Send results to your other tools

Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool.

For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

### API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its `defaultDatasetId` to fetch the results.

For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post).

#### cURL

```bash
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~facebook-comments-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl"
    }
  ],
  "maxCommentsPerPost": 20
}
JSON
```

#### Node.js

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/facebook-comments-scraper').call({
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl"
    }
  ],
  "maxCommentsPerPost": 20
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/facebook-comments-scraper').call(run_input={'startUrls': [{'url': 'https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl'}], 'maxCommentsPerPost': 20})
print(client.dataset(run['defaultDatasetId']).list_items().items)
```

### MCP and AI agents

You can ask your AI assistant to collect data with **Facebook Comments Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app.

#### Easier setup with an Apify plugin

If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

#### Use Apify AI in Console

Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Facebook Comments Scraper**. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

#### Choose your assistant

- **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude).
- **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai).
- **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot).
- **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI.

#### Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/facebook-comments-scraper"
    }
  }
}
```

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

#### Use Apify's general server

Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Facebook Comments Scraper** by Fetch Cat, or give it the identifier `fetch_cat/facebook-comments-scraper`.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

#### Example requests

- “Use Fetch Cat’s Facebook Comments Scraper to collect up to 5 visible comments from the public post URL I provide. Show comment text, source post links and displayed dates with collection times for manual campaign review.”
- “Collect at most 3 comments per post from these 2 public Facebook post URLs. Include visible author names and available likes so I can prepare a human moderation-review sheet.”
- “Retrieve up to 5 visible comments from my supplied creator post. Keep reply labels separate from comment text, and explain any partial or empty outcome without claiming a full reply tree or newest-first order.”

Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/facebook-comments-scraper/pricing) before asking your assistant to run a larger batch.

### Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account.

[Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

#### Other ways for agents to pay

Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup.

### FAQ

#### What data can I export with Facebook Comments Scraper?

You can export visible public comment text, author names, source post URLs, relative dates, likes when shown, reply labels when shown, raw visible text, and scrape timestamps.

#### Can I run Facebook Comments Scraper through an API, schedule, or MCP client?

Yes. Use the Apify API, webhooks, or the official Apify MCP Server. Repeated execution and comparison are external workflow features, not built-in monitoring or new-comment detection.

#### How much does it cost to use Facebook Comments Scraper?

The Actor charges a startup event and a per-comment event for each saved dataset row. Check the live Apify Pricing tab for current tier prices before running large jobs.

#### How do I export Facebook comments data to CSV or Excel?

Run the Actor with public post URLs, open the default dataset, and choose CSV, Excel, JSON, XML, RSS, or API export from Apify.

#### Why are some author URLs or comment links empty?

Facebook does not always expose profile links or comment permalinks in logged-out public views. The Actor leaves unavailable optional fields empty instead of guessing.

#### Can it scrape private groups or comments behind login?

No. The first version is limited to visible public post comments and does not use user accounts or private permissions.

### Related Actors

#### More Facebook scrapers

- [Facebook Ads Library Scraper](https://apify.com/fetch_cat/facebook-ads-library-scraper) — Collect public Meta ad copy, advertiser details and available creative links for advertising research.
- [Facebook Events Scraper](https://apify.com/fetch_cat/facebook-events-scraper) — Collect public event dates, venues, hosts and ticket links from event or organizer targets.
- [Facebook Marketplace Scraper](https://apify.com/fetch_cat/facebook-marketplace-scraper) — Collect visible public listing titles, prices, locations and a primary image for local inventory research.
- [Facebook Pages Scraper](https://apify.com/fetch_cat/facebook-pages-scraper) — Collect public Page profile and contact fields, visible audience counts and optional post links.
- [Facebook Reels Scraper](https://apify.com/fetch_cat/facebook-reels-scraper) — Collect public Reel URLs, IDs and available owner and play-count metadata from known Reels or profile tabs.

### Support and feedback

For custom additions or integrations, email <hello@fetchcat.dev>.

Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/facebook-comments-scraper/issues) with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/facebook-comments-scraper/reviews) to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

# Changelog

This Actor's version history is a separate document: https://apify.com/fetch_cat/facebook-comments-scraper/changelog.md

# Actor input Schema

## `startUrls` (type: `array`):

Required: one or more public facebook.com post URLs. Runs logged out with direct access; no login, proxy selector, or automatic proxy fallback is supported. Facebook may hide comments or request login even for a public post. Empty extraction is explained in RUN-SUMMARY and diagnostics records, not proof of privacy or deletion. Use a small input first.

## `maxCommentsPerPost` (type: `integer`):

Save up to this many visible comments per post (1–500; default 20). This is a cap, not a guarantee: Facebook controls visibility and displayed order. No sorting or date filtering is applied. When both limit fields are supplied, this field takes precedence.

## `maxItems` (type: `integer`):

Per-post limit used only when maxCommentsPerPost is omitted. Accepts 1–500; if both limits are omitted, runtime uses 20. Use Maximum comments per post for new inputs.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl"
    }
  ],
  "maxCommentsPerPost": 20
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fetch_cat/facebook-comments-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [{ "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl" }] }

# Run the Actor and wait for it to finish
run = client.actor("fetch_cat/facebook-comments-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/posts/pfbid0BbKbkisExKGSKuhee9a7i86RwRuMKFC8NSkKStB7CsM3uXJuAAfZLrkcJMXxhH4Yl"
    }
  ]
}' |
apify call fetch_cat/facebook-comments-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/facebook-comments-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/bqj6x0kXn3kG4tR2s/builds/oldWJvzUghcdM9Sqf/openapi.json