apify website-content-crawler fails: proxyConfiguration required even when not sent
With apify-mcp-server, the apify-slash-website-content-crawler tool fails with AI_InvalidToolArgumentsError saying proxyConfiguration is required even though the call doesn't include it. Both WCC and a mastra.ai agent hit this error. Is this a known server bug and was it fixed?
Originally asked on GitHub: https://github.com/apify/apify-mcp-server/issues/44
4 answers
Status: fixed. A contributor stated the problem was "fixed (hacked together)" in https://github.com/apify/actors-mcp-server/pull/45 (opens external site), and the issue was closed as COMPLETED. The thread does not name a release version or describe what changed inside the PR.
The failure is a tool-argument validation error from apify-slash-website-content-crawler. A call such as:
json{"startUrls":[{"url":"https://shveik.dev"}],"crawlerType":"playwright:adaptive","maxCrawlPages":5}failed with:
AI_InvalidToolArgumentsError: Invalid arguments for tool apify-slash-website-content-crawler: Type validation failed ... {"code":"invalid_type","expected":"object","received":"undefined","path":["proxyConfiguration"],"message":"Required"}The original report was a bad WCC run, and a contributor also saw the same failure from a mastra.ai agent with the WCC proxy configuration. The thread does not mention a client-side configuration change that fixes the error. General advice: use a build of the MCP server that includes PR #45; since no release version was named, check the package's release notes or changelog if you install a released binary.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
The issue reporter ran the tool with WCC and reported a bad run, linking to an Apify run log. The thread does not describe what the log showed.
Source: https://github.com/apify/apify-mcp-server/issues/44 (opens external site)
Did this work for you?What @MQ37 tried on GitHub (Didn't work)
A contributor reported that a mastra.ai agent failed with the WCC proxy configuration and included the exact AI_InvalidToolArgumentsError output. This reproduced the same validation failure but no workaround was proposed in that comment.
Source: https://github.com/apify/apify-mcp-server/issues/44#issuecomment-2727656482 (opens external site)
Did this work for you?What @MQ37 tried on GitHub (Worked)
A contributor stated the problem was fixed in apify/actors-mcp-server PR #45. The issue was then closed as COMPLETED.
Source: https://github.com/apify/apify-mcp-server/issues/44#issuecomment-2768551815 (opens external site)
Did this work for you?
Related questions
- OpenAI rejects apify-mcp-server tools: 'array schema missing items' and '--' in tool name
- Open WebUI not calling apify-mcp-server — what URL should I use?
- Why does Apify MCP server truncate Actor output and call get-dataset-items again?
- Why does 'playwright mcp screenshot' find no Actor in the apify-mcp-server search?
- Can apify-mcp-server call-actor call an Actorized MCP server?