MCP Alpha
Let your AI coding agent — Claude Code, Codex or Grok — drive 360 Hextile on your own NVIDIA GPU. Alpha — in active development, not fully tested.
Getting started
Connect your agent
Start the agent in any folder while Hextile is open at 127.0.0.1:8000. Needs Git and Python 3.9+ (as python3).
Before you start, turn on MCP in 360 Hextile's Settings. It's off until you do. A connected agent is fully trusted: it can use the app's tools, settings and task file paths without separate grants.
Explore 360 Shaders-
Choose your agent
-
InstallOnce
/plugin marketplace add ansonphong/360-HEXTILE-PLUGINS/plugin install 360-hextile@360-hextileRun in Claude Code, restart it, then run /mcp to check hextile.
codex plugin marketplace add ansonphong/360-HEXTILE-PLUGINScodex plugin add 360-hextile@360-hextileRun in a terminal with a current Codex CLI, restart it, then run /mcp to check hextile.
grok plugin marketplace add ansonphong/360-HEXTILE-PLUGINSgrok plugin install 360-hextile --trustgrok plugin enable 360-hextileRun in a terminal, then reload with r in /plugins or start a new session.
-
Start a sessionEvery session
Paste it into your agent.
/360-hextile connect and look at what I'm working on -
Shader starters
Pick a brief, copy it into your agent, then fill in the [brackets].
Fly down a tunnel or corridor
/360-hextile Create a new Shader: an animated tunnel flight. Look and mood: [describe the tunnel]. Read the Shader cookbook index (get_guide, name "shader-cookbook"), then read that same guide with detail=true for the full content and use these cards from it: tunnel-flight, repetition, sphere-trace, clock-pose. Adapt their generalized techniques rather than copying anything literally. If the cookbook isn't available, tell me and carry on with the native Shader guidance you have. Use the native Shader workspace and the app's checks, report what they say instead of assuming it compiles, and leave Save to me.Glide over terrain with fog and light
/360-hextile Create a new Shader: a landscape flythrough. Look and mood: [describe the landscape]. Read the Shader cookbook index (get_guide, name "shader-cookbook"), then read that same guide with detail=true for the full content and use these cards from it: landscape-flythrough, heightfield, clock-pose, palette-fog-light. Adapt their generalized techniques rather than copying anything literally. If the cookbook isn't available, tell me and carry on with the native Shader guidance you have. Use the native Shader workspace and the app's checks, report what they say instead of assuming it compiles, and leave Save to me.Place or warp a still image on the sphere
/360-hextile Create a new Shader: an image effect on the sphere. Image and effect: [describe the image and what should happen to it]. Read the Shader cookbook index (get_guide, name "shader-cookbook"), then read that same guide with detail=true for the full content and use these cards from it: still-on-sphere, still-image, coordinates. Adapt their generalized techniques rather than copying anything literally. If the cookbook isn't available, tell me and carry on with the native Shader guidance you have. Use the native Shader workspace and the app's checks, report what they say instead of assuming it compiles, and leave Save to me.A scene I can fly through interactively
/360-hextile Create a new Shader: a playable scene I can steer. Scene: [describe the world and how it should feel to fly]. Read the Shader cookbook index (get_guide, name "shader-cookbook"), then read that same guide with detail=true for the full content and use these cards from it: playable-flight, playable-pose, sphere-trace. Adapt their generalized techniques rather than copying anything literally. If the cookbook isn't available, tell me and carry on with the native Shader guidance you have. Use the native Shader workspace and the app's checks, report what they say instead of assuming it compiles, and leave Save to me.A new Shader from a visual idea of mine
/360-hextile Create a new Shader from my idea: [describe what it should look like and how it moves]. If the Shader cookbook (get_guide, name "shader-cookbook") has a relevant card, adapt its technique. If it isn't available, tell me and carry on with the native guidance you have. Use the native Shader workspace and the app's checks, report what they say instead of assuming it compiles, and leave Save to me.
What you can do
Ask in plain words. Your agent calls the same Workflows you run in the studio.
-
Build 360° shaders
Describe a look. Your agent builds a 360° shader with controls you can tune.
Explore 360 Shaders -
Render worlds from Workflows
Your agent runs the same Workflows you open in the studio. The render happens in the app, on your GPU.
See Worlds -
Make 360 LoRA seeds
Ask for a few seed variations with a 360 LoRA, then render the one you like.
See 360 LoRA -
Check progress and stop jobs
Ask what is running and how far along it is, or stop a job.
How it works
Your agent
Claude Code, Codex or Grok, where you type what you want.
360-hextile plugin
The small local bridge you installed in step 2.
360 Hextile on your GPU
The app must be open. It does the work on your NVIDIA GPU.
The render runs in the app on your machine. Nothing is uploaded to a 360 Hextile render queue. This is separate from the in-app Copilot.
For developers tools · requirements · curl
Package
360-hextile is a stdio MCP server plus skills for Workflows, Shader, Fractal, upres and the Pipe studio matte tools. It is a thin python3 proxy to 127.0.0.1:8000. Merge, validate and render stay in the running app. github.com/ansonphong/360-HEXTILE-PLUGINS is both the public package source and the marketplace. The MCP package is MIT.
Tools
Public tool inventories vary by release channel, and the running app is the system of record. Start with get_capabilities, and use get_guide for live guidance.
| Capability | Stable examples |
|---|---|
| Discover and manage Workflows | list_workflows · get_workflow · save_workflow |
| Validate and run | validate_config · run_workflow |
| Monitor and control runs | get_status · list_runs · cancel_run |
| Create and inspect seeds | generate_seed · list_360_loras · list_seed_history |
| Inspect capabilities and guidance | get_capabilities · list_installed_models · get_guide |
This is a capability map, not an exhaustive tool list. Batch workflow tools visible in local APP development are disabled by default and are not part of the released public package or marketplace promise.
Requirements
- 360 Hextile running on this machine. MCP talks to the local app, not a cloud queue.
- Windows + NVIDIA CUDA.
- python3 ≥ 3.9 on PATH, stdlib only, zero pip. On Windows, a Claude .mcp.json command should be python or py -3, not python3.
- An app build with POST /api/workflows/run. Older builds return an upgrade error.
- Codex ≥ 0.34.0 without plugin support: use the manual installer plugins/360-hextile/codex/install.py in the repository.
- Local checkout of the plugins repository? Swap the marketplace slug for /path/to/360-HEXTILE-PLUGINS.
- If a tool says the app is down, launch 360 Hextile, then retry. The MCP process stays up.
The MCP connection is opt-in and off by default. A connected agent can use native tools, settings and task file paths without separate grants. Disconnect blocks new work; admitted exports finish. Stop cancels the named job.
No python3? Use curl
Same endpoints, same machine.
curl -s http://127.0.0.1:8000/api/workflows
curl -s -X POST http://127.0.0.1:8000/api/workflows/run \
-H 'Content-Type: application/json' \
-d '{"workflow_id":"quick-scout","origin":"builtin","dry_run":true}'
Facts
- Protocol
- MCP (Model Context Protocol) · stdio only
- Package
- 360-hextile · public source · MIT
- Clients
- Claude Code · Codex ≥ 0.34.0 · Grok · any MCP client
- Where work runs
- Your NVIDIA GPU, in the running app
- What the agent opens
- The same .hextile.json Workflow the studio uses
Work on your own GPU
One-time licence from $180. No subscription, no per-render cloud charge.
30-day money-back guarantee on every purchase.