mouser-search-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mouser-search-mcp
Model Context Protocol server for the Mouser Electronics Search API.
Exposes the Mouser Search API as MCP tools so MCP-aware clients (Claude Code, Claude Desktop, etc.) can query Mouser's parts catalog.
Tools
Tool | Endpoint | What it does |
|
| Keyword search across the catalog (up to 50 parts). Supports paging and RoHS/in-stock filters. |
|
| Look up 1–10 part numbers (pipe-separated), with optional exact-match. |
|
| Keyword search scoped to one manufacturer by name. |
|
| Part-number lookup scoped to one manufacturer by name. |
|
| Enumerate manufacturer names (use the result to populate the |
Related MCP server: DigiKey MCP Server
Prerequisites
Python 3.10+
A Mouser Search API key — request one at https://www.mouser.com/api-search/.
Install
Using uv (recommended):
uv pip install -e .Or with pip:
pip install -e .Configure
The server reads the API key from the MOUSER_API_KEY environment variable. Copy .env.example to .env and fill in your key, or export it in your shell.
Run
The server speaks MCP over stdio:
MOUSER_API_KEY=... mouser-search-mcpUse with Claude Code
Register the server (replace the path and key):
claude mcp add mouser-search \
--env MOUSER_API_KEY=your-key \
-- mouser-search-mcpUse with Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"mouser-search": {
"command": "mouser-search-mcp",
"env": {
"MOUSER_API_KEY": "your-key"
}
}
}
}If mouser-search-mcp is not on your PATH, point command at the absolute path to the script (e.g. inside your venv's bin/).
Notes
Mouser returns at most 50 records per search response. Use
records+starting_record(v1 keyword search) orrecords+page_number(v2 keyword+manufacturer search) to page.search_optionsacceptsNone,Rohs,InStock, orRohsAndInStock— only one at a time.part_search_optionsacceptsNoneorExact.The cart and order endpoints documented by Mouser require an Ordering API key and are not exposed by this server — it covers search only.
Releasing
Versioning and releases are fully automated by python-semantic-release. Every push to main runs .github/workflows/release.yml, which:
Inspects commits since the last tag.
Decides the next version (or does nothing if no release-worthy commits).
Updates
versioninpyproject.toml, generates the changelog, commits, and pushes avX.Y.Ztag.Builds wheel + sdist and uploads them to PyPI.
Creates a GitHub Release with auto-generated notes.
Commit grammar
Commits must follow Conventional Commits. The leading keyword decides the bump:
Prefix | Bump | Example |
| minor |
|
| patch |
|
| patch |
|
| major |
|
| none | (no release cut) |
Anything else is ignored. If you push a flurry of small commits, semantic-release collapses them into a single release on the next workflow run.
One-time setup
These steps need to be done once in the GitHub UI before the workflow can publish:
PyPI account + token — create a PyPI account, then on the API tokens page generate an account-scoped token (the project doesn't exist on PyPI yet, so it can't be project-scoped on the first release; re-scope it to
mouser-search-mcpafter the first successful publish).Repo secret — in GitHub: Settings → Secrets and variables → Actions → New repository secret, name
PYPI_API_TOKEN, paste the token value.Workflow permissions — Settings → Actions → General → Workflow permissions must be set to Read and write permissions so semantic-release can push the version bump commit and tag.
After that, just merge to main with a feat: or fix: commit and the rest happens automatically. To skip a release, use a non-bumping prefix (docs:, chore:, etc.) or include [skip ci] in the commit message.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Search multi-merchant supply, checkout, and track orders via MCP.
Find electronic parts with live Mouser, DigiKey and JLCPCB stock and prices, check BOMs, order.
Unofficial GunBroker MCP Pack — wraps the GunBroker firearms-marketplace API.
SerpApi MCP — wraps SerpApi (serpapi.com) search engines
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to the DigiKey Product Search API v4, allowing users to search for electronic components and retrieve detailed product specifications. It supports keyword searches, pricing inquiries, manufacturer lookups, and access to technical datasheets.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving product information from DigiKey's API, including part lookup, keyword search, product details, and pricing.-
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server for the Mouser Electronics API. Enables searching electronic components, managing shopping carts, and tracking orders directly through Claude or other MCP clients.95MIT
- AlicenseAqualityDmaintenanceSearches electronic components across DigiKey and Mouser, enabling keyword search, part details, and merged offers with price comparison.41MIT