Research

The Apify connector.

Social scraping for content & creator research (Instagram, TikTok, YouTube, X). Connect once with your own key. Every agent your team runs reads the same 3 tools under one permission model.

How access is governed

2

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

1

Write tools

Available through governed Slack workflows. MCP endpoints do not expose write tools.

0

Destructive tools

Apify defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Apify tool

3 tools, named as the agent sees them.

  • apify_search_actorsread

    Search the Apify Store for scraping/automation Actors (e.g. "Instagram", "TikTok", "YouTube"). Returns actor ids to use with apify_run_actor. Prefer well-known actors: apify/instagram-scraper, apify/instagram-profile-scraper, apify/instagram-hashtag-scraper, clockworks/tiktok-scraper, clockworks/tiktok-profile-scraper, streamers/youtube-scraper, apidojo/tweet-scraper.

  • apify_run_actorwrite

    Run an Apify Actor synchronously and return its dataset items. Costs money per result on the connected Apify account — keep maxItems small (10–50) unless the user asks for more. inputJson must match the actor's input schema, e.g. for apify/instagram-profile-scraper: {"usernames":["nike"]}; for clockworks/tiktok-scraper: {"searchQueries":["fitness"],"resultsPerPage":20}.

  • apify_get_dataset_itemsread

    Fetch items from an existing Apify dataset by id (e.g. from a prior or scheduled actor run).

Use it from any agent

The same Apify tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Apify API Token in your Apify account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in research

FirecrawlPerplexityApollo

Connect Apify once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in