Sylgeo MCP Server
Check your brand's AI visibility across ChatGPT, Claude, Gemini & Perplexity — right from your coding workflow.
Sylgeo MCP is a Model Context Protocol server that gives AI coding assistants access to Sylgeo's Generative Engine Optimization (GEO) tools. Ask your assistant to scan your brand, analyze your website, compare competitors, and get actionable recommendations — all without leaving your editor.
Quick Start
1. Get Your API Key
Sign up and grab your key at sylgeo.com/dashboard/api-keys.
2. Install in Your AI Assistant
Claude Code
claude mcp add sylgeo-mcp -- uvx sylgeo-mcp
Then set your API key:
export SYLGEO_API_KEY="your-api-key-here"
Cursor
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"sylgeo": {
"command": "uvx",
"args": ["sylgeo-mcp"],
"env": {
"SYLGEO_API_KEY": "your-api-key-here"
}
}
}
}
Windsurf
Add to your Windsurf MCP config:
{
"mcpServers": {
"sylgeo": {
"command": "uvx",
"args": ["sylgeo-mcp"],
"env": {
"SYLGEO_API_KEY": "your-api-key-here"
}
}
}
}
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"sylgeo": {
"command": "uvx",
"args": ["sylgeo-mcp"],
"env": {
"SYLGEO_API_KEY": "your-api-key-here"
}
}
}
}
Available Tools
All tools require a valid SYLGEO_API_KEY.
| Tool | Description |
|---|---|
scan_brand_visibility |
Run a full AI visibility scan across ChatGPT, Claude, Gemini & Perplexity. Returns mention rates, rankings, and sentiment. |
check_visibility_score |
Get current GEO and AEO visibility scores with per-model breakdown. |
analyze_website_geo |
Analyze a website's GEO readiness — robots.txt, schema markup, content structure. |
get_geo_recommendations |
Get prioritized action items with estimated impact scores. |
compare_competitors |
Compare your AI visibility against tracked competitors. |
get_scan_history |
View historical scan data and score trends over time. |
get_tracked_prompts |
List the AI search prompts being tracked for your domain. |
Prompt Templates
| Prompt | Description |
|---|---|
geo_audit |
Full GEO audit — analyze website, run scan, check scores, provide recommendations. |
competitor_analysis |
Competitive AI visibility analysis with gap identification. |
content_optimization |
Content analysis with specific optimization recommendations. |
Resources
| URI | Description |
|---|---|
sylgeo://docs/getting-started |
Getting started guide |
sylgeo://docs/what-is-geo |
What is GEO (Generative Engine Optimization)? |
Example Usage
Once installed, just ask your AI assistant:
"Scan the AI visibility for my domain example.com"
The assistant will call scan_brand_visibility and then check_visibility_score to show your results.
"How does my site compare to competitors?"
The assistant will call compare_competitors and present a comparison table.
"Run a full GEO audit for example.com"
Using the geo_audit prompt template, the assistant will walk through a complete audit:
- Analyze website GEO readiness
- Run a visibility scan
- Check scores
- Provide recommendations
"What prompts are being tracked for my domain?"
The assistant will call get_tracked_prompts to show which AI search queries are being monitored.
Configuration
| Environment Variable | Required | Description |
|---|---|---|
SYLGEO_API_KEY |
Yes | Your Sylgeo API key (get one here) |
SYLGEO_API_URL |
No | Override the API base URL (default: https://api.sylgeo.com) |
Development
# Clone the repo
git clone https://github.com/sylgeo/sylgeo-mcp.git
cd sylgeo-mcp
# Install in development mode
pip install -e ".[dev]"
# Run the server locally
SYLGEO_API_KEY="your-key" python -m sylgeo_mcp.server
Testing with MCP Inspector
npx @modelcontextprotocol/inspector uvx sylgeo-mcp
What is GEO?
Generative Engine Optimization (GEO) is the practice of optimizing your brand's content to appear in AI-generated answers — the responses from ChatGPT, Claude, Gemini, Perplexity, and other LLM-powered search tools.
Traditional SEO focuses on Google's blue links. GEO focuses on getting your brand mentioned, recommended, and cited by AI assistants.
Learn more → sylgeo.com
License
MIT — see LICENSE for details.
Metadata
Release files for sylgeo-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sylgeo_mcp-0.1.0.tar.gz | 8.6 kB | With provenance | Details for sylgeo_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sylgeo_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sylgeo_mcp-0.1.0-py3-none-any.whl |
Total release size: 19.0 kB
Release files / sylgeo_mcp-0.1.0.tar.gz
| Download URL | sylgeo_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b4dbc50b2aa5f703aef3f40e121351dfaec13320da7e7a9d086c992b3a19494
|
|
BLAKE2b-256 checksum How to use checksums |
1d8ebd0e7372e5501fbf30e02f0095108757d5a22adc529eb3bbfbd6559ec658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.
Transparency logRelease files / sylgeo_mcp-0.1.0-py3-none-any.whl
| Download URL | sylgeo_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98d668ae79cf0a765a6a8ae0a7de26f946f7693d2f7e9ca78740669aaa4b6f2d
|
|
BLAKE2b-256 checksum How to use checksums |
7eca9592dc245cc65546016cfd839466d9ae8b735a5766a30aa64031b775eb12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.
Transparency logSecurity for sylgeo-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sylgeo_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.