Getting Started

Get Glippy MCP Server running with your AI assistant in under 5 minutes.

Requirements

  • Node.js 18.0.0 or higher
  • An MCP-compatible AI client (Claude Code, Claude Desktop, Cursor, etc.)
  • A valid Glippy MCP license key

Installation

Option 1: Via npm (recommended)

npm install -g glippy-mcp

Option 2: Via npx (no install)

Use directly in your MCP configuration without installing globally:

npx -y glippy-mcp

License Key

A valid Glippy MCP license key (GLMCP-XXXX-XXXX-XXXX) is required. Get one at glippy.dev/mcp.

How licensing works

The server validates your key against the Glippy API on first use and caches the result for 24 hours. Analysis runs locally on your machine — only the license check calls our servers.

Quick Setup

Choose your AI environment and add the configuration:

Claude Code / Claude CLI

Create .mcp.json in your project root (or ~/.claude/.mcp.json for global):

{
  "mcpServers": {
    "glippy-geo": {
      "command": "npx",
      "args": ["-y", "glippy-mcp"],
      "env": {
        "GLIPPY_LICENSE_KEY": "GLMCP-XXXX-XXXX-XXXX"
      }
    }
  }
}

Claude Desktop

Edit your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "glippy-geo": {
      "command": "npx",
      "args": ["-y", "glippy-mcp"],
      "env": {
        "GLIPPY_LICENSE_KEY": "GLMCP-XXXX-XXXX-XXXX"
      }
    }
  }
}

Cursor IDE

Create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "glippy-geo": {
      "command": "npx",
      "args": ["-y", "glippy-mcp"],
      "env": {
        "GLIPPY_LICENSE_KEY": "GLMCP-XXXX-XXXX-XXXX"
      }
    }
  }
}
Restart required

After editing the configuration, restart your AI client for changes to take effect.

Verify Installation

In your AI client, check that the MCP server is connected:

Claude Code / Claude CLI

/mcp

You should see glippy-geo listed with its 9 tools.

Claude Desktop

Look for the MCP tools icon (hammer/wrench) in the interface. Click it to see available Glippy tools.

Your First Analysis

Try a simple analysis to confirm everything works:

Check if example.com has an llms.txt file

Or run a full GEO analysis:

Analyze example.com for AI readiness and show me the top 3 issues to fix

Allow-list GlippyBot on Your Own Site

If you're using the MCP server to audit a site you own, make sure your WAF or robots.txt isn't blocking the crawler. All Glippy products (MCP server, Desktop app, Chrome Extension) identify themselves with the GlippyBot user-agent.

User-agent: GlippyBot
Allow: /

Full User-Agent string, IP guidance, and WAF allow-list instructions are on the GlippyBot info page.

Next Steps

Explore Tools

Learn about all 9 GEO analysis tools and their parameters.

Tools reference

Integration Guides

Detailed setup for all supported AI environments.

View guides

GlippyBot Crawler Info

User-Agent string and allow-list guide for your WAF or robots.txt.

Allow-list GlippyBot

Environment Variables

Variable Required Default Description
GLIPPY_LICENSE_KEY Yes — Your MCP license key
GLIPPY_RATE_LIMIT No 5 Default requests/second per domain
CHROME_PATH No auto-detect Path to Chrome/Chromium binary. Required for render_mode: "auto" or "chrome" if auto-detection fails.
CHROME_REMOTE_URL No — Attach to a running Chrome (e.g. http://localhost:9222) instead of launching one. Useful for sites that fingerprint headless browsers. See Render Modes.
CHROME_HEADLESS No new Set to 0 or false to run launched Chrome visible.
CHROME_USER_DATA_DIR No — Chrome user-data directory for cookie / auth reuse.