speckle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECKLE_TOKEN | Yes | Your Speckle personal access token (from Profile -> Personal Access Tokens) | |
| SPECKLE_SERVER | No | Speckle server URL (default: app.speckle.systems) | app.speckle.systems |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| speckle_projects_listB | List all accessible Speckle projects for the authenticated user. Projects are top-level containers that hold models. |
| speckle_project_detailsA | Get detailed information about a Speckle project, including its models and team members. |
| speckle_project_createB | Create a new Speckle project to organize models shared across your team. |
| speckle_models_listA | List all models in a Speckle project. Models hold versioned BIM/CAD data from connectors. |
| speckle_model_detailsA | Get detailed model info including full version history with author, date, and commit messages. |
| speckle_model_createA | Create a new model within a Speckle project, organized by discipline (Architecture, Structure, etc.). |
| speckle_send_instructionsA | Get connector-specific instructions for sending BIM data to Speckle. Returns guidance for Revit, Rhino, AutoCAD, etc. Does NOT transfer data — use native Speckle connectors for actual data push. |
| speckle_receive_instructionsA | Get version info and instructions for receiving Speckle data into BIM applications or Python. Does NOT pull objects — use native connectors or specklepy operations.receive() for data retrieval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource (project vs model) and action (list/details/create), with send/receive instructions clearly separated. No two tools overlap in purpose; descriptions clarify any potential confusion between list and details.
All tools use a 'speckle_' prefix with resource and action, but pluralization is inconsistent (e.g., speckle_projects_list vs speckle_project_details) and the instruction tools use a verb-first pattern (speckle_send_instructions, speckle_receive_instructions). Overall pattern is readable and predictable.
8 tools is well-scoped for a server focused on project and model management plus data transfer instructions. Each tool serves a clear purpose without redundancy or excessive bloat.
The set provides create, list, and details for both projects and models, but lacks update and delete operations, leaving the lifecycle incomplete. Actual data transfer is not included, only instructions, which is a noted gap but perhaps intentional given the description.