Pixelvault

Created By
rsweeting1a month ago
AI-native marketplace for pre-cleared licensed assets. Search, license, and stream media rights programmatically — built for post-production, editorial, and brand workflows. Includes tools to search assets, get asset details, and generate usage agreements.
Overview

pixelvault-mcp

MCP server for PixelVault — AI-native marketplace for pre-cleared licensed assets.

Install

Add to your Claude Desktop config:

{
  "mcpServers": {
    "pixelvault": {
      "command": "npx",
      "args": ["-y", "pixelvault-mcp"]
    }
  }
}

Or run directly:

npx pixelvault-mcp

Tools

search_assets

Search PixelVault's database of pre-cleared AI-generated assets using a natural language brief. Returns a ranked shortlist with compliance status and rationale for each match.

get_asset_details

Retrieve full metadata and compliance documentation for a specific asset by ID.

generate_usage_agreement

Generate a completed usage agreement draft based on your project parameters (usage type, territory, duration, platform).

About

PixelVault is a compliance-cleared AI asset marketplace. Every asset is sourced from licensed AI platforms (Adobe Firefly, Moonvalley) and pre-cleared for commercial use. The MCP server gives Claude agents native access to search, evaluate, and license assets without leaving your workflow.

License

MIT

Server Config

{
  "mcpServers": {
    "pixelvault": {
      "command": "npx",
      "args": [
        "pixelvault-mcp"
      ]
    }
  }
}
Project Info
Created At
a month ago
Updated At
a month ago
Author Name
rsweeting1
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago