SpiderLook MCP

An official MCP server that connects AI assistants to SpiderLook's competitor intelligence platform. It allows agents to query daily scans of rivals' websites, social media posts, and ads, retrieve stored evidence, and manage project-specific competitive data through OAuth authentication.

Visit SpiderLook

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Vendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by SpiderLook

You need:Sign in, don't paste secrets. You connect with your SpiderLook login through OAuth.

MCP endpoint (Streamable HTTP)

https://api.spiderlook.com/mcp

Vendor documentation

What you can do with it

Query daily activity changes for tracked rivals
Retrieve stored evidence for social posts and ads
Generate and approve sales battlecards
List accessible projects and competitors

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.spiderlook/spiderlook@1.0.0 Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 317 ms
95th percentile latency: 317 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 7:03 AM UTC · probe · passed · 317 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http spiderlook-mcp https://api.spiderlook.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add spiderlook-mcp --url https://api.spiderlook.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable spiderlook-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "spiderlook-mcp": {
      "url": "https://api.spiderlook.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "spiderlook-mcp": {
      "type": "streamableHttp",
      "url": "https://api.spiderlook.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start spiderlook-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "spiderlook-mcp": {
      "type": "http",
      "url": "https://api.spiderlook.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http spiderlook-mcp https://api.spiderlook.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "spiderlook-mcp": {
      "url": "https://api.spiderlook.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "spiderlook-mcp": {
      "serverUrl": "https://api.spiderlook.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like SpiderLook MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 845

Do you run SpiderLook MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing