Use with AI Agents
Connect MeshRoom to Claude Code, Claude Desktop, Cursor, or any other MCP-capable agent - as a remote MCP server, or as an installable skill your agent reads on its own.
Overview
There are three ways an agent can work with MeshRoom, from least to most setup:
1. llms.txt
Every agent that reads /llms.txt already knows how to use the REST API - zero install.
2. Agent Skill
An installable SKILL.md with the full API reference baked in, so your agent doesn't need network access to figure it out.
3. MCP Server
A live /api/mcp endpoint exposing typed tools - the richest integration, if your agent supports remote MCP servers.
MCP Server
MeshRoom runs a remote MCP server (Streamable HTTP transport) at https://webassets.art/api/mcp, authenticated with the same API key as the REST API. It exposes four tools:
| Tool | Does |
|---|---|
| generate_asset | Create a 3D model, animation, or ASCII art asset from a prompt (async - returns an id to poll) |
| check_generation | Poll a generation started by generate_asset until it completes |
| pixelize_website | Brand Pixelizer - turn a URL into 4 themed pixel-art animations (synchronous) |
| get_credits | Check the authenticated user's remaining credit balance |
Quick setup for Claude Code - one command, run in your terminal (swap in your own key from /dashboard/api-keys):
For any other MCP-capable client, add it to your MCP config with your API key as a header:
For stdio-only clients that can't connect to a remote server directly, bridge it with mcp-remote:
Agent Skill
An Agent Skills-compatible SKILL.md is published at /skills/meshroom-assets/SKILL.md. It documents the same REST API as this page in a form your agent reads directly - useful for agents without MCP support, or that work better with instructions checked into a repo.
Paste this to your agent, or run it yourself - one command, no separate mkdir/mv step needed:
Swap .claude/skills for your agent's own skills folder (e.g. .cursor/skills, .codex/skills for project scope, or the matching ~/.<agent>/skills path for a global install) - the skill spec is shared across agents, only the folder changes.
llms.txt
MeshRoom also publishes a plain /llms.txt - the emerging convention agents check by default when browsing a site, covering the same setup steps and endpoints in a lighter format. Useful as a fallback if an agent hasn't installed the skill or configured the MCP server yet.