
Skia Studio
io.github.lixiaolin94Published by GitHub account lixiaolin94v0.2.1Updated Oct 24, 2026
MCP bridge to a live Skia Studio tab: AGSL/SkSL shader authoring, graph editing, screenshots.
Overview
Local MCP bridge to a live Skia Studio browser tab for AGSL/SkSL shader authoring, graph editing and screenshots.
- What you can do
- Author and edit AGSL/SkSL shaders in a connected Skia Studio tab
- Edit shader graphs in the live studio session
- Capture screenshots of the current shader or graph view
- Connect to a running Skia Studio app over a local WebSocket bridge
- When to use it
- Useful when you work on Skia shaders and want an assistant to drive a running Skia Studio session directly, editing shaders and graphs and checking the visual result, rather than generating shader code blind.
- Requirements
- Runs as a local npm package (skia-studio-mcp) over stdio on a desktop machine, with a Skia Studio app or browser tab available to connect to. Optional environment variables SKIA_STUDIO_APP_URL, SKIA_STUDIO_BRIDGE_PORT (default 8787) and SKIA_STUDIO_EXTRA_ORIGINS adjust the app URL, bridge port and WebSocket origin allowlist. No authentication is declared.
Installation
In SourceWeft
- Open Skia Studio in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.