mcp-gsc MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

20 tools across properties, analytics, URL inspection, sitemaps
Compare periods: week-over-week, query/page/country breakdowns
URL inspection for indexing and crawl issues
OAuth or service account — fits solo or team setups

라이브 데모

실제 사용 모습

gsc.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "gsc",
      "command": "uvx",
      "args": [
        "mcp-gsc"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "gsc": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-gsc"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add gsc -- uvx mcp-gsc

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: mcp-gsc

Generate a weekly SEO report with mcp-gsc

👤 SEO managers, content teams ⏱ ~15 min beginner

언제 쓸까: Monday morning — you want last week's performance summary before standup.

사전 조건

GSC access to the property — search.google.com/search-console
OAuth credentials or service account — console.cloud.google.com — enable Search Console API

흐름

Pull top queries + deltas

For acme.com, top 20 queries last week vs the previous week. Show clicks, CTR, position deltas.✓ 복사됨

→ Delta table
Pull top landing pages movers

Top 10 pages with the biggest clicks changes (up or down).✓ 복사됨

→ Winners + losers list
Draft the summary

Write a 5-bullet summary for the team meeting, with an action item for the biggest loser.✓ 복사됨

→ Ready-to-paste report

결과: Monday report in 10 minutes.

함께 쓰기: google-sheets

Audit indexing issues across your site

👤 Technical SEOs ⏱ ~30 min intermediate

언제 쓸까: Traffic dipped and you want to know if Google is still indexing what it should.

흐름

Sample top pages

From top 50 landing pages last month, inspect each URL's indexing status via inspect_url_enhanced.✓ 복사됨

→ Per-URL status: indexed/crawled-not-indexed/excluded
Cluster issues

Group by issue type. For 'crawled but not indexed', what's the common pattern?✓ 복사됨

→ Diagnosis by cluster

결과: Prioritized fix list tied to real GSC verdicts.

Verify sitemap health and submission status

👤 Anyone launching new pages ⏱ ~10 min beginner

언제 쓸까: You just launched new pages — check Google picked up the sitemap.

흐름

List sitemaps

get_sitemaps for acme.com. Show last-read dates and error counts.✓ 복사됨

→ Sitemap health list
Resubmit stale ones

For sitemaps not read in 7 days, resubmit.✓ 복사됨

→ Submitted

결과: Confidence that Google sees the new content.

Mine GSC for ranking opportunities

👤 Growth-stage SEOs ⏱ ~40 min intermediate

언제 쓸까: You want queries where you rank 11-20 and are close to page 1.

흐름

Find near-miss queries

Queries last 90 days with avg position between 11 and 20 AND >100 impressions. Return with the landing page.✓ 복사됨

→ Target list
Prioritize by effort

For top 20, check the landing page — is it already optimized for the query? If not, suggest on-page changes.✓ 복사됨

→ Effort-weighted opportunity list

결과: A prioritized SEO backlog grounded in your real GSC data.

함께 쓰기: firecrawl

조합

다른 MCP와 조합해 10배 효율

gsc + google-sheets

Automated weekly SEO report dropped into a shared sheet

Every Monday, run my weekly SEO report and append to 'SEO Weekly' sheet.✓ 복사됨

gsc + firecrawl

Scrape competitor pages ranking for your target queries

For each near-miss query in GSC, find the top SERP pages (via firecrawl), and summarize why they outrank me.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
list_properties		Discover what you have access to	1 API call
get_search_analytics	site, start_date, end_date, dimensions[], filters?, row_limit?	The workhorse query	1 API call
inspect_url_enhanced	site, url	Per-URL indexing debug	1 API call
get_sitemaps	site	Sitemap health	1 API call
submit_sitemap	site, feedpath	Nudge Google to recrawl	1 API call

비용 및 제한

운영 비용

API 쿼터: GSC API: 1200 QPM per project, 6000 QPD per site
호출당 토큰: Analytics results up to 25k rows per call — chunk before dumping
금액: Free
팁: Use row_limit and filters; dumping top-10k queries ruins context for agents

보안

권한, 시크릿, 파급범위

최소 스코프: https://www.googleapis.com/auth/webmasters.readonly

자격 증명 저장: GSC_OAUTH_CLIENT_SECRETS_FILE or GSC_CREDENTIALS_PATH in env

데이터 외부 송신: searchconsole.googleapis.com

절대 부여 금지: webmasters (full)

문제 해결

자주 발생하는 오류와 해결

403 User does not have permission

OAuth'd account or service account must be verified user in GSC for that property. Add under Settings → Users

Empty analytics response

GSC has 2-3 day data lag; end_date > today - 3 may be empty. Also: 'Web' vs 'Discover' search types differ

OAuth flow loops

Redirect URI in client_secrets.json must match exactly (including http://localhost port)

대안

mcp-gsc 다른 것과 비교

대안	언제 쓰나	단점/장점
GSC web UI	Ad hoc manual work	No automation, no reporting loop
Ahrefs/SEMrush APIs	You want third-party rank tracking, not Google's own data	Paid; different dataset

mcp-gsc