PixelMagic MCP server
Exposes the PixelMagic image toolkit as tools for AI agents (Claude Desktop, Cursor, and
any MCP client). Each tool calls the public REST API at PIXELMAGIC_API_URL/api/v1/* with
your API key, so it inherits the same auth, per-plan rate limiting, credit metering, and
SSRF protection — there is no separate, less-guarded path.
Tools: generate, edit, upscale, remove_background, remove_object, layers,
localize, enhance, vectorize, list_models, account, health. Works with MCP Python
SDK v1 and v2.
Get an API key
Sign in at pixelmagic.studio → Dashboard → API keys → Create
key. Copy it (shown once). It looks like sk_live_….
Install & connect
You don't need to clone anything — uv (or pipx) can run it
on demand. Add this to your client's MCP config:
Claude Desktop (claude_desktop_config.json) / Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"pixelmagic": {
"command": "uvx",
"args": ["pixelmagic-mcp"],
"env": { "PIXELMAGIC_API_KEY": "sk_live_..." }
}
}
}
Restart the client and the PixelMagic tools appear. Prefer a global install? Run
pipx install pixelmagic-mcp and use "command": "pixelmagic-mcp" (drop the args).
Run from source
pip install "mcp[cli]>=1.2" httpx
export PIXELMAGIC_API_KEY=sk_live_...
python lucida_mcp.py # stdio
Host it for your users (no install on their side)
MCP_TRANSPORT=streamable-http pixelmagic-mcp
Run it on any always-on host (a small VM, Render, Fly, Railway, a container — not Vercel's
serverless). Each user connects with their own PIXELMAGIC_API_KEY.
Environment
| Variable | Default | Purpose |
|---|---|---|
PIXELMAGIC_API_KEY |
— | Your sk_live_… key (required) |
PIXELMAGIC_API_URL |
https://pixelmagic.studio |
API base URL |
MCP_TRANSPORT |
stdio |
stdio or streamable-http |
Offline rendering (HyperFrames video renders)
hyperframes_modal.py renders each video in a Modal Sandbox with no network
(block_network=True). Before the Sandbox starts, the trusted function downloads the
composition's allowlisted assets — the GSAP CDNs (same list as lib/video/ai-html-guard.ts),
Google Fonts (CSS + font files), and user media on R2 (*.r2.cloudflarestorage.com,
*.r2.dev, R2_PUBLIC_HOST, and pixelmagic.studio/api/asset for the render owner's own
files) — via safe_download.py (60 MB per file, 600 MB total, 20 s each), writes them into
the Sandbox as /tmp/proj/assets/<sha1>.<ext> and rewrites the HTML to those relative paths
(render_assets.py). Any other URL is left as-is and simply fails offline.
- Kill switch: set
RENDER_OFFLINE=0in thepixelmagic-hyperframessecret to go back to the old public-egress Sandbox (default is1), then redeploy. - Tests:
python3 server/tests_render_assets.py - Redeploy after changing any of these files:
modal deploy server/hyperframes_modal.py
Metadata
Release files for pixelmagic-mcp 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pixelmagic_mcp-0.4.0.tar.gz | 8.1 kB | Without provenance | Details for pixelmagic_mcp-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pixelmagic_mcp-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for pixelmagic_mcp-0.4.0-py3-none-any.whl |
Total release size: 16.9 kB
Release files / pixelmagic_mcp-0.4.0.tar.gz
| Download URL | pixelmagic_mcp-0.4.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4fbda7d9d11b5250132c52db3751f32bbf3ec3be59678bdc56dbd5c0d03a4f92
|
|
BLAKE2b-256 checksum How to use checksums |
1131a856cda0ec4673eef4177175f71b5fa07dd257629020c013efc73ce7c96a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / pixelmagic_mcp-0.4.0-py3-none-any.whl
| Download URL | pixelmagic_mcp-0.4.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ea4c0398b74441db6187105133bc429311fb02a6604a7c5cf26a2055e86c3de
|
|
BLAKE2b-256 checksum How to use checksums |
ae0642ce918eb013f62da7ea48a86866d021149f75ec6f725b76fb28aef2ab74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for pixelmagic-mcp 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.