MCP.Market

Local LLM Worker MCP server

by JoblessJoe·io.github.JoblessJoe/local-llm-worker·v0.1.4·2 stars

Local LLM does Claude's bulk work: reads logs and files, researches the web, writes test-gated code.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

2 stars186 downloads/wk

Reviews

Write one

Nobody has reviewed Local LLM Worker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Local LLM Worker tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • configure

    Set up or change local-llm-worker (backend URL, models, search, which tools to use automatically via auto_use). No arguments: effective config, where each value comes from,

  • delegate

    Implement a small function, helper or file with the LOCAL model: write the test first, then call this.

  • offload

    Read big output with the LOCAL model instead of reading it yourself: test runs, builds, logs, large files or diffs.

  • research

    Web lookup with the LOCAL model, instead of WebSearch/WebFetch: docs, current versions, facts from pages.

Public scan report

scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Local LLM Worker compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 4,460 AI and agents servers
Tools
4
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 65% of 2,711 AI and agents servers
Downloads a week
186
more than 73% of 1,538 AI and agents servers with a package

What its tools let an agent do: 4 read

Install Local LLM Worker in Claude Code, Cursor or VS Code

Runs npx -y local-llm-worker on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add local-llm-worker -- npx -y local-llm-worker
Add to Cursor

What the publisher says

From the Local LLM Worker repository's README, as published. We do not edit it. Read it on GitHub

local-llm-worker

Let Claude hand the bulk reading to your local LLM: test logs, big files, web pages. Claude only gets the answer.

Works with Ollama · llama.cpp · LM Studio · vLLM · LocalAI · any OpenAI-compatible endpoint

Reading a 5,000-line test log or three docs pages costs the same frontier-model tokens as hard architectural work. local-llm-worker is an MCP server and Claude Code plugin that moves that bulk work onto the GPU (or CPU) you already own:

the answer.

  • offload: your local model runs the noisy command or reads the big file. Claude gets

cited answer. Claude never sees the pages.

  • research: your local model searches the web, reads the pages in full and returns a

and retries until a test Claude wrote first passes. Claude gets a one-line verdict, not the code.

  • delegate (opt-in): your local model writes one file in an isolated git worktree
> offload  npm test 2>&1   "Which test fails, and why?"
`fixed coupon never goes below zero` (test/cart.test.js:404): applyCoupon(5, {type:'fixed',
value:10}) returns -5, expected 0.
— qwen3-coder:30b-a3b-q4_K_M · 19,132 input tokens read locally

Why

slower.

  • Any model, any hardware. No hardcoded models, no GPU assumptions. CPU-only works, just

The concurrency limit is a config value, not a hardcoded lock.

  • Parallel by default. Several calls in one turn, or from several subagents, run at once.

text (number-heavy logs need more tokens than prose). Anything cut is reported.

  • Fits the context automatically. Material is sized to the model's context window per

and changes any setting. It takes effect on the next call, with no restart.

  • Zero dependencies. Plain Node ≥ 18. Installing from git needs no npm install.
  • Agent-configurable. One configure call shows the config, the backend and its models,

Install

Prerequisites: Node ≥ 18, git, and a running local model server (e.g. ollama pull qwen3-coder:30b).

Claude Code plugin

/plugin marketplace add JoblessJoe/local-llm-worker
/plugin install local-llm-worker@local-llm-worker

Then just ask: "set up local-llm-worker for my machine". Claude finds your backend, picks a model, and asks which tools it should use on its own (auto_use). By default that's offload and research; delegate is opt-in. Every tool also works whenever you ask for it.

Make Claude use it every time

A session-start reminder nudges Claude toward the tools you chose. For dependable use, add this to your CLAUDE.md; setup offers to do it for you:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Local LLM Worker: common questions

Is Local LLM Worker MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Local LLM Worker safety report
How do I install Local LLM Worker?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Local LLM Worker need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Local LLM Worker maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v0.1.4.
What can I use instead of Local LLM Worker?
Servers from other publishers that do the same job: agent-device MCP server, Basic Memory MCP server and Superlog MCP server.
How does Local LLM Worker compare with other AI and agents MCP servers?
safety score 92/100 (higher than 90% of 4,460 AI and agents servers); tools 4 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Local LLM Worker

Same job from other publishers: the closest match first, then the best rated.

  • agent-device
    Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • Superlog
    Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
    A
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • You.com Web Access & AI
    Web search, AI agent, and content extraction via You.com APIs
    A