Other MCP clients (Gemini, Cursor, Notion, PostHog)
Spiderlook MCP works with Gemini, Cursor, Notion, PostHog, and any other client that supports MCP. Each connection uses the same remote endpoint and OAuth project consent — never a pasted bearer token.
What every client needs
Open Settings → AI agents in Spiderlook for the endpoint copy and any deeplinks. The MCP server URL is https://api.spiderlook.com/mcp (a trailing slash is accepted). Register Spiderlook as a remote MCP server in the client, complete OAuth, and approve one project on the consent screen.
After connect, ask the assistant to list the workspace or projects it can see, then ask a grounded question about a rival’s recent ads or activity. If tools fail, revoke the stale connector and reconnect — see MCP troubleshooting.
How do I connect Gemini?
Use an MCP-capable Gemini client (for example Gemini CLI). Add a remote HTTP MCP server named Spiderlook with URL https://api.spiderlook.com/mcp. Prefer the client’s documented add-MCP command or settings file rather than inventing menu labels that change between Gemini surfaces.
When the client starts OAuth, sign in to Spiderlook and approve the project. Verify by asking Gemini to list workspace projects, then ask about one rival in that project. Do not paste a bearer token.
How do I connect Cursor?
In Cursor, open Customize → MCPs to add a remote server, or create a project .cursor/mcp.json / global ~/.cursor/mcp.json entry. Configure a remote server with URL https://api.spiderlook.com/mcp (for example under mcpServers.spiderlook.url).
Save the config, enable the server if Cursor shows a toggle, then complete OAuth when prompted. Confirm under MCP tools that Spiderlook is connected, call list_workspace, and ask a rival activity question. Revoke and recreate the server entry if OAuth never finishes.
How do I connect Notion?
Notion custom MCP servers need a Business or Enterprise workspace. A workspace admin enables custom MCP servers under Settings → Connections. Then open your agent Settings → Tools & Access → Add connection → Custom MCP server, enter https://api.spiderlook.com/mcp as the server URL, and choose OAuth when Notion asks for authentication.
After OAuth, approve one Spiderlook project, then ask the Notion agent to list rivals or summarize recent ads for a named rival. If Connect fails, confirm a workspace admin enabled custom MCP servers and that you are on Business or Enterprise, then retry OAuth.
How do I connect PostHog?
In a PostHog surface that accepts custom MCP servers (for example PostHog Desktop), add a remote MCP server for Spiderlook with URL https://api.spiderlook.com/mcp. Use that product’s add-MCP or connectors flow; if menu labels differ by build, follow the in-product MCP settings rather than a guessed path.
Complete Spiderlook OAuth and pick the project. Verify with a workspace list tool call, then a grounded competitive question. If the assistant cannot see the project, reconnect and confirm you authorized the intended landscape.
Any other client that supports MCP
Any other client that supports MCP can use the same pattern: register https://api.spiderlook.com/mcp as a remote server, finish OAuth, approve one project, then call list_workspace before other tools. Prefer Ask Spidey inside the Spiderlook app when you do not need an external client.