InhouseSEO MCP Connector for Claude

Last updated: April 13, 2026

The InhouseSEO MCP connector lets Claude read your real Google Search Console data, run SEO analysis workflows, audit pages, plan content, and update your SEO task list — all through natural conversation. This page is the canonical reference for installing, authenticating, and using the connector.

InhouseSEO is developed by IWD Holding BV and is not affiliated with or endorsed by Anthropic. “Claude” is a trademark of Anthropic, PBC. The connector implements the open Model Context Protocol and is listed in the Claude connector directory.

---

What this connector does

InhouseSEO is an SEO platform built on top of Google Search Console. The MCP connector exposes 18 tools that let Claude:

• Read GSC performance data (clicks, impressions, position, CTR) at the site, page, and keyword level
• Inspect technical SEO health: titles, H1s, meta descriptions, schema, response time, internal-link structure, sitemap drift
• Render any page with a real headless browser to see what users and Google actually see
• Find quick-win keywords (low CTR vs. expected, page-2 rankings with high impressions)
• Detect content decay, traffic declines, and ranking changes
• Run pre-built analytical workflows (page audits, weekly reports, content briefs, competitor intelligence, etc.)
• Read and update your business context, SEO goals, and task list

Because the data comes straight from your connected Google Search Console properties, every answer is grounded in your real traffic — not a generic SEO opinion.

---

Compatible with

• Claude.ai (web) — full support, OAuth handled in-browser
• Claude Desktop (macOS, Windows) — full support, OAuth handled in-browser
• Claude Code — full support, connects directly from your machine
• Claude mobile apps — full support

You need an active InhouseSEO account on the Pro or Max plan, with at least one Google Search Console property connected.

---

Install (Claude.ai web)

1. Open Claude.ai and go to Settings → Connectors.
2. Click Add custom connector.
3. Paste the InhouseSEO MCP server URL:

   https://app.inhouseseo.ai/api/mcp

4. Click Connect. You’ll be redirected to InhouseSEO to log in.
5. Sign in with your InhouseSEO account.
6. On the consent screen, review the requested scopes and click Allow.
7. You’ll be redirected back to Claude.ai. The connector is now active in every conversation.

That’s it. No API keys, no copy-paste tokens. Authorization is OAuth 2.0 with PKCE.

Install (Claude Desktop)

The flow is identical — open Settings → Connectors → Add custom connector, paste https://app.inhouseseo.ai/api/mcp, and complete the OAuth flow in your default browser.

Install (Claude Code)

claude mcp add --transport http inhouseseo https://app.inhouseseo.ai/api/mcp

The first time you use a tool, Claude Code will open the OAuth flow in your browser.

---

Authentication

The connector implements OAuth 2.0 authorization code flow with PKCE, fully compliant with the MCP spec.

• Issuer: https://app.inhouseseo.ai
• Authorization endpoint: https://app.inhouseseo.ai/api/auth/mcp/authorize
• Token endpoint: https://app.inhouseseo.ai/api/auth/mcp/token
• Dynamic client registration: https://app.inhouseseo.ai/api/auth/mcp/register (RFC 7591 — no pre-allowlist required)
• Discovery: https://app.inhouseseo.ai/.well-known/oauth-authorization-server
• Resource metadata: https://app.inhouseseo.ai/.well-known/oauth-protected-resource
• Scopes: openid profile email offline_access
• Grant types: authorization_code, refresh_token
• PKCE: S256 (required for public clients)
• Token lifetime: 24 hours (access token), 2 years (refresh token)

You can revoke access at any time from your InhouseSEO dashboard under Settings → Connected apps, or from your Claude client.

---

Tool reference

All 18 tools are scoped to a single GSC property at a time. The connector injects your default property automatically; pass a different property_id (e.g. sc-domain:example.com) to switch.

Read tools

Tool	What it does
list_properties	Lists every GSC property in your organization with default flag and last data date.
get_context	Returns the business profile: type, audience, goals, brand keywords, watched competitors.
get_plan	Returns your task list and goals with progress.
get_signals	Recent SEO alerts: traffic drops, ranking changes, content decay, technical issues, competitor moves.
get_performance	Site-level metrics. Modes: overview, comparison, insights, declines.
get_page	Per-page metrics: daily trend, top 50 queries, full crawl data (title, H1, meta, schema, response time, links).
get_keywords	Keyword data. Modes: lookup, search, opportunities, trending, clusters, cannibalization.
get_competitors	Competitor data. Modes: market, changes, gaps, serp.
get_site_health	Technical health, internal links, sitemap monitoring. Modes: full, technical, links, sitemap.
get_backlinks	Backlink profile, recently acquired/lost links, gap analysis. (Max plan only.)
get_onboarding_summary	One-call onboarding bundle: top 50 pages, ~120 enriched keywords, competitors.
get_research	Full SEO research playbook for a topic — linkbuilding tactics, content templates, conversion benchmarks.
render_page	Renders any URL with a headless browser and returns the full DOM as markdown — preferred over web fetch for accuracy.
start_workflow	Returns a complete framework (steps, tools, quality criteria) for a named workflow.

Write tools

Tool	What it does
update_context	Update business name, type, audience, tone, goals, brand keywords.
update_signals	Configure alert thresholds, delivery style, and channels.
update_tasks	Create, update, or change status of tasks and goals.
add_competitor	Add a competitor domain to the watch list.

Available workflows (start_workflow)

weekly-report, page-audit, competitor-intelligence, keyword-opportunities, cannibalization-check, content-brief, keyword-deep-dive, traffic-decline-recovery, compare-periods, top-movers, ranking-changes, content-decay, technical-health, index-coverage, internal-links, serp-features, linkbuilding, write-content, improve-content, expert-interview, onboarding-profile, onboarding-strategy, review-plan, refine-strategy.

Each workflow returns a structured plan that bundles the right tools, steps, and quality criteria for the task. Use start_workflow first whenever the user’s request matches one — it’s cheaper and more reliable than reconstructing the same flow from scratch.

---

Usage examples

Example 1 — Diagnose a traffic drop

You: My organic traffic dropped 30% last week. What happened?

What Claude does:

1. Calls get_signals to find recent decay/decline alerts.
2. Calls get_performance with type=declines to list the worst-affected pages.
3. Calls get_page on the top offender to inspect query-level changes and crawl status.

Expected output: A ranked list of declining pages, the queries each one lost, and a probable cause — e.g. “/pricing dropped from position 3 to position 11 for ‘inhouse seo’ starting April 4. The page is still indexable and unchanged; this looks like a competitor leapfrog rather than a technical regression.”

---

Example 2 — Find quick-win keywords

You: Show me keywords I’m ranking on page 2 that have high impressions but I’m not clicking on.

What Claude does:

1. Calls get_keywords with type=opportunities to find queries with low CTR vs. expected for their position.
2. Calls get_page for each ranking URL to fetch the current title, H1, and meta description.

Expected output: A table of opportunity keywords with current position, monthly impressions, expected vs. actual CTR, and a recommended title/meta rewrite for each. Claude will typically rank them by potential clicks gained.

---

Example 3 — Run a full page audit

You: Audit my pricing page and tell me what to fix.

What Claude does:

1. Calls start_workflow with workflow=page-audit and url=/pricing. The workflow returns a 7-dimension audit framework.
2. Calls get_page for GSC + crawl data.
3. Calls render_page to see the live rendered DOM.
4. Calls get_competitors (type=serp) to check what competitors are doing on the same query.
5. Synthesises everything into a prioritised audit.

Expected output: A structured audit covering technical issues, content quality, intent match, schema, internal links, conversion elements, and competitive gaps — ranked by impact.

---

Example 4 — Plan next quarter’s content

You: Based on my keyword clusters and competitor gaps, what should I write next quarter?

What Claude does:

1. Calls get_keywords with type=clusters for the hub-and-spoke structure.
2. Calls get_competitors with type=gaps for keywords competitors rank for that you don’t.
3. Calls get_context for business positioning, tone, and audience.

Expected output: A 12-week content plan with target clusters, primary keyword per piece, the competitive gap each piece closes, and a brief outline. Claude will typically also offer to convert the plan into tasks via update_tasks.

---

Example 5 — Update your task list (write example)

You: Mark the “Fix duplicate H1s” task as done and add a new task to write meta descriptions for my top 20 pages.

What Claude does:

1. Calls update_tasks with action=status to flip the existing task to done.
2. Calls update_tasks again with action=create to insert the new task with a derived priority.

Expected output: Confirmation message and the updated task list. This example demonstrates a write tool — Claude will ask you to confirm the change in your client before it executes.

---

Rate limits & quotas

• Per organization: 100 requests per minute across all tools.
• render_page: 60-second timeout per page; rendered through our managed headless browser cluster.
• get_backlinks: Live data fetched from DataForSEO on first use, then cached for 14 days. (Max plan only.)
• Tool result size: Capped at 80,000 characters (~20k tokens) per call to comply with the MCP directory’s 25k-token limit. If a result is truncated, Claude is told how to narrow the request — pass a smaller limit, a specific url, or a more targeted type.

---

Troubleshooting

“This tool requires approval in your MCP client” Open your Claude client → Settings → Connectors → InhouseSEO and enable all tools. Claude Desktop sometimes asks per-tool the first time you use it.

“Property not found” or “No properties connected” Reconnect Google Search Console from the InhouseSEO dashboard under Settings → Properties. Make sure the GSC account you authorized has at least one verified property.

OAuth loop / “Invalid client” Clear cookies for app.inhouseseo.ai, then reconnect from your Claude client. If you’re on a corporate network, check that your firewall isn’t stripping the Authorization header.

get_site_health returns crawl_pending Site crawls run in the background after signup and typically finish within 1–2 hours. Try again once your crawl is complete — you can check the status from the dashboard.

Token expired Access tokens last 24 hours. Refresh tokens last 2 years. Your client refreshes silently; if it can’t, just reauthorize from Claude → Settings → Connectors → InhouseSEO.

Something else Email hello@inhouseseo.ai — we usually respond within 24 hours.

---

Privacy & data

• The connector only sees data Claude explicitly queries during your conversation. We do not log prompts, tool arguments beyond what’s needed for the call, or Claude’s responses.
• All data is read from your own connected Google Search Console properties. We don’t share it with third parties beyond the subprocessors listed in our Privacy Policy.
• Anthropic processes the conversation under your existing Claude subscription terms; InhouseSEO is one of the subprocessors named in our policy.
• You can revoke the connector and delete your account at any time from the InhouseSEO dashboard. See the full Privacy Policy for retention periods, data subject rights, and subprocessor list.

---

Support

• Email: hello@inhouseseo.ai
• Contact form: inhouseseo.ai/contact
• Response time: within 24 hours, typically much faster during EU business hours
• Status: issues with the connector are flagged on our status channel; subscribe via the contact form.

---

Disclaimer

InhouseSEO is developed by IWD Holding BV (KVK 94864144, Utrecht, Netherlands) and is not affiliated with, sponsored by, or endorsed by Anthropic, PBC. “Claude” is a trademark of Anthropic. The connector implements the open Model Context Protocol and any Claude-compatible MCP client can connect to it.