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메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 marvtub 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 27일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 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.
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요