timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Plug apps, sites and HTML pages into CloudGrid and get a live URL, with databases and AI built in.
教 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)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 CloudGrid。按照 https://mcp.popnx.com/i/cloudgrid-io-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.cloudgrid.io) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
CloudGridhttps://mcp.cloudgrid.io/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsCloudGrid
用 CloudGrid 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 CloudGrid,或回答中出现 CloudGrid 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
CloudGridhttps://mcp.cloudgrid.io/mcp开启新聊天,输入前先从插件列表中选择 CloudGrid
用 CloudGrid 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 CloudGrid,或回答中出现 CloudGrid 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user cloudgrid-io https://mcp.cloudgrid.io/mcp应能看到 CloudGrid 在列表中并显示已连接
用 CloudGrid 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 CloudGrid,或回答中出现 CloudGrid 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 CloudGrid 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 CloudGrid,或回答中出现 CloudGrid 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 CloudGrid 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 CloudGrid,或回答中出现 CloudGrid 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.cloudgrid.io/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user cloudgrid-io https://mcp.cloudgrid.io/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"cloudgrid-io": {
"url": "https://mcp.cloudgrid.io/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"cloudgrid-io": {
"type": "http",
"url": "https://mcp.cloudgrid.io/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 cloudgrid-io 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
在 295 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/cloudgrid-io-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于5天前,最新版本(0.22.7)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Official changedetection.io MCP: web page change tracking, back-in-stock and price alerts.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use
Let your AI agent operate any website through a real, logged-in browser session.
| 本项 CloudGrid | Browser Use | changedetection.io (official) | Apify MCP Server | Pomerado | Actionbook | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 是 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 5/5 | 3/3 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | Apache-2.0 | MIT | MIT | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server for CloudGrid. It exposes the CloudGrid actions as MCP tools.
Add this URL to your AI tool as a remote MCP server (in claude.ai and ChatGPT, add it as a custom connector):
https://mcp.cloudgrid.io/mcp
Sign in to CloudGrid when your AI tool asks; the connection uses OAuth. There is nothing to install and nothing to configure. The hosted server carries the tools that call the CloudGrid API directly. How it works and how it is hosted: REMOTE.md.
The local edition runs on your machine over stdio and adds the tools that wrap the grid CLI (logs, rollbacks, env vars, secrets, scaffolding). Use it in Claude Code, Cursor or Claude Desktop when you build runtime apps from a folder on disk.
Install and sign in to the CLI:
npm install -g @cloudgrid-io/cli
grid login
Then point your MCP client at:
npx -y @cloudgrid-io/mcp
The server reads no credentials of its own. It uses the CLI's stored sign-in at ~/.cloudgrid/credentials; grid_login writes the same file.
Add either the hosted server or the local server to a given client, not both. With both, each grid_* tool appears twice and the two hold separate sign-in state, so they can disagree about whether you are signed in. To check, look for duplicate grid_* entries in the client's tool list, or two CloudGrid servers in its MCP or connector settings. Keep the local server where you build runtime apps from folders, and the hosted server in chat-only clients.
All optional:
CLOUDGRID_TELEMETRY=off: turns off grid_report error reports.HTTPS_PROXY, HTTP_PROXY, NO_PROXY: route API calls through a proxy.NODE_EXTRA_CA_CERTS=/path/to/root-ca.pem: trust an extra root certificate, for networks that inspect TLS.GRID_AUTH_STALE is out of scope: grids whose owner enforces SSO can return it when your session predates an SSO policy change. The server does not retry; sign in again through Console SSO.
38 tools registered (15 shared across both editions, 23 local-only). No deprecated aliases. MIN_CLI_VERSION: 0.15.26.
| Tool | Wraps | Summary |
|---|---|---|
grid_pickup | API | Pick up an app: copies any app the user can see into one of their grids as a NEW, separate entity (a fork, like a git... |
grid_pull | API | Pull an app to continue or edit it IN PLACE, like git clone of the SAME entity: the next plug with its target_entit... |
grid_collab | API | Collab: grants the signed-in user PUSH ACCESS to the SAME live entity that someone else owns, as a collaborator on th... |
grid_create_grid | API | Create a new grid (the workspace the user's apps live in) for the signed-in user, who becomes its admin. |
grid_note | API | Record a one-paragraph summary of what was built this session and why, for the local edition's optional QA session lo... |
grid_plug | API | Plug an app, website, game, or HTML page into CloudGrid at a live public URL. |
grid_get_app_source | API | Retrieve the CURRENT deployed HTML of an inspiration/drop inline as text, for editing and re-plugging the SAME URL wh... |
grid_visibility | API | Change who can see a CloudGrid inspiration OR runtime app/agent. |
grid_check_deploy | API | Check whether an async runtime-app build (a deploy, which here means a plug) has finished and the app is live. |
grid_list_grids | API | List the signed-in user's grids, each with slug, name, role, whether it is the active grid, and setup status (render_... |
grid_start | API | A short orientation for building with CloudGrid: the account this session is signed in as and its active grid, how to... |
grid_get_template | corpus | Load a specific CloudGrid workflow, template, example, rule, troubleshooting note, or reference doc by kind and name:... |
grid_report | API | Report a genuine CloudGrid failure (a build, deploy, or platform call that failed unexpectedly) to the CloudGrid team... |
grid_hello | API | Create a minimal hello page and plug it into the user's grid, returning the live URL. |
grid_delete | grid delete entity | Archive a CloudGrid inspiration. |
The direct-API tools call the platform without the CLI, so they also work in the web edition. grid_login writes the same ~/.cloudgrid/credentials the CLI uses, so the two share one identity.
| Tool | Wraps | Summary |
|---|---|---|
grid_login | API | Start a CLI-free CloudGrid sign-in. |
grid_login_status | API | Finish a browser sign-in started from this server. |
grid_create_project | grid new | Scaffold a new CloudGrid app or agent folder (cloudgrid.yaml + a web service), optionally pre-declaring resources. |
grid_view_logs | grid logs | Tail recent logs for an entity. |
grid_share | grid visibility set | Set an entity's visibility and print its URL. |
grid_feedback | grid feedback list | List recent feedback events for the active grid. |
grid_whoami | grid whoami | Show the signed-in user and active grid. |
grid_switch_grid | grid use | Switch the active grid. |
grid_logout | grid logout | Sign out and clear local credentials. |
grid_status | grid status | Grid dashboard, entity detail, or deploy snapshot. |
grid_info | grid info | Show metadata for a CloudGrid entity. |
grid_get | grid get --json | List CloudGrid grids, entities, or spaces. |
grid_describe_grid | grid describe grid --json | Show a grid's detail: role, members, spaces, tier, wildcard-TLS state. |
grid_edit_existing_app | grid pull | Continue/edit an EXISTING entity locally: downloads its source + cloudgrid.yaml and links the folder so the next `gri... |
grid_rename | grid rename | Rename a CloudGrid entity's display name (slug stays the same). |
grid_take_offline | grid unplug | Take an entity off the grid. |
grid_rollback_deploy | grid rollback | Rollback an entity to a previous version. |
grid_list_versions | grid versions | List published versions for an entity. |
grid_set_env | grid env | Manage environment variables for an entity. |
grid_set_secret | grid secrets | Set or list secret names for an entity. |
grid_scaffold | grid scaffold | Scaffold service folders declared in cloudgrid.yaml (idempotent). |
grid_diagnose | grid doctor | Run CloudGrid diagnostics on the local environment. |
grid_get_url | grid open --print | Return the public URL for an entity. |
grid_share and grid_visibility overlap on purpose: grid_share wraps the CLI and defaults to link; grid_visibility is direct API, takes an explicit scope, and defaults its target to the session's last drop — it is the one the web edition gets.
All tools carry MCP annotations (readOnlyHint, destructiveHint, openWorldHint) for clients that support them.
Full policy: https://cloudgrid.io/privacy
Authentication. grid_login opens a browser-based Google sign-in flow via CloudGrid's API (/auth/login). The returned JWT is stored at ~/.cloudgrid/credentials with 0600 permissions — the CLI and the MCP share one credential file by design (auth.js:7-8). The web edition has no sign-in tool: the AI tool's connector signs in with OAuth, and this server issues its own short-lived access token, with the CloudGrid session sealed inside it, so the session is never handed to the AI tool.
Deploying. grid_plug uploads your app files (HTML, source, assets) to https://api.cloudgrid.io/api/v2/plug. Before upload, inline sources are scanned for known API-key patterns (OpenRouter, Anthropic, OpenAI, Google, GitHub, AWS, Slack, Stripe); a match blocks the deploy. This is not a guarantee — a determined model can obfuscate a key past the scan — but it stops the good-faith "embed it so it works" path. Auth headers (Bearer JWT, grid slug) are attached to identify the caller.
Error reporting. grid_report sends an error report to https://api.cloudgrid.io/api/v2/errors. The tool description instructs the model to call it only with the user's explicit consent, and setting CLOUDGRID_TELEMETRY=off disables it unconditionally — but there is no programmatic consent check in the report handler itself. The payload includes an error summary, diagnostic metadata (platform, Node version, transport), a flag recording whether the user agreed to share the conversation (deploy.js:544), and a context object the model supplies — which by its declared shape (register.js:964-975) can carry the failing inputs (for example the HTML or args) and the original request. The transcript itself is not sent by this tool. The report scrub is two-layer: values AND the message field are scanned for known secret shapes (API key prefixes such as sk-ant-, sk-proj-, AKIA…; JWTs; PEM private-key blocks; Bearer tokens; basic-auth URL credentials) and matches are replaced with [REDACTED]. Arbitrary or unknown-shape secrets that do not match a known pattern still transit unredacted. The client-side scrub (scrubReportContext + scrubSecretValues in deploy.js) runs before the POST; the server endpoint applies a server-side key-name filter on top. To keep a secret out of a report, do not place it in the message or context you send, or set CLOUDGRID_TELEMETRY=off to disable reporting entirely.
Version check. At startup the local edition makes one request to https://registry.npmjs.org/@cloudgrid-io/mcp/latest to detect a stale .mcpb install, which never auto-updates. It sends no account data and no user content. The hosted edition does not do this.
QA session log. Off by default. The local (stdio) server posts a per-session QA log to the CloudGrid team only on a machine where a maintainer has turned it on (see CONTRIBUTING.md); a user never sets it. When on, it posts on deploy, error, idle timeout, or process shutdown. The log includes: session metadata (user ID, email, grid slug, client name), the user's first message (scrubbed, capped at 2 000 chars), a per-tool-call trail with allowlisted arg keys only, and an optional narrative set via grid_note or grid_plug's session_note (capped at 4 000 chars). The first message is captured from the CLOUDGRID_USER_REQUEST environment variable (forwarded by Claude Code) or grid_plug's user_request argument (local edition only). The hosted edition sends nothing on its own: its grid_plug has no user_request or session_note, and there is no post on a plug, on idle, or on close. The one hosted post is grid_note, which the user asks for: it POSTs the note to the CloudGrid API (/api/v2/feedback) under the user's own sign-in, with the grid slug and the client name — no email address, no tool-call trail, nothing else from the conversation; signed out, it returns needs_auth and sends nothing. grid_report (both editions) sends a failure report to the CloudGrid API only after the user agrees: the message and context the model passes plus the client name and platform, and the conversation only when they explicitly agree to that. Free-text values (the first message, the narrative, tool arguments, and error messages) pass through a scrubber that redacts JWTs, PEM keys, Bearer tokens, and known provider API-key formats. Identity fields (_keyResult values and the header block) and structured result data bypass the text scrubber.
No other data collection by this server. The server does not track usage analytics or transmit data beyond the flows listed above and the authenticated CloudGrid API calls the individual tools make (e.g. /grids, /pickup, /deploys, /inspirations/{id}/source). CLI-wrapping tools shell out to the Clo