Ext Ops Panel
Open dashboard
Comparison

NetSuite vs io.github.PromptPartner/bexio-mcp-server

NetSuite is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.PromptPartner/bexio-mcp-server is an MCP server published by PromptPartner. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-13. 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
MarketplaceNetSuiteio.github.PromptPartner/bexio-mcp-server
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 701
Stars (GitHub): 16 155
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.6.2
Downloads/month (npm): 840
Downloads/week (npm): 192
Forks (GitHub): 14
Stars (GitHub): 42
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.6.2
Downloads/month (npm): 840
Downloads/week (npm): 192
Forks (GitHub): 14
Stars (GitHub): 42
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

NetSuite vs io.github.PromptPartner/bexio-mcp-server
FactNetSuiteio.github.PromptPartner/bexio-mcp-server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)16 155 (better)42 (worse)
Forks (GitHub) (differs)1 701 (better)14 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@promptpartner/bexio-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/cursor/pluginsgithub.com/promptpartner/bexio-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-11-122026-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

NetSuite

In its own words, on Cursor: cursor/plugins:

Work with records, reports, saved searches, and SuiteQL queries in NetSuite.

io.github.PromptPartner/bexio-mcp-server

In its own words, on Official MCP Registry:

Swiss accounting integration for Bexio. 315 tools: invoices, contacts, projects, account balances

How to run each

NetSuite

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

io.github.PromptPartner/bexio-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio bexio-mcp-server -- npx -y @promptpartner/bexio-mcp-server

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

Neither one's marketplaces publish the settings it asks for.

What it can do: NetSuite · What it can do: io.github.PromptPartner/bexio-mcp-server · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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