MCP Server / guide 6 of 19
MCP credentials are managed from Dashboard → MCP access. The page shows active and historical credentials in a table so you can compare scope, last use, expiry, and creation time without exposing the secret again.
| Column | Meaning |
|---|---|
| Credential | Friendly name, active/expired/revoked status, and the final four characters of the key preview. |
| Access | Granular capabilities plus all tracked Actors or an explicit Actor allowlist. MCP credentials are for ActorConsole MCP access only. |
| Last used | The last successful request made with that credential. A dash means it has not been used yet. |
| Expires / created | Lifecycle dates shown in your browser locale so old credentials are easy to identify. |
Security rule
Store the value as ACTORCONSOLE_API_KEY. Never commit it to a repository, browser bundle, screenshot, or shared prompt. If it is exposed, rotate it from the dashboard immediately.
| Status | Troubleshooting |
|---|---|
| 401 | The credential is missing, malformed, expired, or revoked. |
| 403 | The plan, selected capability, feature flag, or Actor allowlist denied the operation. |
| 409 | A workspace prerequisite, active run, stale proposal, or idempotency conflict must be resolved. |
| 413 | The hosted MCP request exceeded the 1 MiB transport payload limit. |
| 429 | The key, workspace, or tool-specific rate limit was reached; honor Retry-After. |
| 503 | A queue or dependent ActorConsole service is temporarily unavailable. |
The clearest way to operate Apify actors from first signal to shipped release.
Built for
Apify Actor builders
Independent developers, studios, and product teams.
Security posture
Explicit and auditable
Credentials encrypted, actions reviewed, changes recorded.