SISTRIX SEO Toolbox

sistrix-mcp

Talk to your SISTRIX SEO data. From Claude, Cursor, VS Code, or any MCP client.

*17 curated, credit-aware SEO tools + a full-API escape hatch. Single binary, instant startup, context-friendly.*

Quickstart · Clients · Tools · Credits · Configuration · FAQ

---

You  ▸ How is example.com doing in Google — and who is beating us?

Claude ▸ example.com's visibility index is 4.82 (Germany), up 6% over the last 8 weeks. It ranks for 18,400 organic keywords, 2,100 in the top 10. Closest SEO competitors: competitor-a.de (74% overlap), competitor-b.com (61%). Biggest opportunity: 312 keywords sit on page 2 — want the top 20 by potential gain?

Every question the SISTRIX Toolbox can answer, your AI assistant can now answer too — including follow-ups, comparisons, and "why?".

✨ Why sistrix-mcp?

🚀 Quickstart

1. Install

Prebuilt binary (Linux, macOS, Windows) — grab it from Releases, or:

# Cargo

cargo install sistrix-mcp

From source

cargo install --git https://github.com/Liohtml/sistrix-mcp

Docker

docker pull ghcr.io/liohtml/sistrix-mcp

2. Get a SISTRIX API key

app.sistrix.com/account/api → create a key. API access is included from the Plus package onwards and uses a weekly credit budget.

3. Verify the connection

sistrix-mcp --api-key YOUR_KEY --check

✓ Connected — 10000 API credits available

4. Connect your client ⬇

🔌 Connect your client

Claude Code

claude mcp add sistrix \

--env SISTRIX_API_KEY=YOUR_KEY \ --env SISTRIX_COUNTRY=de \ -- sistrix-mcp

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{

"mcpServers": { "sistrix": { "command": "sistrix-mcp", "env": { "SISTRIX_API_KEY": "YOUR_KEY", "SISTRIX_COUNTRY": "de" } } } }

Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{

"mcpServers": { "sistrix": { "command": "sistrix-mcp", "env": { "SISTRIX_API_KEY": "YOUR_KEY", "SISTRIX_COUNTRY": "de" } } } }

VS Code (GitHub Copilot)

.vscode/mcp.json:

{

"servers": { "sistrix": { "type": "stdio", "command": "sistrix-mcp", "env": { "SISTRIX_API_KEY": "${input:sistrix-key}", "SISTRIX_COUNTRY": "de" } } }, "inputs": [ { "id": "sistrix-key", "type": "promptString", "description": "SISTRIX API key", "password": true } ] }

Windsurf / Zed / other MCP clients

Any client that speaks MCP over stdio works with the generic shape:

{

"command": "sistrix-mcp", "args": [], "env": { "SISTRIX_API_KEY": "YOUR_KEY", "SISTRIX_COUNTRY": "de" } }

Docker (any client)

{

"mcpServers": { "sistrix": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SISTRIX_API_KEY", "-e", "SISTRIX_COUNTRY", "ghcr.io/liohtml/sistrix-mcp" ], "env": { "SISTRIX_API_KEY": "YOUR_KEY", "SISTRIX_COUNTRY": "de" } } } }

[!TIP]

Set SISTRIX_COUNTRY (e.g. de) and every tool call automatically uses that

country index unless the model asks for another one.

🧭 Tools

*Costs as documented by SISTRIX per method; see API credits.

Domain tools accept a target (the domain, host, path, or URL) plus a scope that tells SISTRIX how to interpret it, a country index, and a row limit.

Guided workflows (MCP prompts)

Four ready-made analysis workflows ship as MCP prompts — clients like Claude surface them as one-click commands. Each runs a proven, credit-aware tool sequence and ends in a structured report:

Prompts to try

• *"Give me an SEO health check for example.com in Germany."*
• *"Which keywords sit on positions 11–20 with the most traffic potential?"*
• *"Compare our visibility trend with competitor-a.de over the last 12 months."*
• *"Does ChatGPT recommend our brand? Which sources does it cite in our niche?"*
• *"What's the search intent and CPC for our top 10 money keywords?"*

💳 API credits

SISTRIX API access starts with the Plus package and uses a weekly credit budget. Most methods cost 1 credit per returned row; a few are flat-rate (domain.overview = 5, domain.visibilityindex.overview = 10, links.overview = 25) and keyword.seo.metrics costs 5 per keyword.

sistrix-mcp defaults every list to 25 rows (not SISTRIX's 100–10,000) and tells the model what each call costs, so exploratory conversations stay cheap. Check the balance anytime with sistrix_credits — it's free, as are sistrix_lists and the project/tracker list reports.

The rate limit is 300 requests/minute; sistrix-mcp backs off and retries automatically when it's hit.

⚙️ Configuration

🆚 How is this different from SISTRIX's official MCP integration?

SISTRIX documents its own MCP bridge for connecting chatbots to the API — and per their docs, requests through it currently don't count against the credit quota. If that covers your needs, use it!

sistrix-mcp is the open-source, self-hosted alternative: a local stdio binary with a curated, fully documented tool surface (17 tools with exact schemas, enums, and per-case validation), an escape hatch to every documented API method including the newest areas (ai.check, marketplace, Optimizer onpage), hard response budgets for the model's context, offline tests, and no dependency on a hosted bridge. MIT-licensed, so you can read exactly what the model can and cannot do with your API key.

🩺 Troubleshooting

"wrong api key" (code 100)

Run sistrix-mcp --api-key ... --check. If it fails, regenerate the key under app.sistrix.com/account/api.

"not enough credits" (code 200)

The weekly budget is exhausted. Credits refill weekly; check the balance with sistrix_credits. Keep limit small — most tools cost 1 credit per row.

</d