jlcpcb-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JLCPCB_DATABASE_PATH | No | Custom path for the SQLite database file. If not set, uses default platform location. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentsA | Search JLCPCB components by keyword with live stock and pricing. This tool searches the local component database and enhances results with real-time stock levels and pricing from JLCPCB's API. Examples:
Results include:
|
| get_component_detailsA | Get detailed information for a specific JLCPCB component. This tool fetches comprehensive details including specifications, current stock, pricing tiers, datasheet, and images. Example: lcsc="C17976" returns full details for that specific component. |
| database_statusA | Get status and information about the local component database. Returns information including database location, size, age, and last update time. |
| refresh_databaseA | Refresh/update the component database to get the latest parts from JLCPCB. This downloads the latest component data (~50MB) and rebuilds the local database. Takes 5-10 minutes. Use this monthly to stay current with new components. |
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 4 tools
Each tool has a clear, distinct purpose: database status, component details retrieval, database refresh, and keyword search. No overlap in functionality.
All tool names use snake_case and consistently follow a verb_noun pattern (e.g., search_components, get_component_details). This provides a predictable naming convention.
With 4 tools, the set is well-scoped for a component search server, covering core operations without being too sparse or excessive.
The tool set covers the primary workflow: searching, getting details, refreshing data, and checking database health. Minor omission like category browsing but core functionality is complete.