Spline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPLINE_API_KEY | Yes | Your Spline API key | |
| SPLINE_API_URL | No | The Spline API URL | https://api.spline.design |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-cube | |
| create-basic-scene | |
| create-apply-material | |
| create-rotation-animation | |
| create-color-change-interaction | |
| create-api-interaction | |
| create-interactive-scene | |
| create-animation-sequence | |
| create-react-integration |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 73 tools
The tools cover distinct aspects of 3D scene creation and management, but there's significant overlap in configuration tools (e.g., configureApi vs configureApiRequestAction) and creation tools (createEvent vs createComprehensiveEvent). Without descriptions, it's unclear how these differ, leading to potential confusion for agents trying to select the right tool.
Most tools follow a consistent verb_noun pattern (e.g., addCamera, createObject, getMaterials), with clear action prefixes like add, create, configure, get, delete, update, generate, and list. Minor deviations exist (e.g., exportSceneCode vs generateEmbedCode), but the overall naming is predictable and readable.
With 73 tools, this is an extremely large set that feels overwhelming for a single server. While 3D scene creation is a complex domain, the high count suggests fragmentation or redundancy, making it difficult for agents to navigate and increasing the risk of misselection.
The tool set appears to cover a comprehensive range of operations for 3D scene management, including creation, configuration, retrieval, updating, and deletion of objects, materials, events, APIs, and more. There's good CRUD coverage (e.g., createObject, getObjects, updateObject, deleteObject), though some gaps might exist in specific subdomains like animation or physics.