PixelDrive MCP MCP server

An official MCP server provided by PixelDrive that allows AI agents to interact with the PixelDrive image rendering platform. It exposes 26 tools enabling agents to list and browse templates, design and edit templates programmatically (adding elements, updating properties), search stock assets, and render final branded images in various formats like PNG and JPEG. It supports variable data injection for text, images, and ratings, facilitating automated generation of marketing creatives, e-commerce catalogs, and localized campaign assets.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

API keyEndpoint checked 2026-10-05Operated by PixelDrive

MCP endpoint (Streamable HTTP)

https://pixeldrive.pro/mcp

Vendor documentation

What you can do with it

Generate branded marketing images from templates via AI prompts
Automate e-commerce product catalog image creation
Design and edit visual assets programmatically
Render localized campaign graphics for multiple languages

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http pixeldrive-mcp https://pixeldrive.pro/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add pixeldrive-mcp --url https://pixeldrive.pro/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pixeldrive-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "pixeldrive-mcp": {
      "url": "https://pixeldrive.pro/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "pixeldrive-mcp": {
      "type": "streamableHttp",
      "url": "https://pixeldrive.pro/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pixeldrive-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "pixeldrive-mcp": {
      "type": "http",
      "url": "https://pixeldrive.pro/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http pixeldrive-mcp https://pixeldrive.pro/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "pixeldrive-mcp": {
      "url": "https://pixeldrive.pro/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "pixeldrive-mcp": {
      "serverUrl": "https://pixeldrive.pro/mcp"
    }
  }
}

See all 161

Do you run PixelDrive MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing