Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Gradient MSP MCP

by servosityversion 0.1.9i★ –iRuns on your computer
Registry nameio.github.Servosity/gradient-mcp

Install

Overview

Description from the maker (original English)

CLI and MCP server for Gradient MSP Synthesize: usage push, billing drift, alert tracing.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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: Other
  • You need to fill in: GRADIENT_PARTNER_API_KEY, GRADIENT_TOKEN, GRADIENT_VENDOR_API_KEY, PRINTING_PRESS_CLIENT_PROFILE, GRADIENT_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: GRADIENT_BASE_URL, GRADIENT_PARTNER_API_KEY, GRADIENT_TOKEN, GRADIENT_VENDOR_API_KEY, GRADIENT_MCP_READ_ONLY, GRADIENT_NO_LOCAL_DATA, GRADIENT_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, GRADIENT_MCP_HTTP_TOKEN

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

  • GRADIENT_BASE_URL env
    Base URL for the Gradient MSP API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
  • GRADIENT_PARTNER_API_KEY secret env
    Synthesize partner API key, issued with the vendor key. Fill in this and the vendor key, or GRADIENT_TOKEN alone.
  • GRADIENT_TOKEN secret env
    The GRADIENT-TOKEN header value, base64(" : "). Leave empty when you fill in the vendor and partner API keys; when set, it is used instead of them.
  • GRADIENT_VENDOR_API_KEY secret env
    Synthesize vendor API key (Integrations -> Custom -> Generate API Tokens). Fill in this and the partner key, or GRADIENT_TOKEN alone.
  • GRADIENT_MCP_READ_ONLY env
    Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call. Leave blank to keep every tool available.
  • GRADIENT_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API and nothing is written to the local store. Leave blank to keep the local store.
  • GRADIENT_USER_AGENT env
    Overrides the User-Agent the CLI sends on Gradient MSP requests. Leave blank to use the CLI's own built-in User-Agent.
  • PRINTING_PRESS_CLIENT_PROFILE secret env
    Only for tenant-gated multi-client deployments: binds the MCP server to an existing Printing Press client profile. Leave blank for a single-tenant install.
  • GRADIENT_MCP_HTTP_TOKEN secret env
    Required only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transpo…

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 6, 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 Otheri

  • More stars than 0% of the other 32433 servers in this category
  • Published to the registry more recently than 96% of the other 32433 servers in this category
  • Basic checks equal to or better than 100% of the other 32433 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 Gradient MSP 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: GRADIENT_PARTNER_API_KEY, GRADIENT_TOKEN, GRADIENT_VENDOR_API_KEY, PRINTING_PRESS_CLIENT_PROFILE, GRADIENT_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.9) 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: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
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.

Gradient MSP + 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 Gradient MSP

API. Not affiliated with, endorsed by, or sponsored by Gradient MSP, Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

The Gradient MSP Synthesize vendor API from your terminal: bulk usage pushes with a single billing rebuild, a local push-drift ledger, and alert-to-ticket tracing the portal and SDK don't offer. 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 agentHow to install the Gradient MSP skill
Claude DesktopRun installer, then Settings > Extensions to register gradient-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add gradient-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web needs a self-hosted HTTPS server (mcp-install.md).
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add gradient-mcp to mcp.json under the servers key, then pick Agent mode.

The ChatGPT desktop app runs gradient-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server: host gradient-mcp over HTTPS with GRADIENT_MCP_HTTP_TOKEN set, and check that your ChatGPT connector can send that bearer token (mcp-install.md, Remote agents). 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.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot 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 GeminiGemini 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.md directly *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 .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion gradient-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 set GRADIENT_CLI_PATH to an existing binary). Details: #331.

Download Gradient MSP MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Gradient MSP 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 gradient@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Gradient MSP 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/gradient/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/gradient/install.ps1 | iex. Then authenticate per the README and run gradient-cli --help to 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/gradient/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/gradient/install.sh)

The installer drops both gradient-cli (the CLI) and gradient-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

gradient-cli --version
Upgrade 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/gradient/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/gradient/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update gradient@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/gradient --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/gradient --force

Hermes speaks MCP natively, so it can also use the gradient-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the gradient skill from https://github.com/servosity/msp-skills/tree/main/skills/gradient. The skill defines how its required CLI (gradient-cli) can be installed via the openclaw: 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 Gradient MSP portal):

GRADIENT_TOKEN=<value> gradient-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Question your MSP keeps askingCommand
Push a whole file of usage counts and rebuild billing exactly once?gradient-cli usage push --file ./counts.csv --agent
Which accounts' usage changed between my last two pushes?gradient-cli usage drift --agent
Send an alert and confirm the PSA ticket was actually created?gradient-cli alert send --account "123456789" --title "Backup failure" --wait --agent
Which of my dispatched alerts never became tickets?gradient-cli alert trace --stuck --agent
Which accounts are unmapped or missing a vendor SKU?gradient-cli hygiene unmapped --agent
Is my integration ready to flip to active?gradient-cli status ready --agent
Add a single ad-hoc unit count for one account and service?gradient-cli billing --account-id "123456789" --unit-count 42
Are my credentials valid and what's my integration status?gradient-cli integration get --agent

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 Gradient MSP 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 accounts drifted in billable units since your last push, or how many of 200 dispatched alerts never became PSA tickets.

This skill syncs Gradient MSP into a local SQLite mirror with full-text search, and records every count you push in a local ledger. Aggregate questions become one local lookup: instant, offline, and the AI sees the answer, not the raw data. Compound commands like usage drift, hygiene unmapped, and alert trace --stuck join across accounts, service/SKU mappings, and the push ledger - work a stateless API wrapper can't do.

The pain this closes

Billing reconciliation is the recurring tax on MSP margin: every cycle someone pulls a CSV from each vendor, hand-maps the fields to the PSA, and hopes they caught every seat that drifted. It's a standing topic on r/msp, and Gradient MSP's own research frames the manual version as costing up to 90% more time than automating it - which is why 1,000+ MSPs run Synthesize. But Synthesize ships a PowerShell SDK that wants a script project per integration, so the pushes that drive reconciliation live in brittle one-off scripts with no record of what was sent.

This skill closes that gap:

  • `usage push` - push a whole CSV or JSON file of counts in one shot, with exactly one billing rebuild.
  • `usage drift` - the pre-invoice pre-flight: which accounts' counts changed between your last two pushes.
  • `alert send --wait` / `alert trace --stuck` - dispatch an alert and block until the PSA ticket exists; list the ones that never landed.
  • `hygiene unmapped` - one work-queue rollup of every unmapped account and SKU gap.
  • `status ready` - go/no-go before you flip the integration to active.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way gradient-mcp r

Only the beginning is shown; read the rest in the repo

Ask PopNx