Ext Ops Panel
Open dashboard
Comparison

nitrosend vs Wild Apricot MCP Server and API by Cotlet

nitrosend is a plugin bundle for AI coding tools published by nitrosend. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Wild Apricot MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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

Where each is published
MarketplacenitrosendWild Apricot MCP Server and API by Cotlet
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
No figure published
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

nitrosend vs Wild Apricot MCP Server and API by Cotlet
FactnitrosendWild Apricot MCP Server and API by Cotlet
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)Not published2026-11-10
Where it runs (differs)Remote server (api.nitrosend.com/mcp)Remote server (cotlet.dev/mcp/v1/wild-apricot/connect)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nitrosend/copilotNot stated
Changes in the last 7 days (differs)07
First seen (differs)2026-10-262026-11-09
Endpoint at the last check (differs)Responded 17 h ago, requires authenticationAnswered with HTTP 302 (24 h ago)

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

In its own words, on Copilot CLI: github/awesome-copilot:

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.

Wild Apricot MCP Server and API by Cotlet

In its own words, on Official MCP Registry:

Wild Apricot club and association management MCP server: list contacts.

How to run each

nitrosend

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Wild Apricot MCP Server and API by Cotlet As a remote MCP server

Claude Code
claude mcp add --transport http wild-apricot https://cotlet.dev/mcp/v1/wild-apricot/connect

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of nitrosend 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: Wild Apricot MCP Server and API by Cotlet · 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.

Where the data comes from: how the catalog is built