Integrations

Apify

Connect Apify to run web scraping actors and tasks, control runs, and read datasets, stores, and request queues.

API credentialsAnalytics & SEOApify API docs

You end up with one Apify API token that starts with apify_api_. Paste it into PopMCP's API token field.

Setup time
2 min
Auth
API credentials
API base URL
https://api.apify.com/v2
Rate limits
Most endpoints allow 60 requests per second per resource. Actor runs, dataset pushes and request-queue operations allow 400 per second, key-value store CRUD allows 200 per second, and the account-wide cap is 250,000 requests per minute.

Before you begin

  • An Apify account. The free plan is enough to mint a token.
  • If your Actors belong to an Apify organisation, switch to that account in the Console first. Tokens are per account, so a personal token cannot see organisation Actors.
  • Owner access, or the Manage access tokens permission, on an organisation account.

Get your credentials

Open Settings, then API & Integrations

Sign in at console.apify.com and click Settings at the foot of the left sidebar. Open the API & Integrations tab.

Open this screen →

console.apify.com/settings/integrations
Search Actors, tasks and runsacme-supply
Settings / API & Integrations

API & Integrations

Manage the API tokens and third-party connections on this account.

AccountLogin & PrivacyAPI & IntegrationsOrganizationsNotificationsReferrals
Create new token
NameTokenPermissionsCreatedExpires
Personal API tokenDefault tokenapify_api_****7q3dFull accessJan 9, 2026Never
CI runnerScoped to 2 Actorsapify_api_****b18fLimitedMar 4, 2026Sep 1, 2026

The default Personal API token is already listed. Create a separate one for PopMCP rather than reusing it.

Create a token for PopMCP

Click Create new token and name it PopMCP. Leave Limit token permissions switched off and click Save.

Open this screen →

console.apify.com/settings/integrations
Search Actors, tasks and runsacme-supply
Settings / API & Integrations

API & Integrations

AccountLogin & PrivacyAPI & IntegrationsOrganizationsNotificationsReferrals
Create new token
Token name
PopMCP
Expiration
Never
Limit token permissionsSwitch on to pick individual Actors, tasks and storages
SaveCancel

Turning on Limit token permissions reveals Actors, Tasks and Storages pickers plus an Allow this token to access default run storages toggle.

Copy the token value

Click the copy icon next to the new token to copy the full apify_api_… string.

console.apify.com/settings/integrations
Search Actors, tasks and runsacme-supply
Settings / API & Integrations

Token created

PopMCP
API token
apify_api_****7q3d
Permissions
Full access
Expires
Never
CopyDone

A full-access token can do everything your Apify user can do. Store it the way you would store a password.

Paste it into PopMCP

In PopMCP, paste the value into API token and save.

Connect in PopMCP

Open your workspace, choose Apify in the marketplace, and fill in the connect dialog:

FieldWhat to enter
API tokensecretIn the Apify Console open Settings → Integrations (https://console.apify.com/settings/integrations) and copy your Personal API token. It's sent as the Authorization: Bearer header and stored encrypted; used server-side only. No OAuth app or client secret is required.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against Apify immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

PopMCP's Apify connector shows Connected with your account username, and listing your Actors returns the same ones you see in the Console.

Troubleshooting

401 Unauthorized on every call

Why: The token was truncated on paste, or it was rotated or expired in the Console.

Fix: Open Settings, then API & Integrations, create a fresh token, and paste the whole apify_api_ string with no surrounding spaces.

You cannot find the token value again

Why: Apify shows the complete value at creation and masks it in the list afterwards.

Fix: Delete the token and create a replacement rather than guessing at a partial value.

403 Forbidden on one Actor or dataset

Why: Limit token permissions is on and the scope does not cover that resource.

Fix: Edit the token to include the Actor and its default dataset, or replace it with a full-access token.

The connector works but sees none of your team's Actors

Why: The token belongs to your personal account rather than the organisation.

Fix: Switch to the organisation in the Console account switcher, then mint the token from that account's API & Integrations tab.

429 Too Many Requests

Why: More than 60 requests per second against a single resource, or many parallel runs.

Fix: Retry with exponential backoff. The limit applies per resource, not per token.

Reference

On this page