Skip to main content
Glama
pixelvault-dev

@pixelvault-dev/local-mcp

by pixelvault-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PIXELVAULT_API_KEYYesYour PixelVault API key (a pv_live_… secret key for private uploads)
PIXELVAULT_API_URLNoOptional: point at a different API URL

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
upload_imageA

Upload an image to PixelVault and get an instant CDN URL. Prefer path — a LOCAL file path the server reads off disk and streams — so large files aren't base64-encoded into the model context. Alternatively pass source_url (a public https URL the API imports) or data (base64 bytes). Optional folder, filename, visibility (private → signed URL, needs a secret key), expires_in (auto-expiring image), sign_expires_in. Max 5 MB; JPG/PNG/GIF/WebP/AVIF/SVG. The returned CDN URL supports on-the-fly transforms via query params — e.g. ?w=400&fit=cover (resize/crop), ?fmt=webp (format), ?segment=foreground (AI background removal → transparent PNG), and effects like ?blur=30&saturation=0&rotate=90. Or call transform_image to build a valid transform URL for you. See https://pixelvault.dev/docs#transforms.

list_imagesA

List images in your PixelVault project, most recent first (GET /v1/images), paginated via page/per_page. The returned CDN URL supports on-the-fly transforms via query params — e.g. ?w=400&fit=cover (resize/crop), ?fmt=webp (format), ?segment=foreground (AI background removal → transparent PNG), and effects like ?blur=30&saturation=0&rotate=90. Or call transform_image to build a valid transform URL for you. See https://pixelvault.dev/docs#transforms.

get_imageA

Get metadata (CDN URL, size, MIME type, dimensions) for one PixelVault image by id (GET /v1/images/:id). The returned CDN URL supports on-the-fly transforms via query params — e.g. ?w=400&fit=cover (resize/crop), ?fmt=webp (format), ?segment=foreground (AI background removal → transparent PNG), and effects like ?blur=30&saturation=0&rotate=90. Or call transform_image to build a valid transform URL for you. See https://pixelvault.dev/docs#transforms.

delete_imageA

Permanently delete one PixelVault image by id (DELETE /v1/images/:id).

sign_urlA

Mint a time-limited signed URL for a private image (POST /v1/images/:id/sign-url). The signature binds the image, so the URL can't be replayed against another; strip it and the CDN returns 403. Optional expires_in (seconds, default 3600).

transform_imageA

Build an on-the-fly transform URL for a PixelVault image (resize, crop, format/quality, AI background removal, blur/sharpen/rotate/flip, brightness/contrast/saturation, and same-project watermark tiling). Provide exactly one of url (a PixelVault CDN URL) or id (resolved via the API), plus one or more transform params. See https://pixelvault.dev/docs#transforms.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: uploading, listing, retrieving metadata, deleting, signing URLs, and building transform URLs. No functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., upload_image, list_images, get_image), making the set predictable.

Tool Count5/5

6 tools is appropriate for an image management server—neither too few nor too many, covering essential operations without redundancy.

Completeness4/5

The server covers upload, list, get, delete, signing, and transform URL generation. Missing an update/rename tool for metadata, but the core lifecycle is well-represented.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources