About Pixso MCP
MCP (Model Context Protocol) is an open protocol. It provides LLMs with a standardized, secure, and extensible framework to interact with external tools and data sources.
In Pixso, MCP currently has two product forms:
- Local MCP: an MCP service running inside the Pixso desktop client (local service)
- Remote MCP: an MCP service running on Pixso cloud servers (remote service)
Together, they can safely bring design nodes, layout, and assets into AI coding workflows, helping teams move from design to code more efficiently.
Differences: Local MCP vs Remote MCP
Both can provide design context to an Agent, but they differ in how they run and when to use them:
| Dimension | Local MCP | Remote MCP |
|---|---|---|
| Runtime location | Pixso desktop client on the user machine | Pixso cloud server |
| Network dependency | Mainly local loopback (e.g. localhost) | Depends on external/internal network and auth |
| Access design files | Available | Available |
| Edit design files | Available | Available |
| Design To Code | Available | Available |
| Prerequisites | Install and open Pixso desktop; keep the target design file open with its tab active | No need to open Pixso desktop, but operations typically use a layer link |
| Connection | IDE connects to http://127.0.0.1:3667/mcp | Prefer OAuth 2.1; personal access token is also supported |
| Target file | The design currently being edited on this machine | Cloud design file |
| Typical scenarios | Design-to-code, code-to-design, screenshot checks, writing back styles/variables, and canvas edits while viewing the canvas | Remote collaboration, cross-device access, or cases where desktop is inconvenient |
See Local MCP and Remote MCP for setup, and Tools & Commands for tool coverage.