search_by_keywordLABSCO SUMMARY
Parts lookup where the design conversation is.
Sourcing questions interrupt design work because they live in a browser tab. This answers them in place — keyword or part number, filtered to what is in stock and RoHS-compliant, scoped to a manufacturer when that is what matters.
What it is
A client for the Mouser Electronics Search API. Keyword and part-number searches run on their own or scoped to a single manufacturer, and the manufacturer list is queryable so the scoping argument is a real name.
What you get
- Keyword search across the catalogue, up to 50 parts, with paging and RoHS or in-stock filters
- Lookup of 1–10 part numbers at once, pipe-separated, with optional exact match
- Both of those searches scoped to one manufacturer by name
- The manufacturer list, which supplies the name those scoped tools expect
Requirements
Python 3.10+ and a Mouser Search API key in MOUSER_API_KEY, requested from Mouser. Responses cap at 50 records, so larger result sets are paged. The cart and order endpoints need a separate Ordering API key and are not covered here.
Setup effort
Build from source — git clone https://github.com/cmaurer/mouser-search-mcp
USE CASES
01
Checking a part is still available
Look the part number up directly with exact match on, and read availability off the result.
02
Finding an alternative for something out of stock
Keyword search with the in-stock filter applied, so what comes back can actually be bought.
03
Staying with one manufacturer
Take the manufacturer's exact name from the list, then search inside it by keyword or by part number.
04
Checking a BOM in one pass
Up to 10 part numbers per call, pipe-separated, rather than one lookup per line.
05
Working through a broad search
Results cap at 50 per response, so a wide keyword is paged deliberately instead of arriving truncated.
5 tools
Listed in project docs. Your client may show a different list.
search_by_part_numbersearch_by_keyword_and_manufacturersearch_by_part_number_and_manufacturerlist_manufacturersBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- Python 3.10+
- uv on PATH
- MOUSER_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/cmaurer/mouser-search-mcp
cd mouser-search-mcp
uv venv
uv pip install -e .MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add mouser-search --env MOUSER_API_KEY=<YOUR_MOUSER_API_KEY> -- <YOUR_PATH_TO_MOUSER_SEARCH_MCP>/.venv/bin/mouser-search-mcp<YOUR_PATH_TO_MOUSER_SEARCH_MCP> is the absolute path to your clone, and <YOUR_MOUSER_API_KEY> is your Mouser Search API key. The install puts the mouser-search-mcp command inside the clone's .venv, not on your PATH.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mouser-search": {
"command": "<YOUR_PATH_TO_MOUSER_SEARCH_MCP>/.venv/bin/mouser-search-mcp",
"env": {
"MOUSER_API_KEY": "<YOUR_MOUSER_API_KEY>"
}
}
}
}<YOUR_PATH_TO_MOUSER_SEARCH_MCP> is the absolute path to your clone, and <YOUR_MOUSER_API_KEY> is your Mouser Search API key. The install puts the mouser-search-mcp command inside the clone's .venv, not on your PATH.
