
mouser
Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Also supports batch MPN-list seeding (--mpn-list) for bulk datasheet workflows without a KiCad project. Use this skill when the user specifically mentions Mouser, when DigiKey is out of stock or has worse pricing, when comparing prices across distributors, or when searching for parts that DigiKey doesn't carry. For package cross-reference tables and BOM workflow, see the bom skill.
- Installs
- 495
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/aklofas/kicad-happy --skill mouser- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mouser automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Mouser Electronics Parts Search & Analysis
Related Skills
| Skill | Purpose |
|---|---|
kicad | Schematic analysis — extracts MPNs for part lookup |
bom | BOM management — orchestrates sourcing across distributors |
digikey | Primary prototype source (prefer for datasheets — direct PDF links) |
spice | Uses Mouser parametric data for behavioral SPICE models |
Mouser is the secondary source for prototype orders — use when DigiKey is out of stock or has worse pricing. For production orders, see lcsc/jlcpcb. For BOM management and export workflows, see bom. For datasheets, prefer DigiKey's API (direct PDF links) — Mouser blocks automated PDF downloads.
API Credential Setup
Mouser uses simple API key authentication — no OAuth, no tokens, no callback URLs. The Search API key is a UUID passed as a query parameter.
Getting Your API Key
- Go to mouser.com → My Mouser → My Account
- Under "APIs" section, click "Manage"
- Register for Search API key — this is the one needed for part lookups and datasheet downloads
- Search API keys may require approval (status shows "pending authorization" initially)
Setting Credentials
Set the environment variable before running the scripts:
export MOUSER_SEARCH_API_KEY=your-search-api-key-uuid
If credentials are stored in a central secrets file (e.g., ~/.config/secrets.env), load them first:
export $(grep -v '^#' ~/.config/secrets.env | grep -v '^$' | xargs)
Mouser Search API Reference
All search endpoints use the Search API key as a query parameter: ?apiKey=<key>. Content-Type is application/json for all POST requests.
V1 Endpoints
Keyword Search
POST /api/v1/search/keyword?apiKey=<key>
{
"SearchByKeywordRequest": {
"keyword": "100nF 0402 ceramic capacitor",
"records": 50,
"startingRecord": 0,
"searchOptions": "InStock"
}
}
searchOptions:"None"|"Rohs"|"InStock"|"RohsAndInStock"records: max 50 per requeststartingRecord: offset for pagination
Part Number Search
POST /api/v1/search/partnumber?apiKey=<key>
{
"SearchByPartRequest": {
"mouserPartNumber": "GRM155R71C104KA88D|RC0402FR-0710KL",
"partSearchOptions": "Exact"
}
}
- Up to 10 part numbers, pipe-separated (
|) - Works with both Mouser part numbers AND manufacturer part numbers (MPNs)
partSearchOptions:"Exact"|"BeginsWith"|"Contains"
V2 Endpoints
V2 adds manufacturer filtering and pagination by page number.
Keyword + Manufacturer Search
POST /api/v2/search/keywordandmanufacturer?apiKey=<key>
{
"SearchByKeywordMfrNameRequest": {
"keyword": "LMR51450",
"manufacturerName": "Texas Instruments",
"records": 25,
"pageNumber": 1,
"searchOptions": "InStock"
}
}
Note: the wrapper object name is SearchByKeywordMfrNameRequest (not SearchByKeywordMfrRequest — the V1 name is deprecated).
Part Number + Manufacturer Search
POST /api/v2/search/partnumberandmanufacturer?apiKey=<key>
Manufacturer List
GET /api/v2/search/manufacturerlist?apiKey=<key>
Returns the full list of manufacturer names for use in filtered searches.
V1 Deprecated Endpoints
These still work but V2 equivalents are preferred:
POST /api/v1/search/keywordandmanufacturer→ use V2POST /api/v1/search/partnumberandmanufacturer→ use V2GET /api/v1/search/manufacturerlist→ use V2
Search Response Structure
All search endpoints return the same response format:
{
"Errors": [],
"SearchResults": {
"NumberOfResult": 142,
"Parts": [...]
}
}
Key Part Fields
| Field | Type | Description |
|---|---|---|
MouserPartNumber | string | Mouser's internal part number (prefixed, e.g., 81-GRM155R71C104KA88) |
ManufacturerPartNumber | string | Manufacturer's part number (MPN) — use for cross-distributor matching |
Manufacturer | string | Manufacturer name |
Description | string | Product description |
Category | string | Product category |
DataSheetUrl | string | URL to datasheet PDF (Mouser-hosted — see Datasheet section) |
ProductDetailUrl | string | URL to Mouser product page |
ImagePath | string | Product image URL |
Availability | string | Human-readable stock text (e.g., "2648712 In Stock") |
AvailabilityInStock | string | Numeric stock quantity (as string) |
AvailabilityOnOrder | array | Incoming stock: [{Quantity, Date}] |
LeadTime | string | Factory lead time (e.g., "84 Days") |
LifecycleStatus | string|null | "New Product", "End of Life", etc. |
IsDiscontinued | string | "true" or "false" (string, not boolean) |
SuggestedReplacement | string | Replacement MPN if discontinued |
Min | string | Minimum order quantity (as string) |
Mult | string | Order multiple (as string) |
Reeling | bool | Tape-and-reel packaging available |
ROHSStatus | string | RoHS compliance status |
PriceBreaks | array | Tiered pricing: [{Quantity, Price, Currency}] |
ProductAttributes | array | Parametric specs: [{AttributeName, AttributeValue}] |
AlternatePackagings | array|null | Alternate packaging MPNs: [{APMfrPN}] |
SurchargeMessages | array | Tariff/surcharge info: [{code, message}] |
ProductCompliance | array | HTS codes, ECCN: [{ComplianceName, ComplianceValue}] |
UnitWeightKg | object | {UnitWeight: <float>} in kg |
Quirks and Gotchas
- Price is a string with currency symbol:
"$0.10", not a float. Parse it before comparing. - Stock is a string:
AvailabilityInStockreturns"2648712"not2648712. - IsDiscontinued is a string:
"true"or"false", not boolean. - Mouser part numbers have prefixes:
81-GRM155R71C104KA88— the prefix is Mouser-specific. UseManufacturerPartNumberfor cross-referencing. - V2 wrapper names differ from V1: V2 uses
SearchByKeywordMfrNameRequest, notSearchByKeywordMfrRequest. - Tariff info:
SurchargeMessagesmay contain US tariff percentages — useful for cost estimation. - On-order data:
AvailabilityOnOrdershows incoming stock quantities and expected dates.
Datasheet Download & Sync
Mouser's DataSheetUrl field points to Mouser-hosted URLs (mouser.com/datasheet/...). These URLs block automated downloads — they return an HTML "Access denied" page when fetched with Python/curl/wget, even with browser User-Agent headers. The download scripts handle this with a multi-strategy approach:
- Try the Mouser datasheet URL directly (works for some parts)
- Scrape the Mouser product page HTML for alternative datasheet links
- Try manufacturer-specific alternative URL patterns
Note: Mouser's product pages return 403 for most automated requests, so strategy 2 has limited success. DigiKey and LCSC are more reliable datasheet sources.
Datasheet Directory Sync
Use sync_datasheets_mouser.py to maintain a datasheets/ directory alongside a KiCad project. Same workflow and manifest.json format as the DigiKey skill.
# Sync datasheets for a KiCad project
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch>
# Preview what would be downloaded
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --dry-run
# Retry previously failed downloads
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --force
# Custom output directory
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> -o ./my-datasheets
# Parallel downloads (3 workers)
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --parallel 3
# Batch mode — sync from a plain MPN list (no KiCad project required)
python3 <skill-path>/scripts/sync_datasheets_mouser.py --mpn-list mpns.txt --output ./datasheets
MPN-list batch mode (KH-312) — when you have a list of MPNs but no
KiCad project to point at (harness datasheet seeding, bulk part-library
seeding). One MPN per line; blank lines and # comments (full-line and
inline) are skipped; generic values (100nF, DNP) are filtered via
is_real_mpn() and de-duplicated. Output defaults to ./datasheets/ in
the current working directory when --output is omitted.
Rate limiting — the script paces API calls with a 1.0s delay between
requests by default (Mouser's Search API allows 30 calls/min on the free
tier; 1.0s stays comfortably under). Override with --delay <seconds> if
you have a higher-tier key or want to slow things down further.
Single Datasheet Download
Use fetch_datasheet_mouser.py for one-off downloads.
# Search by MPN (uses Mouser API)
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "TPS61023DRLR" -o datasheet.pdf
# Direct URL download
python3 <skill-path>/scripts/fetch_datasheet_mouser.py "https://example.com/datasheet.pdf" -o datasheet.pdf
# JSON output
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "ADP1706" --json
Download Strategy
The scripts try multiple sources in order:
- Schematic URL — uses the datasheet URL embedded in the KiCad symbol (sync only)
- Mouser API search — gets the
DataSheetUrlfrom the API response - Alternative manufacturer sources — tries known URL patterns for major manufacturers (TI, Microchip, etc.) when the Mouser URL is blocked
- Headless browser fallback — if
playwrightis installed, uses headless Chromium as a last resort
When all methods fail, provide the ProductDetailUrl to the user so they can download from the Mouser product page in their browser.
Web Search Fallback
If no API key is available, search Mouser by fetching product pages directly:
- Search URL:
https://www.mouser.com/c/?q=<query> - Product pages contain full specs, pricing tiers, stock, datasheets
- Results from Mouser can be noisy (JS-heavy pages)
Include key parameters in the query:
- Passives: value, package (0402/0603/0805), tolerance, voltage/power rating, dielectric (C0G/X7R)
- ICs: part number or function, package (QFN/SOIC/TSSOP), key specs (voltage, current, interface)
- Connectors: type (USB-C, JST-PH), pin count, pitch, mounting (SMD/THT), orientation
Tips
- Pipe-separate up to 10 part numbers in a single PartNumber search for batch lookups
MinandMultfields matter — some parts have minimum order qty or must be ordered in multiplesSurchargeMessagesmay include US tariff percentages — factor into cost estimatesAvailabilityOnOrdershows incoming stock with expected dates- Check
IsDiscontinuedandLifecycleStatusbefore selecting parts
FAQ
What does the mouser skill do?
Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Also supports batch MPN-list seeding (--mpn-list) for bulk datasheet workflows without a KiCad project. Use this skill when the user specifically mentions Mouser, when DigiKey is out of stock or has worse pricing, when comparing prices across distributors, or when searching for parts that DigiKey doesn't carry. For package cross-reference tables and BOM workflow, see the bom skill.
How do I install mouser?
Run npx skills add https://github.com/aklofas/kicad-happy --skill mouser in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mouser/ (personal) or .claude/skills/mouser/ (project).
Which AI agents can use mouser?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mouser safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mouser?
It is published by aklofas in aklofas/kicad-happy. It has 495 recorded installs.
More from aklofas/kicad-happy
kicad
aklofas/kicad-happy
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trustsummary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicadsch, .kicadpcb, .kicadpro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question
jlcpcb
aklofas/kicad-happy
JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the bom skill.
bom
aklofas/kicad-happy
BOM (Bill of Materials) management for electronics projects — the workflow skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills around a unified BOM lifecycle. Create, update, and maintain BOMs with part numbers, costs, quantities stored as KiCad symbol properties. ALWAYS trigger this skill for any task involving component sourcing, pricing, ordering, distributor searches, BOM export, or fabrication preparation — even if the user names a specific distributor or fab house (e.g. "search DigiKey for...", "generate JLCPCB BOM", "order from Mouser"). This skill analyzes the schematic for sourcing gaps, recommends which distributor/fab skills to call for each gap, and writes results back as symbol properties — the agent (or user) performs the actual searches via the called skills. Also trigger on phrases like "what parts do I need", "order components", "how much will this cost", "export for JLCPCB", "find parts for this board", "compare pricing", or "chec
lcsc
aklofas/kicad-happy
Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (--mpn-list) for bulk workflows without a project. No API key needed — uses the free jlcsearch community API. Use this skill when the user mentions LCSC, JLCPCB parts library, JLCPCB assembly parts, production sourcing, Cxxxxx part numbers, needs to find LCSC equivalents for parts, is preparing a BOM for JLCPCB assembly, or wants to download datasheets and LCSC is available. For package cross-reference tables and BOM workflow, see the bom skill.
spice
aklofas/kicad-happy
Run automatic SPICE simulations on subcircuits detected from KiCad schematic analysis — validates filter frequencies, divider ratios, opamp gains, LC resonance, and crystal load capacitance. Supports ngspice, LTspice, and Xyce (auto-detected). Generates testbenches, runs batch mode, produces structured pass/warn/fail report. Use when the user asks to simulate, verify, or validate any analog subcircuit — RC filters, LC filters, voltage dividers, opamp circuits, crystal oscillators. Also for "simulate my circuit", "run spice", "verify with simulation", "check my filter cutoff", "does this divider give the right voltage", "what's the bandwidth of this opamp stage". Consider suggesting simulation during design reviews when the schematic analyzer reports simulatable subcircuits and a SPICE simulator is available.
emc
aklofas/kicad-happy
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, shielding, and magnetic leakage from switching inductors. Produces severity-ranked risk report with pre-compliance test plan. Supports FCC Part 15, CISPR 32, CISPR 25 (automotive), MIL-STD-461G. SPICE-enhanced when available. Use when the user asks about EMC, EMI, radiated/conducted emissions, FCC compliance, CE marking, CISPR, ground plane issues, decoupling strategy, clock routing EMC, switching noise, differential pair skew, or whether their board will pass EMC testing. Also for "will this pass FCC?", "check my EMC", "is my ground plane okay?", "check my decoupling", or "generate an EMC test plan".
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.