Supabase
by supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Computer or cloud★ 2,993Apache-2.0Updated today
Install
ImmyBot MCP
Overview
Description from the maker (original English)
Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Databases & datasets
- You need to fill in: IMMYBOT_CLIENT_ID, IMMYBOT_CLIENT_SECRET, IMMYBOT_SUBDOMAIN, IMMYBOT_TENANT_ID, IMMYBOT_MCP_HTTP_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
IMMYBOT_BASE_URL,IMMYBOT_CLIENT_ID,IMMYBOT_CLIENT_SECRET,IMMYBOT_SUBDOMAIN,IMMYBOT_TENANT_ID,IMMYBOT_TOKEN_URL,IMMYBOT_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE,IMMYBOT_NO_CONFIG_WRITE,IMMYBOT_MCP_READ_ONLY,IMMYBOT_NO_LOCAL_DATA,IMMYBOT_MCP_HTTP_TOKEN,IMMYBOT_MCP_UPLOAD_ROOT
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
IMMYBOT_BASE_URLenvFull API base URL. Leave blank: the CLI builds it from IMMYBOT_SUBDOMAIN. Set it only to point at a different host.- Set the IMMYBOT_CLIENT_ID credential for the ImmyBot MCP server.
- Set the IMMYBOT_CLIENT_SECRET credential for the ImmyBot MCP server.
- Set the IMMYBOT_SUBDOMAIN credential for the ImmyBot MCP server.
- Set the IMMYBOT_TENANT_ID credential for the ImmyBot MCP server.
IMMYBOT_TOKEN_URLenvToken endpoint the client-credentials exchange posts to. Leave the prefilled default unless your tenant uses a different token endpoint.IMMYBOT_USER_AGENTenvOverrides the User-Agent the CLI sends on ImmyBot requests. Leave blank to use the CLI's own built-in User-Agent.PRINTING_PRESS_CLIENT_PROFILEenvBinds this MCP server to one tenant-gated client profile, so every call answers for that customer. Leave blank to use the profile configured as default_client_profile.IMMYBOT_NO_CONFIG_WRITEenvSet to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml. Leave blank for the default cached behavio…IMMYBOT_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.IMMYBOT_NO_LOCAL_DATAenvOptional. Set to 1 to save no API data locally: sync and workflow archive are refused and the response cache is off.- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
IMMYBOT_MCP_UPLOAD_ROOTenvOptional. Has no effect: this release's MCP server refuses every upload and never opens a local path. Run uploads with immybot-cli.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Databases & datasetsi
- More stars than 0% of the other 954 servers in this category
- Published to the registry more recently than 96% of the other 954 servers in this category
- Basic checks equal to or better than 100% of the other 954 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is ImmyBot MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: IMMYBOT_CLIENT_ID, IMMYBOT_CLIENT_SECRET, IMMYBOT_SUBDOMAIN, IMMYBOT_TENANT_ID, IMMYBOT_MCP_HTTP_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.12) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MongoDB MCP Server
by mongodb-js
MongoDB Model Context Protocol Server
Runs on your computer★ 1,157Apache-2.0Updated 2 days ago
Install
Elasticsearch MCP Server
by cr7258
MCP server for interacting with Elasticsearch
Runs on your computer★ 315Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
ImmyBot + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the ImmyBot
API. Not affiliated with, endorsed by, or sponsored by ImmyBot, LLC..
Full skill page - install, outcomes, safety model.
Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions the web UI cannot. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the ImmyBot skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register immybot-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add immybot-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add immybot-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs immybot-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionimmybot-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setIMMYBOT_CLI_PATHto an existing binary). Details: #331.
Download ImmyBot MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ImmyBot release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills/plugin install immybot@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ImmyBot Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iex. Then authenticate per the README and runimmybot-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh)The installer drops both immybot-cli (the CLI) and immybot-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
immybot-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update immybot@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/immybot --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/immybot --forceHermes speaks MCP natively, so it can also use the immybot-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the immybot skill from https://github.com/servosity/msp-skills/tree/main/skills/immybot. The skill defines how its required CLI (
immybot-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your ImmyBot portal):
export IMMYBOT_SUBDOMAIN=acme # the "acme" in acme.immy.botexport IMMYBOT_TENANT_ID= export IMMYBOT_CLIENT_ID= export IMMYBOT_CLIENT_SECRET= immybot-cli doctor
ImmyBot issues no API key of its own. You register an app in Microsoft Entra ID, create a client secret, then add that Enterprise Application's object ID as an admin person inside ImmyBot (Show More > People > New > AD External ID). IMMYBOT_SUBDOMAIN is required: it derives the OAuth scope, and without it the token request falls back to a scope naming your own app registration and Entra rejects it.
doctor checks config, paths, and API reachability, then verifies the credential itself with one authenticated read against /auth/me: it reports valid, invalid (HTTP 401), or scope-limited (HTTP 403). It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| What failed in last night's maintenance window, and why? | immybot-cli session-triage --since 24h |
| Which tenants are still behind on Chrome? | immybot-cli version-spread "Google Chrome" --min-version 140 |
| Why did this machine never get the deployment? | immybot-cli assignment-explain 4821 |
| What actually changed in the fleet since last night? | immybot-cli fleet-diff --snapshot once, then immybot-cli fleet-diff --since 24h |
| Which computers are stuck part-way through onboarding? | immybot-cli onboarding-stalled --older-than 3d |
| What does this shared script reach before I edit it? | immybot-cli script-blast-radius "Install Chrome" |
| Which deployments have never once succeeded? | immybot-cli deployment-health --only-failing |
| Which computers are in ImmyBot but missing from my PSA? | immybot-cli psa-reconcile |
| What is this one machine's full history in one view? | immybot-cli computer-dossier WS-01 |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most ImmyBot integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking which of your 40 clients are still running a Chrome build below 140, because that is one API call per tenant per title and ImmyBot keeps no history to compare against.
This skill syncs ImmyBot into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like session-triage, version-spread and assignment-explain join across maintenance sessions, actions, computers, tenants, software inventory and target assignments - work a stateless API wrapper can't do.
The pain this closes
ImmyBot's own community threads and the r/msp deployment discussions circle the same shape: the platform is excellent at putting software on machines and unhelpful the morning after. A maintenance window runs across hundreds of endpoints, a slice of it fails, and the console shows you the same error text once per machine with no grouping, no root cause, and no way to ask "is this one broken package or forty broken agents?". The neighbouring questions are worse, because they are cross-tenant: which clients are still below a version floor, why one machine did not match a deployment when its neighbour did, and what changed overnight. ImmyBot keeps no history to diff against, so the honest answer today is a spreadsheet.
- `session-triage --since 24h` - collapses a night of failed actions into distinct root causes, so you read the failure once instead of forty times.
- `version-spread "Google Chrome" --min-version 140` -
Only the beginning is shown; read the rest in the repo