SEO エージェントを ChatGPT & Claude Desktop と連携
MCP API を使用して、お気に入りの AI チャット（ChatGPT、Claude、または MCP 対応ツール）から直接、SEO チェック、順位追跡、最適化されたコンテンツの執筆が可能です。
トークンもコピーも不要 — Claude Desktop に URL を貼り付けてブラウザで承認するだけです。
MCP (Model Context Protocol) とは？
MCP は、ChatGPT や Claude などの AI アシスタントが外部のツールやサービスと接続できるようにする標準プロトコルです。
当社の MCP 統合により、AI チャット内から SEO データへのアクセス、順位の確認、キーワードの分析、最適化されたコンテンツの生成がすべて可能になります。
Claude Desktop との直接連携
公式 MCP サポートを標準装備
ChatGPT との互換性
カスタムアクション経由で利用可能
安全な認証
API キーによる認証に対応
リアルタイムデータアクセス
基本設定にコードは不要
サポートされているチャットプラットフォーム
推奨Claude Desktop
- 公式 MCP サポート内蔵
- 設定で当社の MCP サーバーを追加
- すぐに SEO データでのチャットを開始可能
高度な設定ChatGPT Custom Actions
- 当社 API を使用してカスタム GPT を作成
- SEO データにアクセスするためのアクションを構成
- ChatGPT Plus または Team で利用可能
Cursor, Windsurf, Zed & more
- Any MCP-compatible client
- OAuth 2.0 auto-registration
- Single-URL setup
セットアップガイド - ステップバイステップ
Claude Desktop を連携 (OAuth — 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"
}
}
}完了 — ブラウザで一度承認するだけです
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.
利用可能な MCP ツール/関数
19 tools across 7 categories — all workspace-scoped and OAuth-authenticated.
| Category | 関数名 | 説明 | クエリ例 |
|---|---|---|---|
| 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." |
なぜ MCP 連携を使用するのか？
スピードと効率
- 数秒で SEO インサイトを取得
- ツール間の切り替えが不要
- 自然言語でのクエリ
AI によるインサイト
- AI にデータを分析させる
- 自動的に推奨事項を取得
- その場でコンテンツを生成
安全とプライバシー
- データは安全に保持されます
- 特定の権限を持つ API キー
- すべての操作の監査ログ
継続的なアップデート
- 常に最新データを使用
- リアルタイムの順位チェック
- GSC との自動同期
よくある質問
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.