ClayHog MCP Server

The ClayHog MCP server connects AI assistants like Claude, Cursor, and Windsurf to your ClayHog account. Once connected, you can ask plain-language questions about your AI search visibility, compare competitors, research topics, and create content without leaving the chat.

MCP (Model Context Protocol) is an open standard that lets AI tools securely call external data and actions. The ClayHog server exposes your brands, scouts, competitors, citations, and content as tools your assistant can use.

What you need

• A ClayHog account with at least one brand. Start free if you do not have one yet.
• An AI tool that supports MCP, such as Claude, Cursor, VS Code, or Windsurf.
• A personal access token, which you generate in Settings > Access Tokens in the ClayHog app.

Option 1: Hosted server (recommended)

The hosted server is the fastest way to connect. It uses OAuth, so you sign in once and your token is never passed through tool arguments. Add this to your AI tool’s MCP config:

{
  "mcpServers": {
    "clayhog": {
      "url": "https://mcp.clayhog.com/mcp"
    }
  }
}

The first time your assistant calls a ClayHog tool, it will prompt you to sign in and authorize access.

Option 2: Run it locally

You can also run the server on your own machine with npx. Set your credentials as environment variables in the MCP client config:

{
  "mcpServers": {
    "clayhog": {
      "command": "npx",
      "args": ["-y", "clayhog-mcp"],
      "env": {
        "CLAYHOG_API_URL": "https://api.clayhog.com",
        "CLAYHOG_API_TOKEN": "your-token",
        "CLAYHOG_TENANT_ID": "your-tenant-id"
      }
    }
  }
}

Variable	Description
CLAYHOG_API_URL	ClayHog backend URL (https://api.clayhog.com)
CLAYHOG_API_TOKEN	Personal access token from Settings > Access Tokens
CLAYHOG_TENANT_ID	Your tenant ID

If you prefer to authenticate inside the conversation, you can omit the token and tenant ID and call the connect tool instead. Note that some MCP hosts log tool arguments, so environment variables are the safer choice.

Where to add the config

The setup is the same idea in every tool, only the config file location changes.

• Cursor: add the server to .cursor/mcp.json in your project, or to your global MCP settings.
• Claude Desktop: add it to claude_desktop_config.json (Settings > Developer > Edit Config).
• VS Code and Windsurf: add it to the MCP settings for the editor’s AI assistant.

After saving, restart the assistant so it picks up the new server.

What you can do

Once connected, you can ask your assistant to work across your whole ClayHog account:

• Brand visibility: visibility scores, analytics, and trends across ChatGPT, Gemini, Perplexity, Claude, and Google AI Overviews.
• Competitor analysis: rankings, share of voice, and side-by-side comparisons.
• Prompts and scouts: list, create, and schedule the prompts you track.
• Responses and citations: full AI responses with the domains and sources they cite.
• Topic research: related topics, People Also Ask questions, and SERP competitive gaps.
• Content and GEO: draft, optimize, translate, and analyze content for AI search.
• Domain authority: authority scores, backlinks, and keyword rankings.

A few examples to try:

• “What is my brand visibility on ChatGPT this week?”
• “Which competitors gained share of voice on Perplexity this month?”
• “Show me the domains AI models cite most for my topics.”
• “Draft a weekly AI visibility report for my brand.”

Workflow templates

The server ships with ready-made workflows you can pick from your assistant’s prompt picker:

• Weekly Visibility Report: analytics, competitive standings, and citation sources in one report.
• Content Pipeline: pick a prompt, outline it, create the content, then run a GEO analysis.
• Competitive Snapshot: competitive analysis across every AI platform.
• Topic Research: research a topic for content opportunities and competitive gaps.
• Set Up a New Brand: create a brand, add competitors, generate prompts, and start a scout.

Troubleshooting

Message	What it means	What to do
Authentication failed	Invalid or expired token	Generate a new token in Settings > Access Tokens and reconnect
Access denied	Token lacks permissions	Generate a new token with full access
This feature requires a plan upgrade	Not available on your plan	Upgrade in your ClayHog billing settings
Not found	Wrong ID or missing resource	Verify the brand, scout, or prompt ID with the matching list tool
Not connected	No credentials provided	Use the hosted URL, set environment variables, or call the connect tool

Next steps

• Add and manage prompts
• Set up competitive analysis
• Connect a CMS integration

Still stuck? Contact our support team and we will help you get connected.