Ext Ops Panel
Open dashboard
Comparison

mcp-tools vs MidOS - MCP Community Library

mcp-tools is a plugin bundle for AI coding tools published by izumin5210. Marketplaces we read that list it: 1 (Community GitHub marketplaces). MidOS - MCP Community Library is an MCP server published by MidOSresearch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacemcp-toolsMidOS - MCP Community Library
Community marketplace izumin5210/dotfiles Listed
Version: 1.0.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.2.27
Downloads/month (PyPI): 134
Downloads/week (PyPI): 35
Forks (GitHub): 5
Stars (GitHub): 8
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

mcp-tools vs MidOS - MCP Community Library
Factmcp-toolsMidOS - MCP Community Library
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub8
Forks (GitHub) (differs)No figure on GitHub5
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.deepwiki.com/mcp)Remote server or your machine
Transport (differs)Streamable HTTPstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 11, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/izumin5210/dotfilesgithub.com/midosresearch/midos
Changes in the last 7 days (differs)20
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)Responded 3 days agoNot responding since 2026-10-15

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

mcp-tools

In its own words, on Community GitHub marketplaces:

Personal MCP servers (any-script-mcp, o3-search, deepwiki)

MidOS - MCP Community Library

In its own words, on Official MCP Registry:

Curated knowledge for AI agents — 19K chunks, 121 skills, semantic search via MCP

How to run each

mcp-tools As a Claude Code plugin

Claude Code
/plugin marketplace add izumin5210/dotfiles
/plugin install mcp-tools@izumin5210-dotfiles

MidOS - MCP Community Library As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MIDOS_API_KEY=<YOUR_MIDOS_API_KEY>" --transport stdio midos -- uvx midos-mcp

Requires: MIDOS_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of mcp-tools responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only mcp-tools asks for

  • OPENAI_API_KEY (secret)
  • OPENAI_API_TIMEOUT
  • REASONING_EFFORT
  • SEARCH_CONTEXT_SIZE

Only MidOS - MCP Community Library asks for

  • MIDOS_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: mcp-tools · What it can do: MidOS - MCP Community Library · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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