Troubleshooting
Fix common Screpy MCP OAuth, connection, missing project, and unavailable tool issues.
Use this guide when Screpy does not connect, cannot finish OAuth, or returns unexpected project and tool results.
Diagnose a Screpy MCP issue
Check that Screpy is connected
In your AI client's MCP or connector settings, confirm that the server URL is https://mcp.screpy.com and that its status is connected or authorized.
Ask the smallest diagnostic question
Ask: "List my Screpy projects." This quickly separates a connection or permission issue from a crawl-specific question.
Reconnect only when needed
If the project-list prompt fails, disconnect Screpy in the client, add the server again, and complete the browser sign-in with the intended Screpy account.
I cannot complete authorization
Make sure your client supports remote HTTP MCP servers and OAuth. Then reconnect using https://mcp.screpy.com and complete the Screpy sign-in flow in the browser.
My REST API key does not work
REST API keys and MCP credentials are separate. Remove the API key from the MCP client and reconnect through OAuth.
My project is missing
Screpy only returns projects you can currently access. Confirm that you own the project or that it has been shared with your account.
A tool cannot access crawl data
Ask the client to list your projects first, then list the crawls for the selected project. Screpy uses the project and crawl identifiers returned by those tools.
A tool is unavailable
Refresh the MCP connection in your client. If the issue continues, disconnect Screpy, reconnect it, and complete OAuth again.
Use the smallest diagnostic question first
Do not begin with a long prompt that assumes project or crawl identifiers. Ask the client to list projects, then select a project, then list its crawls. This shows whether the problem is the connection, account permission, project access, or the specific analysis request.
If a tool returns an error, keep the project domain, request, and error message. Remove secrets before sharing any diagnostic details. A precise failing tool call is more useful than a screenshot of a general chat response.
When to reconnect or contact support
Reconnect when OAuth was cancelled, completed with the wrong account, or the client no longer shows Screpy as connected. Check workspace policy first when an organization-managed client blocks custom MCP servers. If the same issue continues after a clean reconnect and a project list succeeds, include the client name, the action you tried, and the time of the failure when contacting support.