About glippy-mcp
GEO (Generative Engine Optimization) analysis: check any domain's AI-readiness for LLM search
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y glippy-mcpGLIPPY_LICENSE_KEYSecretYour Glippy MCP license key (GLMCP-XXXX-XXXX-XXXX)GLIPPY_RATE_LIMITMax requests per second per domain for batch tools (default 5)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
10Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| domain | string | Yes | The domain to analyse, e.g. "example.com". Do not include https:// prefix. |
| max_pages | integer | No | Maximum pages to crawl (1 = homepage only, up to 10 for multi-page analysis). Defaults to 10. |
| render_mode | enum | No | How to fetch HTML. "static" (fast, plain Node fetch) is default for this tool. "auto" tries static first and falls back to a local headless Chrome for bot-blocked responses (401/403/407/429/503 or empty 2xx). "chrome" always renders via Chrome. Chrome modes need a local Chrome binary (CHROME_PATH) or an attached instance (CHROME_REMOTE_URL).static | chrome | auto |
| output_format | enum | No | Output format. "text" (default) returns a human-readable report. "json" returns the raw analysis result object that can be passed to export_report's analysis_result parameter.text | json |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.