Other · Remote MCP server
Backgrounds
Deterministic procedural SVG/PNG backgrounds: 58 generators, curated palettes, brand kits.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.creatica/backgrounds- Version
- 0.1.3
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-06
- Updated
- 2026-09-06
- Publisher
- app.creatica
- Namespace
- Namespace verified by the MCP Registry via the domain creatica.app · how
- Website
- creatica.app
- Repository
- github.com/anup-a/web-backgrounds
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.creatica.app/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- creatica-backgrounds 0.1.0 · protocol 2025-06-18
- Tools discovered
- 6:
list_backgrounds,suggest_backgrounds,describe_background,list_palettes,list_brand_kits,generate_background - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @creatica/mcp | 0.1.3 | stdio |
How to connect Backgrounds
Backgrounds is a remote MCP server: there is nothing to install. Its endpoint is https://api.creatica.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @creatica/mcp version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @creatica/mcp@0.1.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"backgrounds": {
"command": "npx",
"args": [
"-y",
"@creatica/mcp@0.1.3"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Babelwrap MCPLet AI agents interact with any website through natural language instead of CSS selectors. | Local · stdio |
| Baby AgeFree hosted MCP server by Baby Age Calculator: exact baby age, zodiac, and milestone dates. No key. | Remote · HTTPLive check: ✓ handshake |
| Backblaze B2 MCP ServerOfficial Backblaze B2 MCP server for buckets, files, keys, Object Lock, and S3 storage. | Local · stdio |
| BackBond Agent ScanVet MCP tool manifests before attachment; returns block, review, or no blocking finding. | Local · stdio |
| Backlinkmcp ServerBacklink & domain authority MCP for AI agents: referring domains, link gap, toxic review queue. | Remote · HTTPLive check: ✓ handshake |
| BacklinksbeheerRead existing backlink records and dated check results in your own account. | Remote · HTTPLive check: sign-in required |
| BackPow PoW OracleProof of Work oracle: solo mining odds, cost of production, hashrate, mining hardware. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Backtest Cost SensitivityCommission/slippage sensitivity sweep, breakeven cost finder, and lookahead-bias checklist. | Remote · HTTPLive check: sign-in required |