easyeda-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| session.statusA | Return the local EasyEDA MCP bridge status and connected editor windows. |
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 1 tool
With only one tool, there is no possibility of confusing it with another. The name 'session.status' clearly indicates it provides status information about the EasyEDA bridge session.
The single tool name 'session.status' is clear and follows a namespace-like convention. While it doesn't follow the typical verb_noun pattern, consistency is trivially satisfied with only one tool, and there is no internal inconsistency.
The server name 'easyeda-mcp' suggests a broader purpose, but with only one status-checking tool, it is far too minimal for the apparent scope. One tool is insufficient to interact with EasyEDA in any meaningful way.
The server provides only a status endpoint with no tools to perform actual operations on EasyEDA projects, files, or editor windows. It is severely incomplete for its intended domain.