Ext Ops Panel
Open dashboard
Comparison

dataverse vs Ollama / vLLM Bridge

dataverse is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 2 (Copilot CLI: github/awesome-copilot, Copilot CLI: github/copilot-plugins). Ollama / vLLM Bridge is an MCP server published by setheerwagen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
MarketplacedataverseOllama / vLLM Bridge
Copilot CLI: github/awesome-copilot Listed
Version: 1.16.1
Forks (GitHub): 63
Stars (GitHub): 248
Not marked · First seen
Not listed
Copilot CLI: github/copilot-plugins Listed
Version: not stated
Forks (GitHub): 63
Stars (GitHub): 248
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.6
Downloads/month (PyPI): 256
Downloads/week (PyPI): 175
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

dataverse vs Ollama / vLLM Bridge
FactdataverseOllama / vLLM Bridge
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)248 (better)0 (worse)
Forks (GitHub) (differs)63 (better)0 (worse)
Last release (differs)2026-10-23 (better)2026-10-22 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-ollama-vllm)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published7, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/dataverse-skillsgithub.com/setheerwagen/local-ai-mcp-servers
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

dataverse

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

Microsoft Dataverse plugin for coding agents, covering record CRUD, bulk data operations, advanced queries, schema and metadata, administration, security, environment management, and solution lifecycle through MCP, CLI, and SDK workflows.

Ollama / vLLM Bridge

In its own words, on Official MCP Registry:

Call your local Ollama or vLLM model over MCP with schema-validated JSON output

How to run each

dataverse

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

Ollama / vLLM Bridge As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LOCAL_API_KEY=<YOUR_LOCAL_API_KEY>" --transport stdio mcp-ollama-vllm -- uvx mcp-ollama-vllm

Requires: LOCAL_API_KEY (secret)

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: Ollama / vLLM Bridge · 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 public marketplace file https://github.com/github/copilot-plugins/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