English Français العربية

Pixelixe

Official registry Marketing and sales

Brand-safe MCP for AI agents to create editable, on-brand graphics and automate variants.

Source code Website Documentation

What can you do with Pixelixe?

  • Creative automation for marketing teams
  • On-brand graphic generation for AI agents
  • Template-based image and graphic variants
  • Editable graphics for review and approval workflows
  • Branded content production for ecommerce, SaaS, and internal automation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http pixelixe 'https://studio.pixelixe.com/api/mcp/v1'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "pixelixe": {
            "type": "http",
            "url": "https://studio.pixelixe.com/api/mcp/v1"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Pixelixe MCP
  2. MCP endpoint
  3. What Pixelixe MCP does
  4. Why teams use Pixelixe MCP
  5. Typical use cases
  6. Authentication
  7. Links
  8. Official registry entry
  9. Notes

Pixelixe MCP

Pixelixe MCP is a remote MCP server for AI agents that need on-brand graphic generation, editable outputs, reusable templates, and creative automation workflows.

It gives AI agents a brand-safe creative layer to generate graphics from natural language, reuse approved templates, and automate visual variants for marketing, ecommerce, and branded content workflows.

MCP endpoint

https://studio.pixelixe.com/api/mcp/v1

What Pixelixe MCP does

  • Create editable, on-brand graphics from natural language
  • Reuse templates and saved Pixelixe documents
  • Generate visual variants for campaigns, messages, and formats
  • Return outputs teams can review, edit, approve, and reuse
  • Support creative automation and branded visual production across AI workflows

Why teams use Pixelixe MCP

  • Turn AI prompts into editable branded graphics instead of one-off flat images
  • Keep creative output aligned with templates, brand rules, and reusable layouts
  • Automate marketing creatives, campaign variants, social graphics, and other recurring assets
  • Give designers and operators a workflow where outputs can still be reviewed and refined

Typical use cases

  • Creative automation for marketing teams
  • On-brand graphic generation for AI agents
  • Template-based image and graphic variants
  • Editable graphics for review and approval workflows
  • Branded content production for ecommerce, SaaS, and internal automation

Authentication

Pixelixe MCP supports:

  • OAuth for clients that support remote MCP sign-in flows
  • Bearer authentication with a Pixelixe API key when a client accepts a custom bearer token

Official registry entry

  • Name: com.pixelixe/pixelixe-mcp
  • Endpoint: https://studio.pixelixe.com/api/mcp/v1

Notes

This repository is the public metadata and documentation entry point for the hosted Pixelixe MCP server. The production runtime is operated by Pixelixe and is not distributed from this repository.

Frequently asked questions

What is Pixelixe?

Brand-safe MCP for AI agents to create editable, on-brand graphics and automate variants.

How do I install Pixelixe?

It runs as a remote server. In Claude Code: claude mcp add --transport http pixelixe 'https://studio.pixelixe.com/api/mcp/v1'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Pixelixe need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Pixelixe open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Pixelixe?

It is published by pixelixe. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.