timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Google Search Console: 37 tools, every API endpoint, hourly data, history beyond 16 months.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 6/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 13/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Google Search Console。按照 https://mcp.popnx.com/i/mamrrez-gsc-mcp-full.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Google Search Console,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "gsc-full": { "command": "uvx", "args": [ "gsc-mcp-full" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Google Search Console 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"gsc-full": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}用 Google Search Console 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Google Search Console,或回答中出现 Google Search Console 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Google Search Console
Google Search Console 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Google Search Console,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user gsc-full -- uvx gsc-mcp-full 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Google Search Console 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user gsc-full -- uvx gsc-mcp-full应能看到 Google Search Console 在列表中并显示已连接
用 Google Search Console 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Google Search Console,或回答中出现 Google Search Console 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Google Search Console,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "gsc-full": { "command": "uvx", "args": [ "gsc-mcp-full" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Google Search Console 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Google Search Console 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Google Search Console,或回答中出现 Google Search Console 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Google Search Console,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "gsc-full": { "type": "stdio", "command": "uvx", "args": [ "gsc-mcp-full" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Google Search Console 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Google Search Console 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Google Search Console,或回答中出现 Google Search Console 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user gsc-full -- uvx gsc-mcp-fullClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"gsc-full": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"gsc-full": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"gsc-full": {
"type": "stdio",
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 mamrrez 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 gsc-mcp-full@0.2.2 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mamrrez-gsc-mcp-full)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.2.2)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Google Search Console | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The complete MCP server for Google Search Console. Ask Claude, Cursor, Windsurf, VS Code, Codex or any other MCP client about your search performance, indexing and sitemaps in plain language — and get analysis back, not a spreadsheet.
37 tools · every Search Console API endpoint · the 24-hour view and hourly data · history beyond 16 months · correct numbers in every language.
[Quick start](#quick-start) · [Tools](#tools) · [Languages](#languages) · [FAQ](#faq) · [Full docs](https://mamrrez.github.io/gsc-mcp-full/) · [Project page](https://hasanpour.com/tools/gsc-mcp-full/)
| ✅ Complete | All 10 live methods of the Search Console API, all 6 search types (web, image, video, news, Discover, Google News), all 7 dimensions including hourly, with contains, exact, exclude and regex filters. Nothing in the API is left out. |
| ⚡ Fast | Starts in under a second. Inspects up to 10 URLs in parallel, 50 per request, inside a time budget so a big batch never times out your client. Retries rate limits and server errors on its own. Groups 25,000 queries in about half a second. Questions about synced history never touch the network. |
| 🔄 Current | Built on MCP SDK 2.x. API coverage checked against Google's own API definition (October 2026). Mirrors the Performance report's newest options: the 24-hour view with preliminary data, and hourly, daily, weekly or monthly granularity. Tested on Linux, macOS and Windows with Python 3.10–3.13 on every change. |
| 🧠 Answers, not exports | Cannibalization, striking-distance keywords, under-performing titles, decaying pages, brand vs non-brand — worked out for you and returned as short tables your AI can reason about. |
| 🌍 Right in every language | Search Console splits one keyword into several rows when it is typed several ways. This server merges them — Persian, Arabic, Chinese, Japanese, Korean, Turkish, Vietnamese, Russian and more — so the totals are the real ones. |
| 🗄️ No 16-month limit | Sync your data into a local file once; compare this quarter with the same quarter two years ago, long after Google has deleted it. |
| 🕒 Your timezone | Search Console days are Pacific-Time days. Hourly data is re-cut into *your* local days. |
| 🎯 Numbers you can trust | Header totals are the real period totals, not a sum of the rows shown. Page URLs are never shortened, so they can be passed straight to the next tool. A failure is reported as an error with its reason, never as an empty result. Covered by 117 automated tests on Linux, macOS and Windows, and checked end to end against real properties. |
| 🔒 Safe by default | Read-only access unless you opt in. Runs on your machine; your sign-in never leaves it. No hosted service, no account, no telemetry. |
| 💸 Free and light | MIT licensed. Four dependencies. One command to run. |
Works with: Claude Desktop · Claude Code · Cursor · Windsurf · VS Code (Copilot agent mode) · OpenAI Codex CLI · any MCP client over stdio or HTTP.
37 tools in 8 groups. You don't call them yourself — ask in plain language and your AI picks the right one.
🌍 merges spelling variants · 🗄️ can run on local history (any date range) · ✍️ needs write access (GSC_ALLOW_WRITE=1)
| Tool | What it gives you | Ask it like this |
|---|---|---|
performance_overview | One-screen summary: totals, a daily, weekly or monthly trend, top queries and pages, devices, countries, data freshness | *"How did example.com do in the last 6 months, month by month?"* |
query_search_analytics 🌍 | Any report you can build in Search Console: every dimension, search type and filter, with a query filter that also matches a term's other spellings | *"Top mobile queries from Germany containing 'klima' last month"* |
compare_periods 🌍 | Two periods side by side with the biggest movers first — previous period, same dates last year, 52 weeks ago, or custom dates | *"Compare this month with the same month last year"* |
queries_for_page 🌍 | Every query that brings traffic to one page | *"What do people search to land on /pricing/?"* |
pages_for_query 🌍 | Which pages rank for one keyword and how impressions split between them | *"Which of my pages rank for 'air conditioner installation'?"* |
hourly_performance | Search Console's 24-hour view, and hour-by-hour data for the last 10 days in your own timezone | *"Show the last 24 hours"* · *"Show last week as Tehran days"* |
data_freshness | Which recent days and hours are final and which are still preliminary | *"Is yesterday's data complete yet?"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
striking_distance 🌍🗄️ | Keywords ranking 8–20 with real demand, and the clicks you'd gain on page one | *"What are my quickest ranking wins?"* |
find_cannibalization 🌍🗄️ | Keywords where two or more of your pages compete as separate results (sitelinks and #section links are not counted as competitors), ranked by wasted impressions | *"Where are my pages competing with each other?"* |
low_ctr_opportunities 🌍🗄️ | Page-one results whose click-through rate is far below what their position should earn | *"Which titles should I rewrite first?"* |
content_movers 🌍🗄️ | Pages or queries that decayed, rose, disappeared or appeared since the last period | *"Which pages lost traffic this month?"* |
brand_split 🌍🗄️ | Brand vs non-brand traffic, with your brand matched in every script it's written in | *"How much of my traffic is non-brand?"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
query_variants 🗄️ | Keywords that Search Console splits across spellings, with their real combined totals | *"Which keywords are split across spellings?"* |
language_breakdown 🗄️ | Share of clicks and impressions by the language and script of the query | *"How much of my traffic is Arabic vs English?"* |
keyboard_mistypes 🗄️ | Queries typed with the keyboard on the wrong layout (ovdn lhadk = «خرید ماشین») | *"Find searches typed on the wrong keyboard"* |
top_terms 🗄️ | Most demanded words across all queries — including Chinese, Japanese and Thai, which have no spaces | *"What words appear most in my Japanese queries?"* |
build_query_regex | A regex filter that works for non-English text, for the API or the Search Console UI | *"Give me a regex for خرید خودرو that matches every spelling"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
sync_history | Copies your data into a local database, day by day, past Google's 16 months and row caps | *"Sync the last 16 months of example.com"* |
history_status | What's stored: date range, days and rows per property | *"What history do I have saved?"* |
history_query 🌍 | Any report over any stored date range | *"Top queries for all of 2025"* |
history_trend 🌍 | Clicks, impressions, CTR and position per day, week or month | *"Monthly clicks for 'heat pump' over two years"* |
history_compare 🌍 | Two stored periods against each other, however far apart | *"Q3 this year vs Q3 two years ago"* |
history_sql | Your own read-only SQL against the stored data | *"Run this SQL on my history: …"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
inspect_url | Full inspection of one page: index status, last crawl, canonical, robots, sitemaps, rich results | *"Is /new-article/ indexed? What canonical did Google pick?"* |
inspect_urls | Up to 50 pages inspected in parallel, as one table with separate index and rich-result verdicts | *"Inspect these 30 URLs"* |
indexing_summary | Problems only: which pages are not indexed or fail structured data, and why | *"Which of these pages have indexing issues?"* |
inspection_quota | How much of Google's daily inspection allowance is used | *"How many inspections do I have left today?"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
list_sitemaps | Every submitted sitemap with URL counts, errors and warnings | *"List my sitemaps and their errors"* |
get_sitemap | Details of one sitemap | *"When did Google last read sitemap.xml?"* |
submit_sitemap ✍️ | Submit or resubmit a sitemap | *"Submit example.com/sitemap.xml"* |
delete_sitemap ✍️ | Remove a sitemap from Search Console | *"Remove the old sitemap"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
list_properties | Every property your account can see, with your permission level | *"List my Search Console properties"* |
get_property | Details of one property — accepts example.com as well as the exact property URL | *"Do I own example.com in Search Console?"* |
add_property ✍️ | Add a site to your account | *"Add newsite.com to Search Console"* |
remove_property ✍️ | Remove a site from your account | *"Remove the old staging property"* |
| Tool | What it gives you | Ask it like this |
|---|---|---|
get_capabilities | Sign-in status, access level, stored history and the tool list | *"Is Search Console connected?"* |
reauthenticate | Sign in again to switch Google accounts | *"Switch to my other Google account"* |
Every parameter of every tool: Tool reference.
Three steps, about ten minutes, no cost. You need a Google account with access to Search Console.
Google requires every app that reads Search Console to identify itself, so you create a free "OAuth client" once.
~/gsc/client_secret.json.Using a service account instead (servers, scheduled jobs, teams)
No browser sign-in is needed with a service account; skip the auth command in ste