Docpick vs io.github.Swih/mistral-mcp
Docpick is an MCP server published by ArkNill. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Swih/mistral-mcp is an MCP server published by Swih. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (PyPI): 2 671 Downloads/week (PyPI): 982 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 1 207 Downloads/week (npm): 119 Forks (GitHub): 2 Stars (GitHub): 15 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.7.0 Forks (GitHub): 2 Stars (GitHub): 15 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 207 Downloads/week (npm): 119 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
| Fact | Docpick | io.github.Swih/mistral-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 4 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 15 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (docpick) | On your machine (mistral-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 12 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/quartzunit/docpick | github.com/swih/mistral-mcp |
| Changes in the last 7 days | 0 | 0 |
| 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
Docpick
Schema-driven document extraction with local OCR + LLM. Document in, Structured JSON out.
io.github.Swih/mistral-mcp
Mistral MCP server: extract invoices and documents from text, Markdown or OCR into typed JSON.
How to run each
Docpick As a local MCP server: PyPI package
claude mcp add --transport stdio docpick -- uvx docpick
io.github.Swih/mistral-mcp As a local MCP server: npm package
claude mcp add --env "MISTRAL_API_KEY=<YOUR_MISTRAL_API_KEY>" --transport stdio mistral-mcp -- npx -y mistral-mcp
Requires: MISTRAL_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 Docpick publish no settings it asks for, so we do not compare settings.
What it can do: Docpick · What it can do: io.github.Swih/mistral-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.