PixelVault MCP server
Commit Nov 6, 2026Uploads local images to PixelVault via file path to avoid base64 encoding in model context and provides image management tools.
Also known as pixelvault-dev/mcp-local
- Stars
- 0
- Tools
- 8
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 6, 2026
- License
- MIT
What is PixelVault MCP?
PixelVault uploads local images to PixelVault via file path to avoid base64 encoding in model context and provides image management tools. It exposes 8 tools, such as upload_image, list_images, get_image.
Summary generated from the project's README
About PixelVault MCP server
Uploading local images to PixelVault via file paths is what this MCP server enables for developers using local coding agents. By streaming files as multipart/form-data instead of using base64 encoding, the server prevents large images from consuming model context and tokens. This makes it an ideal choice for local environments where an agent has direct access to files on your disk.
Users set up the server using npx and must provide a PIXELVAULT_API_KEY secret key. It can also read configurations from a local config file if you have used the PixelVault CLI. The server provides a suite of tools including upload_image for streaming files, list_images for searching via AI descriptions, and delete_image for management. It also includes an optimize_image tool that runs entirely on your machine using sharp to compress or resize files without uploading them to an API.
Beyond simple hosting, the server allows for managing image metadata, signing time-limited URLs for private assets, and generating transformation URLs for resizing or background removal.
What you can do with it
- 1Upload images without bloating contextSend a local file path to an AI agent to upload an image to PixelVault without using base64 encoding.
- 2Search hosted images using AIFind specific images in your project by searching through their AI-generated alt text, captions, or OCR content.
- 3Optimize files locallyCompress or resize an image file directly on your machine before it is ever uploaded.
- 4Secure private image accessGenerate a temporary, time-limited link to view a private image.
Written from the project's README. Every use case is checked against a quote from it.
PixelVault MCP tools 8
Detected from the READMEupload_imagelist_imagesget_imageupdate_image_metadatadelete_imagesign_urloptimize_imagetransform_image
Configuration
PIXELVAULT_API_KEYPIXELVAULT_API_URL
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablepixelvault-dev/mcp-local is public and reachablegithub.com/pixelvault-dev/mcp-local ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-06github.com/pixelvault-dev/mcp-local ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model8 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@pixelvault-dev/local-mcp
A local (stdio) MCP server for PixelVault — agent-first image hosting.
The difference from the hosted MCP server (mcp.pixelvault.dev): this one runs on
your machine, so it can upload a local file by path. It reads the bytes off
disk and streams them to the API as multipart/form-data — the file is never
base64-encoded into the model's context. That keeps large images (and slow,
token-hungry base64 round-trips) out of the conversation.
Use the hosted server when your client is remote (ChatGPT, etc.); use this one for local coding agents that have files on disk.
Install
Runs with npx — no global install needed:
npx @pixelvault-dev/local-mcp
Configure
Set your PixelVault API key (a pv_live_… secret key for private uploads):
export PIXELVAULT_API_KEY=pv_live_xxx
# optional: point at a different API
export PIXELVAULT_API_URL=https://api.pixelvault.dev
The server also reads ~/.pixelvault/config.json if you've authenticated with the
PixelVault CLI (pixelvault login).
Claude Desktop / MCP client config
{
"mcpServers": {
"pixelvault": {
"command": "npx",
"args": ["-y", "@pixelvault-dev/local-mcp"],
"env": { "PIXELVAULT_API_KEY": "pv_live_xxx" }
}
}
}
Tools
| Tool | What it does |
|---|---|
upload_image |
Upload by local path (streamed, no base64), or source_url, or data. Optional folder, visibility, expires_in, metadata, describe (AI alt text + caption + OCR in the background; read it with get_image). |
list_images |
List images in your project (paginated), optionally filtered by custom metadata or searched by AI description (q: alt text, caption, OCR text). |
get_image |
Metadata for one image by id. |
update_image_metadata |
Replace an image's custom metadata (replaces, not merges; null clears). |
delete_image |
Permanently delete an image by id. |
sign_url |
Mint a time-limited signed URL for a private image. |
optimize_image |
Compress, resize and convert a local image file on this machine (no API key, nothing uploaded). Writes <name>.optimized.<ext>; never makes a file bigger. |
transform_image |
Build an on-the-fly transform URL (resize, crop, format, AI background removal, effects). |
Every returned CDN URL supports on-the-fly transforms via query params — see the transforms docs.
optimize_image
Runs entirely locally with sharp, an optional dependency: if it can't be
installed for your platform the tool returns a sharp_unavailable error and every other tool is unaffected. Needs
Node 20.9+. Inputs: path, format (keep|webp|avif|jpg|png, default keep), max_width/max_height (never
upscales), quality (default 80), keep_metadata, output_path or in_place, dry_run. EXIF/GPS metadata is stripped
by default (orientation is applied first). It refuses to overwrite an existing file (other than *.optimized.*), never
follows symlinks, writes atomically, and leaves already-optimal files alone, so it is safe to call repeatedly. The same
engine ships in the pixelvault-cli optimize command.
License
MIT
PixelVault MCP questions
What tools does PixelVault MCP provide?
It exposes 8 tools, including upload_image, list_images, get_image, update_image_metadata, delete_image.
How does this server handle local files differently than the hosted version?
This server runs on your machine and can upload local files by path by streaming bytes as multipart/form-data, avoiding base64 encoding in the model context.
Can I optimize images without uploading them to an API?
Yes, the optimize_image tool runs entirely locally on your machine using sharp to compress, resize, and convert files.