LTspice MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONIOENCODING | No | Sets the Python I/O encoding for the server, typically set to utf-8. | utf-8 |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gestionar_simulacion_ltspiceC | Guarda y simula un circuito en su propia carpeta. |
| buscar_componente_en_libreriaC | Busca componentes en la biblioteca de LTspice. |
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 2 tools
The two tools have clearly distinct purposes: one searches for components in the LTspice library, while the other manages simulation by saving and simulating circuits in a folder. There is no overlap in functionality, making them easy to differentiate.
Both tools use Spanish snake_case naming, which is consistent in style. However, the verb choices differ ('buscar' vs. 'gestionar'), and the naming pattern is not perfectly uniform (e.g., one includes 'en_libreria' while the other specifies 'ltspice'), leading to some inconsistency in structure.
With only two tools, the server feels under-scoped for an LTspice domain, which typically involves tasks like circuit creation, component placement, parameter setting, and analysis. This limited set may not cover essential operations, making it too few for the apparent scope.
The tool set is severely incomplete for LTspice functionality. It lacks core operations such as creating or editing circuits, setting simulation parameters, running analyses (e.g., transient, AC), and viewing results. The existing tools cover only library search and basic simulation management, leaving significant gaps that will hinder agent workflows.