nitrosend vs iBlueText
nitrosend is a plugin bundle for AI coding tools published by nitrosend. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). iBlueText is an MCP server published by ibluetext.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  nitrosend |  iBlueText |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | nitrosend | iBlueText |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | Remote server (api.nitrosend.com/mcp) | Remote server (ibluetext.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/nitrosend/copilot | github.com/ibluetext/ibluetext-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-26 | 2026-10-26 |
| Endpoint at the last check (differs) | Status out of date: last check 47 h ago returned HTTP 401 | Status out of date: last check 44 h ago returned HTTP 401 |
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
nitrosend
Prepare and review email campaigns, automation flows, contacts and transactional messages in Nitrosend through its hosted OAuth MCP server. Includes a scoped skill for account selection, consent and live-send review.
iBlueText
Send iMessage, SMS and WhatsApp from a dedicated line, run text campaigns and read replies.
How to run each
nitrosend
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
iBlueText As a remote MCP server
claude mcp add --transport http ibluetext https://ibluetext.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: nitrosend · What it can do: iBlueText · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.