Spline MCP Server

Created By
aydinfera year ago
An MCP server for working with Spline 3D design tool API
Overview

what is Spline MCP Server?

Spline MCP Server is a server designed to work with the Spline 3D design tool API, providing a convenient interface for users to interact with Spline's features such as exporting scenes, importing models, creating animations, and managing projects.

how to use Spline MCP Server?

To use Spline MCP Server, install it via npm or npx, and configure your Spline API credentials in a .env file. You can then use it to perform various operations with Spline's API.

key features of Spline MCP Server?

  • Export Spline scenes to multiple formats (GLB, GLTF, FBX, OBJ)
  • Import 3D models into Spline
  • Create and manage animations for objects
  • Retrieve details and list available Spline scenes

use cases of Spline MCP Server?

  1. Exporting 3D scenes for use in other applications.
  2. Importing external 3D models into Spline for further editing.
  3. Creating interactive animations for web applications.

FAQ from Spline MCP Server?

  • What formats can I export my Spline scenes to?

You can export to GLB, GLTF, FBX, and OBJ formats.

  • How do I install Spline MCP Server?

You can install it using npm with npm install spline-mcp-server or directly with npx spline-mcp-server.

  • Do I need an API key to use Spline MCP Server?

Yes, you need to create a .env file with your Spline API credentials.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aydinfer
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago