MCP server for Spline.design code generation and asset management
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"spline-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# spline-mcp [](https://github.com/lesleslie/crackerjack) [](https://github.com/lesleslie/oneiric) [](https://github.com/PrefectHQ/fastmcp) [](https://github.com/astral-sh/uv) [](https://www.python.org/downloads/) MCP server for [Spline.design](https://spline.design) code generation and asset management. ## Overview Spline.design is a 3D design tool that exports interactive scenes for the web. This MCP server provides: - **Code Generation**: Generate React, Next.js, and vanilla JS integration code - **Asset Management**: Download, cache, and validate `.splinecode` files - **Integration Support**: WebSocket event sink - **Helper Utilities**: URL building, event documentation, code snippets > **Note**: Spline does not have a traditional REST API. Scenes are created in the Spline editor and exported as `.splinecode` files for runtime use. ## Spline V2 Compatibility Spline V2 (released August 20, 2026) ships its own MCP server inside the rebuilt Spline desktop app that lets AI agents drive the editor directly — creating and modifying objects, materials, lights, cameras, booleans, particles, cloners, lathes, sky, variables, events, and states. See the [Spline V2 launch announcement](https://blog.spline.design/spline-v2) for details. This server fills a **different, complementary niche**: | Workflow stage | Tool | |---|---| | **Authoring** — building / editing the scene in the editor | [Spline V2 MCP](https://blog.spline.design/spline-v2) (bundled with the Spline desktop app) | | **Embedding** — putting the exported scene into your React / Next.js / v…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.