User guides

MCP connection and troubleshooting

For Remote MCP, configure https://pixso.net/mcp with OAuth and provide the target layer link. For Local MCP, keep Pixso desktop running with the target file active. The checks below apply to the connection mode you use.

What can Pixso MCP access?

MCP tools can read design nodes, styles, variables and components, capture screenshots and support design-to-code or design-editing tasks. Read and write tools have different requirements. See the English tools and commands reference for the supported operations and permissions.

Connected, but unable to read the design

  1. Open the file in Pixso using the authorized account and confirm access.
  2. For Remote MCP, provide a layer or frame link with its node information.
  3. Check the account’s seat and file permission. Write operations require editing access.
  4. For Local MCP, keep the target file tab active and select the intended layer if the task uses the current selection.

Code generation fails or needs adjustment

D2C⁺ requires the enterprise seat and space conditions described in the English D2C⁺ quick start. Once access is available, select a clear page or frame and specify the target framework and component library. Process complex designs in smaller sections, then compare layout, text, assets and interaction states with the source.

The agent has no MCP entry or cannot connect

Use an agent version that supports Streamable HTTP. Follow that client’s configuration format and complete authorization. Remote MCP supports OAuth and personal access tokens; keep tokens out of public repositories, screenshots and shared prompts. Private deployments use their own service URL.

There is no MCP entry in Pixso desktop

Remote MCP is configured in the agent and does not require a desktop entry. For Local MCP, update Pixso desktop to version 2.2.0 or later, open a design file and use the MCP configuration entry at the top left.

Local MCP is enabled but calls fail

Copy the current service address from Pixso; the port may differ from 3667. Use HTTP / Streamable HTTP rather than SSE. Keep one local MCP provider active to reduce port conflicts, and keep the target file open and active. Complete steps are in the English Local MCP guide.