Creatica MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Creatica procedural-background generation over local stdio: Which background-generation tools run locally, and do new export capabilities change the documented data boundary?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Deterministic local procedural SVG/PNG background generation for design and build workflows.

What we know

Local-first MCP server for browsing, describing and generating Creatica's procedural backgrounds; same seed produces reproducible output. A hosted API/MCP option exists for permanent URLs.

Maintenance / activity evidence

@creatica/mcp 0.1.3 published 2026-09-06T18:05:29.015Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Local generation reads parameters and writes/returns generated SVG/PNG assets. Writes: Generate image assets; Potentially write/export generated files depending on client workflow.
Authentication not yet verified.
Sensitive access: Brand palettes or design parameters if supplied

Primarily creative generation; hosted mode adds external data/cost boundary.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Which background-generation tools run locally, and do new export capabilities change the documented data boundary?

Owner-reviewed official Creatica documentation establishes the local stdio MCP execution/product boundary and distinguishes it from hosted deployment. The supplied reviewed boundary is sufficient for Radar tracking; Selected-level setup/security completeness and installation readiness are not claimed.

Primarily creative generation; hosted mode adds external data/cost boundary.
Local generation reads parameters and writes/returns generated SVG/PNG assets.
Local engine runs on the user's machine; hosted mode sends generation requests to Creatica.
Reviewed write actions: Generate image assets; Potentially write/export generated files depending on client workflow
Sensitive access: Brand palettes or design parameters if supplied
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
The owner supplied the official-documentation finding without an additional documentation URL; preserve the original npm evidence and supplemental authority rather than inventing a URL or fetch result.
public repository identity
hosted authentication specifics
Local mode does not need an account; hosted mode has separate paid plans.
No exact first-party repository binding was established in this research pass.
Generated output quality depends on generator/schema rather than free-form image synthesis.

Original activity observations

@creatica/mcp 0.1.3 published 2026-09-06T18:05:29.015Z

Technical identity

npm/@creatica/mcp

Exact implementation source: https://www.npmjs.com/package/@creatica/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@creatica/mcp
Service endpoint: api.creatica.app (hosted option)

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@creatica/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
creatica.app/docs
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
creatica.app/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Publisher npm README only confirms local stdio run; detailed docs/MCP.md is not bundled on npm page. Do not assert exact client JSON or authentication until upstream document checked.
Limitation: sparse setup evidence; local run command is not proof of complete client integration.
Earlier review note retained for provenance; the V3 verified fields take precedence: Targeted 2026-10-13 re-research: Publisher says npx -y @creatica/mcp provides local stdio server; minimal package README, advanced options undocumented.
Supported in publisher npm README; confirm local platform/prerequisites and never paste credentials as literals.
MCP100 normalized publisher npm README command/config; placeholders are NOT real secrets; no client/runtime validation.
Prior reviewed safety note: The README points to docs/MCP.md for complete setup, which was not independently fetched in this pass; keep credential or extra command claims unresolved.
Prior reviewed safety note: Do not place orders, spend tokens, modify infrastructure or upload confidential files as a test.
Prior reviewed safety note: Do not invent a one-line reversal command.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
Publisher npm README only confirms local stdio run; detailed docs/MCP.md is not bundled on npm page. Do not assert exact client JSON or authentication until upstream document checked.
publisher install or stdio launch · Publisher instructions
npx -y @creatica/mcp
Configure / authenticate
MCP100 setup guide
Publisher npm registry confirms `creatica-mcp` -> dist/stdio.js and Node >=20. npx runs a local stdio MCP for SVG/PNG backgrounds; no API key in minimal README.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "creatica": { "args": [ "-y", "@creatica/mcp" ], "command": "npx" } } }
Check connection
Suggested check
Inspect MCP tools and test on non-sensitive local sample; full linked docs were not available in publisher package README.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `creatica-mcp`, run `claude mcp remove creatica-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove creatica-mcp

Official Documentation & Sources

What it does

Local-first MCP server for browsing, describing and generating Creatica's procedural backgrounds; same seed produces reproducible output. A hosted API/MCP option exists for permanent URLs.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Deterministic local procedural SVG/PNG background generation for design and build workflows.

Representative uses

Browse available generators and parameter schemas
Generate deterministic SVG/PNG backgrounds
Reuse seeds for reproducible OG cards/backgrounds
Use hosted API for permanent asset URLs

Limitations

Local mode does not need an account; hosted mode has separate paid plans.
No exact first-party repository binding was established in this research pass.
Generated output quality depends on generator/schema rather than free-form image synthesis.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Local generation reads parameters and writes/returns generated SVG/PNG assets.
Data handling: Local engine runs on the user's machine; hosted mode sends generation requests to Creatica.
Cost: free_local_paid_hosted
Risk and cautions: Primarily creative generation; hosted mode adds external data/cost boundary.

Access scope and cautions

Write actions: Generate image assets Potentially write/export generated files depending on client workflow
Sensitive access: Brand palettes or design parameters if supplied
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Browse available generators and parameter schemas; Generate deterministic SVG/PNG backgrounds; Reuse seeds for reproducible OG cards/backgrounds; Use hosted API for permanent asset URLs.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @creatica/mcp. Recorded transport: stdio, http. Prerequisites: Node/npm; MCP client. Client notes: Local install is documented as free. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local mode requires no account; hosted mode uses Creatica account/service.

Can it modify data or perform write operations?

Documented write actions include: Generate image assets; Potentially write/export generated files depending on client workflow. Recorded permission boundary: Local generation reads parameters and writes/returns generated SVG/PNG assets.

What data-handling boundary should I consider?

Local engine runs on the user's machine; hosted mode sends generation requests to Creatica. Recorded sensitive-access context: Brand palettes or design parameters if supplied.

What limitations and risks should I check before use?

Primarily creative generation; hosted mode adds external data/cost boundary. Local mode does not need an account; hosted mode has separate paid plans. No exact first-party repository binding was established in this research pass. Generated output quality depends on generator/schema rather than free-form image synthesis. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is free local paid hosted. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.