Skip to main content
Glama
10on

schematic-mcp-bridge

by 10on

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_componentsD–
get_componentD–
get_component_pinsD–
create_schematicD–
load_schematicD–
save_schematicD–
add_componentD–
remove_componentD–
set_component_valueD–
connectD–
connect_netD–
disconnectD–
rename_netD–
set_placement_hintD–
set_pin_sideD–
group_componentsD–
auto_layoutD–
validateD–
run_ercD–
render_svgD–
get_previewD–
export_kicadD–

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.7/5.0

Scored across 22 tools

Disambiguation2/5

Several tool pairs overlap in purpose: connect and connect_net both appear to handle wiring, validate and run_erc both check the design, and render_svg and get_preview both produce visual output. Without descriptions, an agent would struggle to choose between these near-duplicates.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern such as search_components, create_schematic, set_component_value, and export_kicad. A few bare verbs like connect, disconnect, and validate, plus auto_layout, deviate slightly but the overall pattern remains predictable.

Tool Count3/5

At 22 tools, the server sits in the heavy range. The count is plausible for a schematic editor workflow, but redundant tools like connect/connect_net and validate/run_erc make the set feel larger than it needs to be.

Completeness4/5

The tool surface covers the core schematic lifecycle: component search/placement, schematic create/load/save, wiring, validation, layout, rendering, and KiCad export. Minor gaps such as explicit component move or net deletion are workable through existing tools like set_placement_hint and disconnect.

Maintenance

ActivitySlowing
ResponsivenessNo issues