Pixso MCP. Manage design files, nodes, and teams via AI.

You need to get info from Pixso's design files, but navigating the UI is a pain in the ass. This server connects your AI client straight into Pixso’s guts, letting your agent treat complex designs like an organized database. You stop clicking through menus and start asking questions.

Listing Assets and Scope
You can get a complete manifest of every file available across your entire workspace using list_files. If you're focused on one project, the server pulls all associated design files for that specific project ID via get_project_files. You can also see what teams are active in your organization with list_teams, or get a rundown of every person who belongs to Pixso overall using get_org_members.

For managing team scope, you'll find details on all current collaboration groups by calling list_team_projects.

Understanding Design Details
When you select a specific file, the server gives your agent access to critical metadata. Use get_file to pull high-level info about any single design asset. You can dive deep into what’s actually in the file: run list_nodes to get a layer-by-layer list of every frame or node structure inside.

For style consistency, your agent pulls the active style library data—colors, typefaces, everything—from a selected design using list_styles. If you need to know who left notes on a specific file, get_comments retrieves all comments made right there in the document.

Tracking Changes and History
You're always dealing with versions. To track milestones for any given design asset, the server provides a full version history log via get_file_versions. This lets you see exactly when changes were saved and who saved them. You can get a list of all available collaboration teams using list_teams to understand where your project fits in.

What Your Agent Does for You
Your agent uses these tools to build context fast. It'll grab the full scope—you can use get_file and then follow up with list_nodes if you want to map out the entire structure of a file. To check style compliance across multiple files, your agent runs list_styles on each asset you point it toward.

If you need to know who's working together, you can pull all project details using get_project_files, and then use get_org_members to see every name attached to the effort.

This means your AI client doesn't just read; it maps out relationships between files, projects, teams, and styles. You don’t have to switch screens or remember which tab has the style guide—your agent handles all that heavy lifting for you.