Kumpay AEO MCP
Live SEO data for AI agents: SERP competition, keywords, backlinks, site audits, AI visibility.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http kumpay-aeo-mcp 'https://mcp.kumpaytech.com/mcp' --header 'Authorization: <Your per-buyer API key, sent as: Bearer sk_mcp_... (request a key from Kumpay Tech)>'
{
"mcpServers": {
"kumpay-aeo-mcp": {
"type": "http",
"url": "https://mcp.kumpaytech.com/mcp",
"headers": {
"Authorization": "<Your per-buyer API key, sent as: Bearer sk_mcp_... (request a key from Kumpay Tech)>"
}
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Kumpay AEO MCP
Remote MCP server that gives AI agents live SEO data: SERP competition analysis, keyword research, backlink profiles, full site audits, and AI-search visibility scoring — via 7 metered MCP tools.
By Kumpay Tech — the team behind Kumpay AEO, the AI visibility audit tool.
How it works
- MCP endpoint (Streamable HTTP):
POST /mcp - Buyers authenticate with a per-buyer key:
Authorization: Bearer sk_mcp_... - The upstream provider key lives only in this server's env — never sent to buyers.
- Every tool call is metered into a SQLite ledger (buyer, tool, credits).
Quick start (local)
git clone https://github.com/kumpayinteractive-sudo/kumpay-aeo-mcp
cd kumpay-aeo-mcp
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
cp .env.example .env # fill in SERPSLING_AUTH_KEY, ADMIN_TOKEN, KEY_PEPPER
# create a buyer key
.venv/bin/python -m app.store create-key --name "test-buyer"
# run
.venv/bin/uvicorn app.server:app --port 8080
Connect an MCP client to http://localhost:8080/mcp with header
Authorization: Bearer <key>.
Tools (v1)
| Tool | Cost |
|---|---|
keyword_research | 0 credits |
competition_analysis | 10 credits flat |
backlink_analysis | 10 credits flat |
site_audit | 1 credit / page (default 20, max 100) |
ai_visibility_audit | 0 credits |
get_analysis_status | free |
locations | free |
Costs are the values measured live against the upstream provider on 2026-10-12.
Buyer key management
python -m app.store create-key --name "acme" # prints key once
python -m app.store list-keys
python -m app.store revoke --name "acme"
python -m app.store usage --name "acme"
Admin
GET /health→{"ok": true}GET /admin/usage?token=...→ credit usage per buyer/toolGET /admin/buyers?token=...→ buyer list
Deploy (Coolify)
Separate service from the Whop app. Uses the included Dockerfile
(port 8080). Required env: SERPSLING_AUTH_KEY, ADMIN_TOKEN,
KEY_PEPPER. Needs a real domain + HTTPS before pointing buyers at it.
Persist /app/data (SQLite) with a volume.
Questions fréquentes
Qu'est-ce que Kumpay AEO MCP ?
Live SEO data for AI agents: SERP competition, keywords, backlinks, site audits, AI visibility.
Comment installer Kumpay AEO MCP ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http kumpay-aeo-mcp 'https://mcp.kumpaytech.com/mcp' --header 'Authorization: <Your per-buyer API key, sent as: Bearer sk_mcp_... (request a key from Kumpay Tech)>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Kumpay AEO MCP ?
Oui. Il attend Authorization, à renseigner dans sa configuration.
Kumpay AEO MCP est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Kumpay AEO MCP ?
Il est publié par kumpayinteractive-sudo. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.