MCP Server that enables local agentic flows or inference to capture and to 'see/analyze' images in a continuous loop (for example, when using LMStudio for Agentic Flow and a VLM can retrieve but not actually see the real pixels of the picture and the flow breaks).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-local-vision","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 👁️ mcp-local-vision (Local Vision MCP Tool) > **Give your local agent eyes. Close the autonomous loop.** **mcp-local-vision** is the missing link for autonomous local AI. It allows standard MCP agents (Your local agent running on LMStudio/Ollama/vLLM, Claude Desktop, Goose, etc.) to **"see"** images, screenshots, and visual assets by routing them back through an call to the same inference engine and same model (in case the initial model was a VLM model of course so that it can see and reason about the image thus enhancing your workflows. Most current MCP servers like Playwright, File Access and Screenshot tools are missing the ability to allow the Agentic AI mode to actually see and reason about images and just returning responses that the end user at the GUI level can see but the Agentic Model is blind to, thus hindering the agentic flowIt also supports cloud providers like Anthropic, Gemini, OpenAI, Openrouter etc... ## 🚫 The Problem: The "Blind Agent" Paradox You have a cutting-edge local agent. You ask it to "Debug my UI." 1. Agent launches the app. 2. Agent takes a screenshot to check for errors. 3. **Agent stops.** 🛑 Why? Because standard MCP tools only *save* screenshots to disk. The agent knows the file *exists*, but it cannot *see* the pixels. It is blind to its own actions. ## ✅ The Solution: The Visual Loop **mcp-local-vision** bridges the file system and your inference engine. 1. **Agent** takes a screenshot via Playwright/Puppeteer. 2. **Agent** calls `analyze_image(path)`. 3. **mcp-local-vision** instantly pipes the raw pixels to your already hosted model (no extra host, VRAM/RAM usag, just efficient routing/loop in case the initial model supports Vision, or choose any other endpoint where a VLM is hosted and it works too. 4. **Agent** receives a detailed description (from it-self sometimes! for a full descroption on the image which can allow it to proceed further ("I see a 404 error on the dashboard"). 5. **Agent** takes the nex…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.