Hosted MCP · no npm

Connect once. Create website artwork from Codex or Claude.

Designelier runs at https://mcp.designelier.com/mcp. Add the hosted server, sign in to your Designelier account in the browser, and plan a coordinated artwork pack from one public website URL—without copying API keys or moving base64 artwork through the conversation.

Supported clients

Two current command-line setup paths.

Run the command for your client. The first half stores the hosted MCP connection; the second starts browser OAuth for the Designelier account you want that client to use.

Codex CLI

Add the hosted server and sign in

codex mcp add designelier --url https://mcp.designelier.com/mcp && codex mcp login designelier

Syntax checked with codex-cli 0.147.0 on 9 August 2026.

Claude Code

Add at user scope and sign in

claude mcp add --transport http --scope user designelier https://mcp.designelier.com/mcp && claude mcp login designelier

Syntax checked with Claude Code 2.1.220 on 9 August 2026. Prefer the browser connector UI? Open the pre-filled connector →

Browser OAuth

Review the account and permissions before allowing access.

Sign in

The login command opens Designelier in your browser. Sign in or create an account, then return to the connection request.

Check the client

The consent screen names the connecting client, shows where authorization returns, and lists the requested Read and Generate permissions.

Allow or deny

Read can view your credit balance and pack progress. Generate can plan packs and confirm quoted generation that spends credits, so allow only clients you trust.

Return to the client

After approval, OAuth returns to the client and the Designelier tools become available. The client never needs your Designelier password or a copied API key.

Example workflow

Plan first. Inspect the quote. Confirm deliberately.

Example prompt

Ask for a plan without authorizing a spend

Use Designelier to plan an artwork pack for https://example.com. Show me the pack ID, current state, and exact credit quote. Do not confirm generation or spend credits until I explicitly approve the quoted amount.

Replace the example with a public HTTP or HTTPS page you control. This prompt illustrates the supported workflow; it is not a claim that a pack was generated for example.com.

Available tools

One account check and a three-step pack flow

designelier_get_account reads total, reserved, and available credits.
designelier_plan_pack analyzes one public URL and creates a free plan and quote.
designelier_get_pack reads or briefly polls planning and generation state.
designelier_confirm_pack confirms the exact current quote and can spend credits on success.

Permissions and credits

The Generate permission can spend credits.

Planning is free. Before confirmation, the pack response includes an immutable quote ID, exact credit amount, and expiry. The hosted server instructs the client to show that quote and ask before calling the confirmation tool. Confirmation reserves the exact amount; credits are charged only when generation succeeds, and a failed generation releases the reservation. Because the initial OAuth grant lets a trusted client make that confirmation without another Designelier approval screen, review the client and scopes carefully.

Expected output

A stateful pack resource, then verified files.

Before generation

Pack identity and exact quote

Planning returns the pack ID, name, source URL, current state, timestamps, and the exact quote needed for confirmation. States can move through queued, analyzing, awaiting confirmation, generating, succeeded, or failed.

After success

Manifest plus a five-minute archive URL

A successful status response lists each SVG asset's relative path, media type, byte size, and SHA-256 digest. It also provides a five-minute verified ZIP URL with its own size and digest. Artwork is not embedded as base64 in the MCP response. Exact scenes and quoted credits depend on the analyzed page.

Security and privacy

Send public page context, never private access material.

Source URL boundary

The planner accepts a public HTTP or HTTPS URL without embedded credentials or a fragment. Do not provide private pages, signed download URLs, tokens, cookies, passwords, OAuth state, or secrets in the URL or prompt.

Connection boundary

MCP authorization is tied to your Designelier account and the granted scopes. Only approve clients and return origins you recognize. Review the current quote again if it expires or changes before confirmation.

See the Privacy Policy for the service's data handling.

Troubleshooting

Resolve setup, access, quote, and download errors.

The command or option is not recognized

Run codex mcp add --help or claude mcp add --help and use a current client version that supports hosted HTTP servers. Re-run the complete setup command after updating the client through its official distribution channel.

The browser did not open

Re-run the login half of the command. On a headless Claude Code session, use claude mcp login --no-browser designelier and follow the printed authorization flow.

The page cannot be analyzed

Confirm that the URL is public, reachable over HTTP or HTTPS, and contains no username, password, or fragment. Remove signed or private URLs rather than sharing their access material.

The quote expired or does not match

Ask the client to read the pack again and show the current quote ID and credit amount. Confirm only that exact pair. If credits are insufficient, add credits in Studio before retrying confirmation.

Generation is still running

Ask the client to check the pack again. One status call can wait for up to 60 seconds; longer jobs can be checked with another status request without confirming twice.

The ZIP URL expired

Read the succeeded pack again to receive a fresh five-minute verified download URL. Compare the returned byte size and SHA-256 digest when handling the archive.

REST API alternative

Use the same explicit plan-and-confirm model in your own code.

If your automation is not an MCP client, use a Studio API key with Designelier's REST API. It exposes account, planning, status, exact-quote confirmation, individual asset, and verified archive endpoints. Send the key only in the Authorization header to app.designelier.com, never in a URL.

Human-readable quickstart

Follow the request sequence, lifecycle states, curl examples, and error contract.

Read the REST API guide →

Machine-readable contract

Use the public OpenAPI 3.1 document and create or revoke keys in Studio.

OpenAPI JSON → · Sign in for API keys →

Compatibility · checked 9 August 2026

Supported connection paths and verification status.

Client	Connection	Authentication	Verification
Codex CLI 0.147.0	Hosted HTTP MCP with `--url`	`codex mcp login` browser OAuth	Add and login syntax checked locally
Claude Code 2.1.220	HTTP transport at user scope	`claude mcp login` browser OAuth	Add, login, and headless-login syntax checked locally
Claude custom connector	Hosted MCP URL through the connector UI	Browser OAuth	Pre-filled setup path documented; no local CLI command

Command syntax was verified against installed client help. This check did not spend credits or claim a newly generated production pack.

FAQ

Hosted MCP basics.

Does the Designelier MCP require npm or an API key?

No. The supported MCP is hosted over HTTPS and connects to your Designelier account with browser OAuth. There is no customer-side MCP package to install and no API key to paste into the client.

Does planning an artwork pack spend credits?

No. Planning analyzes one public website URL and returns a pack ID and exact quote without spending credits. Confirmation reserves the quoted amount, and those credits are charged only if generation succeeds.

Which URLs can Designelier analyze through MCP?

Use a public HTTP or HTTPS page without embedded credentials or a URL fragment. Do not submit private pages, signed URLs, tokens, OAuth state, or other secrets.

What does a successful MCP generation return?

The status response includes a verified SVG asset manifest and a short-lived verified ZIP download URL. Designelier does not place base64 artwork payloads in the MCP response.

Can I automate the same workflow without an MCP client?

Yes. The REST API provides account, planning, status, exact-quote confirmation, asset, and archive endpoints using a Studio API key.