Content Tools
pixelvault.dev
Manage images on PixelVault, including upload, retrieval, listing, and deletion with CDN URLs.
ENDPOINT 1
https://mcp.pixelvault.dev/mcp
MCP server metadata
- Name
- pixelvault
- Version
- 0.3.0
Known tools 8
get_imageGet metadata (CDN URL, size, MIME type, dimensions) for one PixelVault image by id.
Inferred read-onlyupload_batchUpload many images (1–50) in one call, grouped into a collection — e.g.
Potential side effectstransform_imageBuild 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).
Inferred read-onlyrescue_imgurScan a web page for hotlinked Imgur images and return a PixelVault rescue URL for each — a proxy that lazily rehosts the image on first request, keeping it working through the UK Imgur block.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pixelvault]
url = "https://mcp.pixelvault.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pixelvault": {
"type": "http",
"url": "https://mcp.pixelvault.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pixelvault
Remote MCP URL: https://mcp.pixelvault.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pixelvault": {
"url": "https://mcp.pixelvault.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pixelvault": {
"type": "http",
"url": "https://mcp.pixelvault.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pixelvault",
"transport": "streamable-http",
"url": "https://mcp.pixelvault.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://mcp.pixelvault.dev/mcp/oauth
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pixelvault-dev]
url = "https://mcp.pixelvault.dev/mcp/oauth"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"pixelvault-dev": {
"type": "http",
"url": "https://mcp.pixelvault.dev/mcp/oauth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: pixelvault-dev
Remote MCP URL: https://mcp.pixelvault.dev/mcp/oauth
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pixelvault-dev": {
"url": "https://mcp.pixelvault.dev/mcp/oauth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"pixelvault-dev": {
"type": "http",
"url": "https://mcp.pixelvault.dev/mcp/oauth",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "pixelvault-dev bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "pixelvault-dev",
"transport": "streamable-http",
"url": "https://mcp.pixelvault.dev/mcp/oauth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for pixelvault.dev was fetched 2026-08-04T00:18:21.702Z and is being refreshed.
pixelvault.dev is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.