Ext Ops Panel
Open dashboard
Comparison

io.github.Michael-WhiteCapData/ollama-handoff vs Sezzlee Local LLM

io.github.Michael-WhiteCapData/ollama-handoff is an MCP server published by Michael-WhiteCapData. Marketplaces we read that list it: 1 (Official MCP Registry). Sezzlee Local LLM is an MCP server published by sezzlee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceio.github.Michael-WhiteCapData/ollama-handoffSezzlee Local LLM
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 259
Downloads/week (PyPI): 36
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 383
Downloads/week (npm): 48
Forks (GitHub): 0
Stars (GitHub): 1
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

io.github.Michael-WhiteCapData/ollama-handoff vs Sezzlee Local LLM
Factio.github.Michael-WhiteCapData/ollama-handoffSezzlee Local LLM
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ollama-handoff)On your machine (@sezzlee/llm-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 07, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/michael-whitecapdata/ollama-handoffgithub.com/sezzlee/mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

io.github.Michael-WhiteCapData/ollama-handoff

In its own words, on Official MCP Registry:

Offload cheap work from your AI agent to a local Ollama model, at zero cloud cost.

Sezzlee Local LLM

In its own words, on Official MCP Registry:

Let a planning agent hand bounded language work to a local Ollama model.

How to run each

io.github.Michael-WhiteCapData/ollama-handoff As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio ollama-handoff -- uvx ollama-handoff

Sezzlee Local LLM As a local MCP server: npm package

Claude Code
claude mcp add --env "SEZZLEE_LLM_MODEL=<YOUR_SEZZLEE_LLM_MODEL>" --transport stdio llm -- npx -y @sezzlee/llm-mcp

Requires: SEZZLEE_LLM_MODEL

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

Only io.github.Michael-WhiteCapData/ollama-handoff asks for

  • OLLAMA_DEFAULT_MODEL
  • OLLAMA_KEEP_ALIVE
  • OLLAMA_NUM_CTX
  • OLLAMA_TIMEOUT_S
  • OLLAMA_URL

Only Sezzlee Local LLM asks for

  • SEZZLEE_LLM_BASE_URL
  • SEZZLEE_LLM_KEEP_ALIVE
  • SEZZLEE_LLM_MODEL
  • SEZZLEE_LLM_NUM_CTX
  • SEZZLEE_LLM_OUTPUT_DIR
  • SEZZLEE_LLM_ROOT
  • SEZZLEE_LLM_TIMEOUT_MS

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

What it can do: io.github.Michael-WhiteCapData/ollama-handoff · What it can do: Sezzlee Local LLM · Compare two other plugins

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