Your agent’s hands.

A live MCP server that hands PicX generation, assets, and account tools to any MCP client — Claude Desktop, Cursor, or your own agent. No schema wrangling, no glue code.

Choose your client

Setup

  1. Server endpointPoint your client at the PicX MCP endpoint. Root path — no /mcp or /sse suffix.
    HTTPhttps://mcp.picxstudio.com/
  2. Add to configDrop this into your client’s MCP configuration, with a live PicX API key. Get one from the API Keys page in this console.
    Claude Code
    // .mcp.json (project root)
{
  "mcpServers": {
    "picx": {
      "type": "http",
      "url": "https://mcp.picxstudio.com/"
    }
  }
}
// OAuth runs on first connect — no API key in the file.
  3. Verify connectionRestart your client. All 19 PicX tools should appear in its tool list within seconds. Ask it to generate an image to confirm end-to-end — this will spend credits.

Authentication

Two auth planes, one enforcement point. Both resolve to the same /v1 scopes, rate limits, and credit accounting.

OAuth 2.1 + PKCEDefault for hosted clients. No key in your config file — the client opens a browser sign-in the first time it connects, and PicX mints a scoped token. Everyday use in Claude, Cursor, VS Code, Codex.
API key (pxsk_)For developers, CI, and scripted agents. Send Authorization: Bearer pxsk_YOUR_KEY on every request — the same key as the REST API. Get one from the API Keys page in this console. Automation and self-hosted clients.

Claude Desktop

Claude Desktop's config file validates local (stdio) servers only — a remote MCP server dropped there is silently ignored or crashes the app on next launch.

  1. Open Settings → Connectors.
  2. Click Add custom connector.
  3. Server URL: https://mcp.picxstudio.com/
  4. Leave authentication on its default — PicX uses OAuth, so Claude opens a sign-in page on first use. No API key needed.

Available tools

19 tools
picx_generate_imageGenerate a new image from a text prompt using PicX's AI models. Costs credits.
picx_edit_imageEdit one or more existing images with a natural-language instruction. Costs credits.
picx_generate_videoGenerate a video in one of seven modes (text, image, reference, frames, extend, lipsync, edit). Async background task — poll for the result. Costs credits.
picx_get_generationPoll a generation (image or video) by id for status, output URL, and credits used. Free.
picx_list_generationsList past generations for the account, paginated. History endpoint pending — the backing GET /v1/generations has not shipped, so this returns an empty list with a notice until it does. Free.
picx_get_generation_eventsRead a bounded snapshot of one generation's progress-event stream; returns once a terminal event arrives or the timeout is reached. Free.
picx_get_generation_deliveriesList the webhook deliveries that fired for one generation — was its completed/failed webhook delivered, and with what response? Free.
picx_upload_assetUpload a local file to get an HTTPS URL, for use as input to edit/video tools.
picx_list_assetsList uploaded and generated assets in the account.
picx_delete_assetDelete an asset by id.
picx_list_modelsList available generation models and their live credit costs.
picx_search_templatesSearch PicX's catalogue of ~50,000 curated generation templates.
picx_get_templateGet a single template by id.
picx_get_accountGet the authenticated account's profile and credit balance.
picx_get_usageGet usage statistics for the account.
picx_get_tierGet the account's current plan/tier.
picx_get_profileReturn a compact identity profile for the linked account — an opaque account id plus display name and email when available. Used by hosts like ChatGPT to tell multiple linked accounts apart. Free.
picx_get_webhook_deliveriesList the delivery attempts for one webhook endpoint, with each delivery's status and response. Free.
picx_redeliver_webhookRe-send a previously-failed webhook delivery — re-fires the same signed payload as a real outbound POST. Costs no credits.

Frequently asked

Is the PicX MCP server live?Yes. It's in production at https://mcp.picxstudio.com/ — pick a client above, add the config, and it's connected.
Which MCP clients are supported?Any MCP client that speaks Streamable HTTP. Claude Code, Cursor, VS Code and Codex are shown above with exact config; the PicX CLI can install and health-check the connection for you. Claude Desktop connects through its in-app Connectors UI (its config file is stdio-only).
How many tools does the MCP server expose?19 tools, listed below with each tool's name and description. All are always available to any authenticated client — access is controlled by your API key's scopes, the same as the REST API.
How do I authenticate?Two ways. Hosted clients (Claude, Cursor, VS Code, Codex) use OAuth 2.1 with PKCE: no key in your config file — the client opens a browser sign-in the first time it connects. Developers and CI can instead send a direct API key on every request as Authorization: Bearer pxsk_YOUR_KEY, the same key as the REST API. Both converge on the same /v1 enforcement.