Connectez SEO Agent avec ChatGPT & Claude Desktop
Utilisez notre API MCP pour vérifier le SEO, suivre les classements et écrire du contenu optimisé directement depuis votre chat IA préféré - ChatGPT, Claude, ou tout outil compatible MCP.
Aucun jeton, aucun copier-coller — collez une seule URL dans Claude Desktop et validez dans votre navigateur.
Qu'est-ce que MCP (Model Context Protocol) ?
MCP est un protocole standard qui permet aux assistants IA comme ChatGPT et Claude de se connecter à des outils et services externes.
Avec notre intégration MCP, vous pouvez accéder à vos données SEO, vérifier les classements, analyser les mots-clés et générer du contenu optimisé - tout cela depuis votre chat IA.
Intégration directe Claude Desktop
Support MCP officiel intégré
Compatible avec ChatGPT
Via des actions personnalisées
Authentification sécurisée
Avec clés API
Accès aux données en temps réel
Pas de code requis pour la configuration de base
Plateformes de Chat supportées
Claude Desktop
- Support MCP officiel intégré
- Ajoutez notre serveur MCP dans les paramètres
- Commencez à discuter avec les données SEO instantanément
ChatGPT Custom Actions
- Créez un GPT personnalisé avec notre API
- Configurez des actions pour accéder aux données SEO
- Utilisez dans ChatGPT Plus ou Team
Cursor, Windsurf, Zed & more
- Any MCP-compatible client
- OAuth 2.0 auto-registration
- Single-URL setup
Guide d'installation - Étape par étape
Connecter Claude Desktop (OAuth — sans clé API)
- 1Open Claude Desktop Settings → Developer → Edit Config
- 2Paste the configuration below — no API key needed
- 3Restart Claude Desktop. It will open your browser to approve the connection, then log you in automatically.
- 4Done — you can now ask Claude about your SEO data.
{
"mcpServers": {
"seo-ai-agent": {
"url": "https://seo-agent.net/api/mcp"
}
}
}C'est terminé — autorisez une fois dans votre navigateur
On first use Claude Desktop will open a tab on seo-agent.net, ask you to approve the connection, and redirect back automatically. After that, every MCP call is handled by the access token Claude received — no further action needed.
Outils/Fonctions MCP disponibles
19 tools across 7 categories — all workspace-scoped and OAuth-authenticated.
| Category | Nom de la fonction | Description | Exemple de requête |
|---|---|---|---|
| Profile | get_profile | Return the authenticated user profile (name, email, picture). | "Who am I signed in as?" |
| Profile | get_current_workspace | Return info about the workspace the current credentials are bound to. | "Which workspace am I in right now?" |
| Domains | list_domains | List all domains in the active workspace. | "Show me all my domains." |
| GSC | get_domain_insight | Get aggregated GSC stats (clicks, impressions, CTR, position), top keywords, pages and countries. | "How is example.com performing in Google in the last 30 days?" |
| GSC | get_domain_keywords | GSC keyword breakdown by query/device/country for the last N days. | "Top queries for example.com by country last month." |
| Tracking | list_tracked_keywords | List manually-tracked rank keywords for a domain. | "What keywords am I tracking for example.com?" |
| Tracking | add_tracked_keyword | Add a keyword to the rank tracker for a domain. | "Start tracking "ai seo tools" on example.com." |
| Competitors | list_domain_competitors | List competitor domains configured for a given domain. | "Who are my competitors for example.com?" |
| Competitors | update_domain_competitors | Replace the competitor list for a domain. | "Set competitors for example.com to ahrefs.com and semrush.com." |
| Competitors | get_keyword_competitors | Current competitor ranking positions for a specific tracked keyword. | "Who ranks near me for "seo ai tools"?" |
| Competitors | get_competitor_history | Time-series ranking history for competitors on a keyword. | "How has competitor.com ranked for "seo ai" over time?" |
| Research | get_domain_seo_overview | Domain-level SEO health: clicks, impressions, CTR, position + period-over-period change. | "Give me a 30-day SEO summary for example.com." |
| Research | find_keyword_opportunities | Quick-win buckets: striking distance, low CTR, zero-click, rising keywords. | "Find keyword opportunities for example.com." |
| Research | generate_content_brief | Full content brief for a new article: primary/secondary keywords, target word count, suggested structure, internal link candidates. | "Build a content brief for "best ai seo tools" on example.com." |
| Posts | list_posts | List articles/posts in a domain (draft, published, scheduled). | "Show all my draft posts for example.com." |
| Posts | get_post | Fetch a single post with full HTML content and metadata. | "Show me post #42." |
| Posts | analyze_seo | Run the built-in analyzer on article content (20+ on-page checks, 0-100 score, actionable fixes). | "Analyze this draft for SEO." |
| Posts | save_post | Create or update a post. Automatically computes the SEO score and returns both the saved post and the full analyzer report. | "Save this article as a draft and tell me the SEO score." |
| Posts | delete_post | Delete a post by ID. | "Delete post #42." |
Pourquoi utiliser l'intégration MCP ?
Vitesse & Efficacité
- Obtenez des infos SEO en quelques secondes
- Pas besoin de basculer entre les outils
- Requêtes en langage naturel
Infos propulsées par IA
- Laissez l'IA analyser vos données
- Obtenez des recommandations automatiquement
- Générez du contenu à la volée
Sécurisé & Privé
- Vos données restent sécurisées
- Clés API avec permissions spécifiques
- Journaux d'audit pour toutes les actions
Mises à jour continues
- Utilisez toujours les dernières données
- Vérifications de classement en temps réel
- Synchro auto avec GSC
Questions Fréquemment Posées
No. The server supports OAuth 2.0 Dynamic Client Registration (RFC 7591) and the MCP 2025-06-18 auth spec. You paste a single URL (/api/mcp) into your AI client — it auto-registers, opens your browser for approval, and gets its own access token. Nothing to copy, nothing to manage.
Your AI client first hits /api/mcp and receives HTTP 401 with a WWW-Authenticate header. It discovers the authorization server at /.well-known/oauth-authorization-server, registers a client at /api/oauth/register, then runs the Authorization Code + PKCE flow at /api/oauth/authorize. You approve once on the consent screen, it receives a code, exchanges it for an access_token + refresh_token at /api/oauth/token, and the MCP session is live.
The workspace that is active at the moment you approve the connection. You can switch workspaces from the sidebar, then reconnect your assistant — it will be bound to the new workspace. You can also revoke any connection any time from /profile/oauth-apps.
Yes. Each team member runs the same OAuth flow under their own account — they each get a personal access token scoped to the workspaces they are a member of, with the role (owner / admin / editor / viewer) they have in each. Owners and admins can revoke any teammate connection from the Connected Apps page.
read:profile (your user info + current workspace), read:domains / write:domains, read:gsc (GSC aggregates), read:keywords / write:keywords (rank tracker), and read:analytics. Your AI client only asks for what it needs — the consent screen shows you exactly which scopes you are granting before you approve.
All 19 tools listed in the "Available MCP Tools" table above: profile + workspace info, domains, GSC insights + keywords, rank tracker with competitors, content research (SEO overview, keyword opportunities, content briefs), posts CRUD, and a built-in SEO analyzer that scores articles 0-100 across 20+ on-page factors.
Access tokens are short-lived (1 hour) and refreshed automatically. All tokens are sha256-hashed in the database — we never store them in plain text. Every sync triggered via MCP is logged in gsc_sync_log with the source (mcp / oauth / web) so you have a full audit trail. Revoking a connection invalidates every token it holds immediately.
Yes. Go to /profile/oauth-apps → Developer section → Register an App. You will receive a client_id (and client_secret for confidential clients). Your app can then redirect users to /api/oauth/authorize with "Sign in with SEO AI Agent" — they approve, and your backend exchanges the code for an access token bound to their workspace.
Prêt à booster votre flux de travail SEO ?
Commencez à utiliser MCP pour automatiser vos tâches SEO avec l'IA
Rejoignez 1 000+ utilisateurs automatisant le SEO avec MCP