Connect your agent to PINOC MCP

PINOC MCP is the Model Context Protocol server for PINOC, the 3D creative engine for characters, motion and scenes, built on JST-2. It lets Claude Code, Codex, Cursor or any MCP client build rigged Gaussian splat characters from photos, turn text or video into motion, generate a 3D scene from text or a photo and fill in its missing views, and pull free preset clips, as tools the agent calls on its own.

Games with your own cast: an agent in Claude Code, Codex or Cursor can generate the characters, pull locomotion from the library, capture a signature move from a phone clip and wire it all into a Unity or web project. Already have characters? The motions come as GLB, FBX and USDZ, so they drive your own rigged meshes too. It also fits animating scenes in Blender and Unreal, blocking out NPCs and cutscenes, 3D avatars for web apps, and previs.

The Model Context Protocol is an open standard that lets an AI agent call a service's tools directly, instead of you copying results back and forth by hand.

No. Your MCP client registers itself with PINOC and opens a Google sign-in in your browser. The agent never touches it.

Any MCP client that speaks the protocol over HTTP, including Claude Code, Claude Desktop, Codex and Cursor. The same prompt works in all of them.

Browsing, taking library clips, handing over a file, looking things up and finding what a scene is missing are all free. Only the tools that generate something new (a character, a motion, a scene or a fill for one) spend credits, from the same balance as the app.

Yes. Your agent asks PINOC for a one-time upload link and sends the one file you named. It never browses your disk, and PINOC keeps the upload for a day. From a description in words it can generate with no file at all.

Two tick boxes on PINOC's own consent screen. "Read (free)" covers everything that only looks things up. "Write (uses credits)" covers making new motions, characters and scenes, and handing PINOC a file to make them from. Both start ticked; untick the second to connect read-only.

Your agent asks PINOC for a download link, fetches the file and saves it where you are working, the same place it writes anything else for you. The links expire, so it fetches at the moment you ask rather than handing you one to keep.

GLB and FBX open anywhere: Unity, Blender, Unreal, or any glTF or FBX tool. Motions also come as USDZ, for Apple's AR Quick Look. Splat characters (.vsplat) are not meshes and only render through the Viggle Splat Engine, as a Unity package or an npm package for the web. A scene is one Gaussian splat file (.spz, or .ply for older ones), also not a mesh, so it needs a splat renderer such as the Splat Engine. Every asset also previews and edits in PINOC itself. Get the Splat Engine on the plugin page

Those let an agent drive the software you already have open. PINOC MCP gives it something to put in there: motion clips as GLB and FBX, and Gaussian splat characters that play them in Unity or on the web. An agent connected to both can make a motion here and apply it in your scene there.