GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Website monitoring: uptime alerts, page speed and Core Web Vitals with the next fix, cron check-ins.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.heynimo.com/mcp-server在终端中运行这条命令
claude mcp add --transport http nimo https://api.heynimo.com/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"nimo": {
"url": "https://api.heynimo.com/mcp-server"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"nimo": {
"type": "http",
"url": "https://api.heynimo.com/mcp-server"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.heynimo.com/mcp-server菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 marvtub 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于27天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Hear it from nimo, not your customers. When a page gets slow, checkout breaks or a backup doesn't run, nimo tells you first, in plain words, with the fix.
Ask your AI assistant "is my site up?", "why did my homepage get slower?" or "did last night's backup run?" and get an answer from real checks, not a guess.
nimo checks that your site loads every 5 minutes, double-checks before it alerts you, and messages you in Slack or Telegram when it goes down and again when it's back. It also tracks how fast your key pages load (Core Web Vitals, from real Chrome visitors when available, plus Lighthouse), and watches scheduled jobs such as backups and cron jobs. This MCP server gives Claude, ChatGPT, Cursor, Codex and other assistants access to all of it.
https://api.heynimo.com/mcp-server
Hosted, remote (streamable HTTP), nothing to install. You sign in with your browser; no API key needed.
In your assistant: connect https://api.heynimo.com/try-mcp and ask "What is slowing down https://example.com?"
In your terminal (Node 18+, nothing to install):
$ npx github:marvtub/nimo-mcp#v1.0.1 https://heynimo.com
Checking...
nimo check: https://heynimo.com (mobile)
Performance score 87 needs work Largest paint (LCP) 3.5 s needs work Layout shift (CLS) 0 good Server response (TTFB) 5 ms good
LCP is above the good threshold and Lighthouse identified a text LCP element. No image resource was identified for this element. [...]
Watch this page every 5 minutes with alerts in Slack or Telegram: https://heynimo.com
Add --min-score 70 to exit with an error when a page gets slow, or --json for scripts. Free checks have hourly and daily limits.
Without #v1.0.1, npx github:marvtub/nimo-mcp follows the default main branch rather than a fixed release. Cached installs may need refreshing to receive newer code.
| What it's for | |
|---|---|
| Setup for your assistant | Connect nimo to Claude, ChatGPT, Cursor, Codex, Windsurf or VS Code |
nimo-check CLI | One free speed check from the terminal or any CI |
| GitHub Action | Check the live site after every deploy, result in the run summary |
| Claude skill | Teaches Claude to check uptime and speed after you ship |
| Cron and backup examples | crontab, Postgres backup, GitHub Actions schedule, Kubernetes CronJob, Node |
| Guides | Know when a cron job didn't run, check your site after a deploy |
Claude Code
claude mcp add --transport http --scope user nimo https://api.heynimo.com/mcp-server
claude mcp login nimo
Claude (desktop and web)
Settings → Connectors → Add custom connector → paste https://api.heynimo.com/mcp-server, then approve the sign-in.
ChatGPT
Add a connector with the URL https://api.heynimo.com/mcp-server (Settings → Apps & Connectors; custom connectors need developer mode on some plans), then approve the sign-in.
Codex
codex mcp add nimo --url https://api.heynimo.com/mcp-server
Cursor
Use the Add to Cursor button above, or add to ~/.cursor/mcp.json:
{
"mcpServers": { "nimo": { "url": "https://api.heynimo.com/mcp-server" } } }
Windsurf
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "nimo": { "serverUrl": "https://api.heynimo.com/mcp-server" } } }
VS Code
Use the Install button above, or:
code --add-mcp '{"name":"nimo","type":"http","url":"https://api.heynimo.com/mcp-server"}'
Clients that only run local (stdio) servers
Bridge to the hosted server with mcp-remote:
{
"mcpServers": { "nimo": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.heynimo.com/mcp-server"] } } }
Use an API key instead of signing in
Only if your client can't sign in with a browser. Create a key in nimo under Settings → API keys (it starts with nimo_), keep it in your client's secret store, and send it as Authorization: Bearer . Never commit it.
on: deployment_status
jobs: check: if: github.event.deployment_status.state == 'success' runs-on: ubuntu-latest steps:
The score, LCP, layout shift, server response and the fix to make first show up in the run summary, and as the outputs score, lcp-ms, cls and ttfb-ms. Free, no key or secret. Full example: examples/github-actions/check-after-deploy.yml.
The existing @v1 tag stays on its original release; it does not receive this patch automatically. Update your workflow to @v1.0.1 to opt in, or pin the full release commit SHA for an immutable code reference.
mkdir -p ~/.claude/skills/check-site-after-deploy
curl -fsSL https://raw.githubusercontent.com/marvtub/nimo-mcp/main/skills/check-site-after-deploy/SKILL.md \ -o ~/.claude/skills/check-site-after-deploy/SKILL.md
Then tell Claude "I just deployed" and it checks uptime, measures the changed pages again and compares them with the last check before the deploy.
Ask "watch my nightly backup", and add the ping URL you get to the end of the job:
0 3 * * * /usr/local/bin/backup.sh && curl -fsS https://api.heynimo.com/ping/<your-token>
If the ping doesn't arrive on time, nimo alerts you. Copy-paste versions for crontab, a Postgres backup, GitHub Actions, Kubernetes and Node.
Uptime and scheduled jobs
| Tool | What it does |
|---|---|
get_uptime_status | Latest check, response time, uptime over 24 hours and 30 days, any ongoing outage |
add_check_in | Watch a cron job, backup or other scheduled job; alerts when it stops running |
list_check_ins | List watched jobs and whether each has checked in |
get_check_in | Confirm a job's first check-in arrived |
remove_check_in | Stop watching a job |
Sites and speed
| Tool | What it does |
|---|---|
list_sites | Every site with its latest Core Web Vitals |
get_site | One site's latest metrics, settings and uptime |
add_site | Save a site for repeat checks |
list_watched_pages | Watched pages, check schedule and latest reports |
audit_url | One-off speed and page check of any public URL |
run_audit / get_audit_status | Measure a saved site again and wait for the result |
get_audit_report | What is slowing a page down and what to fix first |
get_audit_history | Past results, to spot a trend or regression |
compare_audits | Before and after a change |
audit_all_sites | Rank every site's latest result, regressions first |
share_report | Make an expiring link to share a report |
Search and analytics
| Tool | What it does |
|---|---|
get_seo_evidence | Indexing, robots, canonical and search evidence for a page |
get_search_coverage | Pages without search impressions, duplicates, and the best next action |
connect_posthog / get_posthog_connection_status / get_posthog_analytics | Connect PostHog and read site traffic |
list_ga4_properties / select_ga4_property | Connect Google Analytics 4 |
Journey Watch (a browser agent that checks sign-up, checkout and other flows on a schedule)
list_journeys, create_journey, get_journey, update_journey, pause_journey, resume_journey, run_journey, get_journey_run, list_journey_credentials.
Load fewer tools with a profile, for example https://api.heynimo.com/mcp-server?profile=monitoring (watched pages and uptime), ?profile=optimize (speed and SEO), ?profile=integrations or ?profile=journeys.
https://api.heynimo.com/try-mcp: check_website, get_check, compare_checks. One-off speed checks of public pages, with shared hourly and daily limits.
https://api.heynimo.com/docs-mcp: list_docs, search_docs, read_doc, read_llms_full. Read-only nimo documentation.
Checking a page once is free and needs no signup. Watching sites (uptime every 5 minutes, speed checks, alerts, MCP access) is part of nimo Pro: $20 a month for up to 10 sites. Business is $199 a month for 50 sites. See heynimo.com.
只显示了开头部分;其余内容请在仓库中阅读