dataverse vs Dicker Data
dataverse is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Dicker Data is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  dataverse |  Dicker Data |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.0.0 Forks (GitHub): 62 Stars (GitHub): 244 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 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 | dataverse | Dicker Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 244 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 62 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/wyre-ai/dicker-data-mcp:v1.0.3) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/dataverse-skills | github.com/wyre-ai/dicker-data-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
dataverse
Build and manage Microsoft Dataverse solutions using natural language. Includes table/column creation, solution lifecycle, data operations, and MCP server configuration.
Dicker Data
MCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices.
How to run each
dataverse
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Dicker Data As a local MCP server: Docker image
claude mcp add --env "DICKERDATA_ACCESS_TOKEN=<YOUR_DICKERDATA_ACCESS_TOKEN>" --env "DICKERDATA_ACCOUNT_CODE=<YOUR_DICKERDATA_ACCOUNT_CODE>" --transport stdio dicker-data-mcp -- docker run -i --rm -e DICKERDATA_ACCESS_TOKEN -e DICKERDATA_ACCOUNT_CODE ghcr.io/wyre-ai/dicker-data-mcp:v1.0.3Requires: DICKERDATA_ACCESS_TOKEN (secret), DICKERDATA_ACCOUNT_CODE
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 dataverse publish no settings it asks for, so we do not compare settings.
What it can do: dataverse · What it can do: Dicker Data · 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.