← Back to directory
A

Analook MCP Server

Community
Understand any competitor in 30 seconds — competitor intelligence for AI agents
GitHub source repository ↗
★ 110 Stars Category · Other Popular
55FMRS · C

Analook is the MCP surface of analook.com, exposing 5 tools over remote streamable-http for MCP clients and producing competitor teardowns from public data sources plus LLMs. It suits indie hackers, growth teams, and investors who need fast competitor intelligence; it is not a fit for teams requiring offline self-hosting or sensitive about data leaving to third-party services. An access token is required, and report conclusions should be reviewed by a human.

Reliability
9/20
Security and permissions
12/20
Maintenance
8/20
Documentation
13/20
Setup experience
13/20
Read the FMRS scoring method →

Analook is a remote MCP server that powers the analook.com backend, bringing competitor intelligence to AI agents: SEO, traffic, social, Product Hunt, pricing, and AI insights. Built on FastAPI + Supabase, it runs a 7-module parallel analysis pipeline that turns any product URL into a structured competitor teardown report. Any MCP-compatible client can connect over streamable-http at https://www.analook.com/mcp/ with no local install.

Tools

analyze_competitor
Submit a competitor URL to start an analysis and generate a structured competitor teardown report.
get_report_status
Check the current processing status of an analysis job.
get_report
Retrieve the completed analysis report as structured data.
get_report_markdown
Retrieve the completed analysis report in Markdown format.
list_my_reports
List previously generated reports for the current account.

Setup

  1. Obtain an Analook access token (see https://www.analook.com/docs/mcp.html for token instructions).
  2. Add the remote server to your MCP client config:
{
  "mcpServers": {
    "analook": {
      "url": "https://www.analook.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_ANALOOK_TOKEN>" }
    }
  }
}
  1. Save the config and restart your client.
  2. This is a remote server — no local install or process is required.
claude_desktop_config.json
{
  "mcpServers": {
    "analook": {
      "url": "https://www.analook.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_ANALOOK_TOKEN>" }
    }
  }
}

Fit and risk

Best for

  • Indie hackers who want competitor intelligence callable directly by an agent
  • Growth teams benchmarking against competitors
  • Investors doing quick pre-DD intelligence gathering
  • Founders preparing a launch in a crowded market

Not for

  • Teams requiring fully offline or self-hosted deployment with no data sent to third-party services
  • Self-hosted setups that cannot supply third-party API keys (such as DataForSEO, Apify, Product Hunt, and LLM providers)
  • Users expecting non-public internal data (this tool works from public signals only)
  • Clients that only support local stdio MCP processes and not remote HTTP MCP

Required permissions

  • Requires a valid Analook access token (Bearer token) for remote MCP authentication
  • Analysis depends on third-party data-source API keys (DataForSEO, Apify, Product Hunt, TeamoRouter, DeepSeek)
  • Server-side use of Supabase for auth, credits, and report storage

Risks and side effects

  • Reports are generated by third-party LLM and data services and may contain inaccurate or outdated information; verify key conclusions manually
  • Results are inferred from public signals, and business-model or revenue estimates are ranges and hypotheses only
  • Requests are sent to the remote service https://www.analook.com/mcp/, so data-transfer and compliance requirements should be assessed
  • A leaked token may allow others to consume your account credits
  • The repository declares no license metadata (the README states MIT); confirm authorization before commercial use

Troubleshooting

  1. Connection fails: confirm the client uses streamable-http and the URL is https://www.analook.com/mcp/
  2. Unauthorized responses: check that the Bearer token in the Authorization header is valid and unexpired
  3. Report stays in progress: use get_report_status to check the job, then retry or start a new analysis
  4. Empty report: confirm the job is complete before calling get_report or get_report_markdown
  5. Self-hosted analysis fails: verify all third-party service keys are set in .env

Use cases

Validate a market and competitive landscape before building
Generate traffic, SEO, and social benchmarks against competitors for growth teams
Collect quick competitor intelligence during pre-DD for investors
Find differentiated angles for a launch in a crowded niche

Supported clients

Claude DesktopFull support
CursorFull support