Wraps local Ollama models so bulk generation runs on your own hardware, not a paid API.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
local_generateGeneral-purpose local LLM generation. Delegates work to a local Ollama model
to save tokens. Use this when the task is bulk text processing that doesn't
require Opus-level reasoning: summarising documents, explaining code for docs,
generating boilerplate, reformatting content, translating, etc.
Th…General-purpose local LLM generation. Delegates work to a local Ollama model to save tokens. Use this when the task is bulk text processing that doesn't require Opus-level reasoning: summarising documents, explaining code for docs, generating boilerplate, reformatting content, translating, etc. Th…
No input schema was published for this tool.
local_summarizeSummarise long text locally. Use this instead of having Opus process large
blocks of text when you only need a summary. Feed in file contents, docs,
logs, or any bulk text and get a concise summary back.
Particularly valuable for: large file contents, documentation, log output,
meeting notes, long…Summarise long text locally. Use this instead of having Opus process large blocks of text when you only need a summary. Feed in file contents, docs, logs, or any bulk text and get a concise summary back. Particularly valuable for: large file contents, documentation, log output, meeting notes, long…
No input schema was published for this tool.
local_analyzeExtract structured information from text locally. Use this for classification,
entity extraction, tagging, pattern recognition, or any task that transforms
unstructured text into structured output.
Good for: categorising issues, extracting names/dates/amounts, tagging content,
parsing semi-structu…Extract structured information from text locally. Use this for classification, entity extraction, tagging, pattern recognition, or any task that transforms unstructured text into structured output. Good for: categorising issues, extracting names/dates/amounts, tagging content, parsing semi-structu…
No input schema was published for this tool.
local_draftDraft text locally - commit messages, PR descriptions, docstrings, changelog
entries, documentation sections, or any formulaic text that follows a template
or convention. Saves Opus tokens on boilerplate generation.Draft text locally - commit messages, PR descriptions, docstrings, changelog entries, documentation sections, or any formulaic text that follows a template or convention. Saves Opus tokens on boilerplate generation.
No input schema was published for this tool.
local_codeCode-aware local generation. Claude reads source code with Read/Grep (free),
then delegates the TEXT GENERATION to local - docstrings, test stubs,
explanations, type annotations, inline comments, or review feedback.
This is the primary tool for reducing API token usage on code tasks.
Claude orches…Code-aware local generation. Claude reads source code with Read/Grep (free), then delegates the TEXT GENERATION to local - docstrings, test stubs, explanations, type annotations, inline comments, or review feedback. This is the primary tool for reducing API token usage on code tasks. Claude orches…
No input schema was published for this tool.
local_diffAnalyse a git diff locally. Use this for generating commit messages,
PR descriptions, changelog entries, or understanding what changed in a diff.
Claude runs `git diff` (free), passes the output here for text generation.
Particularly valuable for large diffs that would consume many API tokens
if p…Analyse a git diff locally. Use this for generating commit messages, PR descriptions, changelog entries, or understanding what changed in a diff. Claude runs `git diff` (free), passes the output here for text generation. Particularly valuable for large diffs that would consume many API tokens if p…
No input schema was published for this tool.
local_transformPerform mechanical code transformations locally. These are pattern-based
transforms that don't require architectural understanding - the kind of
work that burns API tokens for no good reason.
Use this for: converting between formats, renaming patterns, migrating
syntax, generating boilerplate from…Perform mechanical code transformations locally. These are pattern-based transforms that don't require architectural understanding - the kind of work that burns API tokens for no good reason. Use this for: converting between formats, renaming patterns, migrating syntax, generating boilerplate from…
No input schema was published for this tool.
local_modelsList all models available in the local Ollama instance. Use this to check
what models are loaded and available for delegation.List all models available in the local Ollama instance. Use this to check what models are loaded and available for delegation.
No input schema was published for this tool.
local_pullPull/download a model into Ollama from the registry, or import a local GGUF
file. Use this to make additional models available for delegation.
For GGUF files, create an Ollama Modelfile first, then use 'ollama create'.
This tool handles registry pulls (e.g., 'qwen2.5:14b', 'deepseek-r1:8b').Pull/download a model into Ollama from the registry, or import a local GGUF file. Use this to make additional models available for delegation. For GGUF files, create an Ollama Modelfile first, then use 'ollama create'. This tool handles registry pulls (e.g., 'qwen2.5:14b', 'deepseek-r1:8b').
No input schema was published for this tool.
local_visionNo description publishedThis tool published no description. Forge does not invent one.
9 of 10 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Wraps local Ollama models so bulk generation runs on your own hardware, not a paid API.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.