NinjaOne vs IT Glue
NinjaOne is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). IT Glue is an MCP server published by mspstack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  NinjaOne |  IT Glue |
|---|---|---|
| Official MCP Registry | Listed Version: 2.5.1 Forks (GitHub): 26 Stars (GitHub): 26 Not marked · First seen |
Listed Version: 0.6.0 Downloads/month (npm): 400 Downloads/week (npm): 79 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | NinjaOne | IT Glue |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 26 (better) | 5 (worse) |
| Forks (GitHub) (differs) | 26 (better) | 1 (worse) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (ghcr.io/wyre-ai/ninjaone-mcp:v2.5.1) | On your machine (mcp-itglue) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 14, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/wyre-ai/ninjaone-mcp | github.com/mspstack/mcp-itglue |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
NinjaOne
MCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.
IT Glue
IT Glue MCP server for MSPs — documents, flexible assets, semantic vector search, RBAC, and BYOK
How to run each
NinjaOne As a local MCP server: Docker image
claude mcp add --env "NINJAONE_CLIENT_ID=<YOUR_NINJAONE_CLIENT_ID>" --env "NINJAONE_CLIENT_SECRET=<YOUR_NINJAONE_CLIENT_SECRET>" --transport stdio ninjaone-mcp -- docker run -i --rm -e NINJAONE_CLIENT_ID -e NINJAONE_CLIENT_SECRET ghcr.io/wyre-ai/ninjaone-mcp:v2.5.1Requires: NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET (secret)
IT Glue As a local MCP server: npm package
claude mcp add --env "AZURE_OPENAI_API_KEY=<YOUR_AZURE_OPENAI_API_KEY>" --env "AZURE_STORAGE_CONNECTION_STRING=<YOUR_AZURE_STORAGE_CONNECTION_STRING>" --env "ITGLUE_API_KEY=<YOUR_ITGLUE_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio mcp-itglue -- npx -y mcp-itglueRequires: AZURE_OPENAI_API_KEY (secret), AZURE_STORAGE_CONNECTION_STRING (secret), ITGLUE_API_KEY (secret), OPENAI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only NinjaOne asks for
AUTH_MODELOG_LEVELMCP_TRANSPORTNINJAONE_CLIENT_IDNINJAONE_CLIENT_SECRET (secret)NINJAONE_REGION
Only IT Glue asks for
AZURE_OPENAI_API_KEY (secret)AZURE_OPENAI_ENDPOINTAZURE_STORAGE_ACCOUNTAZURE_STORAGE_CONNECTION_STRING (secret)AZURE_STORAGE_CONTAINEREMBEDDING_MODELITGLUE_ADVANCED_TOOLSETITGLUE_API_KEY (secret)ITGLUE_BASE_URLITGLUE_REGIONOPENAI_API_KEY (secret)PUBLIC_BASE_URL
Show the remaining 2
UPLOAD_STAGINGVECTOR_INDEX_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: NinjaOne · What it can do: IT Glue · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.