Ext Ops Panel
Open dashboard
Comparison

Salesforce (Headless 360, Beta) vs MCP Dataverse

Salesforce (Headless 360, Beta) is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). MCP Dataverse is an MCP server published by codeurali. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceSalesforce (Headless 360, Beta)MCP Dataverse
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 066
Stars (GitHub): 11 026
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.0
Forks (GitHub): 2
Stars (GitHub): 15
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

Salesforce (Headless 360, Beta) vs MCP Dataverse
FactSalesforce (Headless 360, Beta)MCP Dataverse
Marketplaces that list it11
Stars (GitHub) (differs)11 026 (better)15 (worse)
Forks (GitHub) (differs)1 066 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-dataverse)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/codeurali/mcp-dataverse
Changes in the last 7 days00
First seen2026-10-112026-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

Salesforce (Headless 360, Beta)

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

Manage records, users, and org setup across Salesforce.

MCP Dataverse

In its own words, on Official MCP Registry:

73 tools for Microsoft Dataverse: CRUD, FetchXML, metadata, audit, batch, role privileges and more.

How to run each

Salesforce (Headless 360, Beta)

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

MCP Dataverse As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dataverse -- npx -y mcp-dataverse

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

The marketplaces of Salesforce (Headless 360, Beta) publish no settings it asks for, so we do not compare settings.

What it can do: Salesforce (Headless 360, Beta) · What it can do: MCP Dataverse · 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. 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