Hooklayer MCP MCP server

Hooklayer is an official MCP server providing viral-content intelligence for AI agents. It exposes tools to score hooks, predict virality, analyze creator accounts, extract voice DNA, and research trends across TikTok, Instagram, and YouTube. It allows agents to test content angles before filming and automate competitive analysis workflows directly within AI workspaces like Claude and ChatGPT.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Hooklayer

MCP endpoint (Streamable HTTP)

https://hooklayer.dev/api/mcp

Vendor documentation

What you can do with it

Score TikTok hooks for virality potential before filming
Analyze competitor creator accounts and extract viral DNA
Predict virality of draft scripts using evidence-layer scoring
Research trending templates and track competitor changes over time

Tools advertised by the last live check:

analyze_account
watch_account
get_changes
list_watches
score_hook
viral_remix
trend_pulse
find_viral_template
search_videos
match_voice
predict_virality
brief_to_blueprint
product_scout
analyze_product

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http hooklayer-mcp https://hooklayer.dev/api/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 hooklayer-mcp --url https://hooklayer.dev/api/mcp

Cursor

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

Cursor configuration

{
  "mcpServers": {
    "hooklayer-mcp": {
      "url": "https://hooklayer.dev/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

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

VS Code

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

VS Code configuration

{
  "servers": {
    "hooklayer-mcp": {
      "type": "http",
      "url": "https://hooklayer.dev/api/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 hooklayer-mcp https://hooklayer.dev/api/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": {
    "hooklayer-mcp": {
      "url": "https://hooklayer.dev/api/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": {
    "hooklayer-mcp": {
      "serverUrl": "https://hooklayer.dev/api/mcp"
    }
  }
}

See all 782

Do you run Hooklayer 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