Connect Spiderlook to Claude
The recommended path is the official Claude directory listing. Manual remote MCP setup remains a fallback for Desktop, Code, and claude.ai — use it only when the directory path is unavailable.
How do I connect from the Claude directory?
Open https://claude.ai/directory/spiderlook and add Spiderlook from the directory listing. Claude starts OAuth and opens Spiderlook so you can sign in and approve access for one project.
You can also start from Settings → AI agents → Claude, which deep-links the same directory path. Do not paste a bearer token. The directory path is preferred because it keeps install and updates aligned with Anthropic’s listing.
How do I approve the project?
On the Spiderlook OAuth consent screen, confirm the organization and project the assistant should see. Only that project’s rivals, activity, and tools are in scope for the connection.
If you pick the wrong project, revoke the connector in Claude and reconnect, choosing the correct landscape on consent.
How do I verify in Claude?
Ask Claude to list the projects and rivals you can access (list_workspace). Then ask a grounded question about a rival’s recent ads or activity. Answers should cite project evidence, not generic web knowledge.
If tools fail, see MCP connection troubleshooting. Common fixes: retry via the directory, clear a stale Claude MCP cache, and confirm the signed-in user can open the project in the Spiderlook app.
Manual setup (not recommended)
Manual remote-MCP setup for Claude Desktop, Claude Code, and Claude on the web uses https://api.spiderlook.com/mcp. This path is not recommended when the directory listing works — prefer the directory so OAuth and listing stay consistent.
If you must use manual setup, register the remote URL, complete OAuth, approve one project, then verify with list_workspace. Full endpoint, CLI, and tool reference live on the MCP docs page.
How should teams use Claude with Spiderlook?
Agency account teams should connect Claude only to the client project they support. Brand strategists usually connect once to the primary landscape. Revoke connectors when someone leaves so OAuth tokens do not outlive access.
Use Claude for narratives, battlecard drafts, and meeting prep grounded in Spiderlook tools. Keep Ask Spidey for quick in-app questions beside Home and rival tabs. When tools error after a project rename, reconnect via the directory and approve the renamed project.
If Desktop or Code was configured manually earlier, migrate to the directory listing when possible so install stays aligned with Anthropic’s Spiderlook entry.