MCP Server / guide 8 of 19
The MCP server communicates with ActorConsole over HTTPS using a workspace MCP credential. The Apify token and AI provider credentials remain inside ActorConsole.
Create an MCP credential from Dashboard → MCP access after selecting its workspace. The credential exists only to authenticate ActorConsole MCP clients. Pro MCP clients can use only the capabilities and Actors selected for that credential. Switching the browser workspace does not change an existing credential's scope. For stdio, provide this value as the ACTORCONSOLE_API_KEY environment variable and set API_BASE_URL to the API origin. Hosted clients send the credential as an Authorization Bearer token on every MCP request.
Publishing schedules are paused by default, create/run requests support idempotency, and Apify quota responses stop the queue without dropping pending Actors. Proposal tools never apply generated changes automatically.