Skip to main content
Glama
Mouser Electronics MCP Server

Mouser Electronics MCP Server

by nickweedon

Mouser Electronics MCP Server

A Model Context Protocol (MCP) server for the Mouser Electronics API. Search for electronic components, manage shopping carts, and track orders directly through Claude or other MCP clients.

Features

  • Part Search: Find components by keyword or exact part number

  • Component Details: Access specifications, pricing, availability, and datasheets

  • Cart Management: Add items to cart and update quantities

  • Order Tracking: View order details and history

  • Pricing Information: Get quantity-based pricing with up to 4 price breaks

  • Real-time Availability: Check stock levels and lead times

Related MCP server: jlcpcb-mcp

Quick Start

Prerequisites

  • Python 3.10 or higher

  • uv package manager (recommended)

  • Mouser Electronics API keys (free at mouser.com/api-hub)

Installation

  1. Clone this repository:

git clone <this-repo> mouser-mcp
cd mouser-mcp
  1. Install dependencies:

uv sync
  1. Create your environment file:

cp .env.example .env
# Edit .env with your Mouser API keys

You'll need two separate API keys from Mouser:

  • Part Search API Key: For searching components

  • Order/Cart API Key: For cart and order operations

Get both keys at: https://www.mouser.com/api-hub/

  1. Run the server:

uv run mouser-mcp

Project Structure

mouser-mcp/
├── src/mouser_mcp/
│   ├── __init__.py          # Package initialization
│   ├── server.py            # Main MCP server entry point
│   ├── client.py            # Mouser API client
│   ├── types.py             # TypedDict definitions
│   ├── api/                 # API modules
│   │   ├── search.py        # Search operations
│   │   ├── cart.py          # Cart management
│   │   ├── order.py         # Order operations
│   │   └── order_history.py # Order history
│   └── utils/               # Utility modules
├── tests/                   # Test suite
├── .env.example             # Environment template
└── README.md               # This file

Available Tools

Tool

Description

search_by_keyword

Search parts by keyword (e.g., "resistor 10k", "STM32F4")

search_by_part_number

Search by exact part number (e.g., "595-TPS54360DDAR")

get_cart

Retrieve cart contents by cart key

add_to_cart

Add item to shopping cart

update_cart_item

Update item quantity in cart

get_order_options

Get shipping/payment options for a cart

get_order

Retrieve order details by order number

list_order_history

View past orders (default: last 30 days)

health_check

Check server status and API configuration

Environment Variables

Variable

Description

Default

MOUSER_PART_API_KEY

API key for part search

(required)

MOUSER_ORDER_API_KEY

API key for cart/orders

(required)

MOUSER_API_BASE_URL

Base URL for Mouser API

https://api.mouser.com/api/v1

MOUSER_API_TIMEOUT

Request timeout in seconds

30

MOUSER_DEBUG

Enable debug logging

false

Claude Desktop Integration

Add to your Claude Desktop configuration (claude_desktop_config.json):

{
  "mcpServers": {
    "mouser": {
      "command": "uv",
      "args": ["--directory", "/path/to/mouser-mcp", "run", "mouser-mcp"]
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "mouser": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--env-file",
        "/path/to/mouser-mcp/.env",
        "mouser-mcp:latest"
      ]
    }
  }
}

Development

Running Tests

# Run all tests (unit tests only, no API keys needed)
uv run python -m pytest -v

# Run integration tests (requires real Mouser API keys)
uv run python -m pytest tests/test_search_integration.py -v -s

# Run specific test
uv run python -m pytest tests/test_search_integration.py::test_search_arduino_boards_integration -v -s

Linting

uv run ruff check src/ tests/
uv run ruff format src/ tests/

Building

uv build

Troubleshooting

"Invalid unique identifier" Error

Problem: When searching for parts, you get:

{
  "Errors": [{
    "Code": "Invalid",
    "Message": "Invalid unique identifier.",
    "PropertyName": "API Key"
  }]
}

Solution: The API keys in your .env file are placeholders. You need to:

  1. Get real API keys from Mouser API Hub

  2. Update your .env file with the actual keys

See API_KEY_SETUP.md for detailed instructions.

Rate Limit Errors

If you see rate limit errors, wait at least 1 minute before retrying. Consider implementing:

  • Request throttling in your application

  • Caching of search results

  • Batch operations where possible

Empty Search Results

If searches return no results:

  • Verify the part exists on mouser.com

  • Try broader search terms

  • Check for typos in part numbers

For more troubleshooting help, see INVESTIGATION_SUMMARY.md

Docker Deployment

Build and run with Docker Compose:

docker compose up --build

For development with VS Code Dev Containers:

  1. Open the project in VS Code

  2. Install the "Dev Containers" extension

  3. Click "Reopen in Container" when prompted

API Rate Limits

Mouser API has the following limits:

  • 50 results maximum per search request

  • 30 requests per minute

  • 1000 requests per day

The server will raise errors if you exceed these limits.

Example Usage

Once integrated with Claude Desktop, you can ask:

  • "Search for STM32F407 microcontrollers on Mouser"

  • "Find 10k ohm resistors with 1% tolerance"

  • "What's the price and availability for part number 595-TPS54360DDAR?"

  • "Show me my recent Mouser orders"

License

MIT License - See LICENSE file for details.

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Run tests and linting

  5. Submit a pull request

Resources

Available Tools

9 tools
add_to_cartA

Add an item to an existing shopping cart.

Adds a single part to the cart with the specified quantity. If the part already exists in the cart, the quantity will be updated.

Inputs: cart_key (required), quantity (required), mouser_part_number (required), customer_part_number. Returns: object

get_cartA

Retrieve shopping cart contents by cart key.

Gets the current state of a shopping cart including all items, quantities, pricing, and totals.

Inputs: cart_key (required). Returns: object

get_orderA

Get order details by order number.

Retrieves complete order information including status, items, totals, shipping details, and tracking information.

Inputs: order_number (required). Returns: object

get_order_optionsA

Get available order options for a cart.

Retrieves billing/shipping addresses, payment methods, shipping options, and other order configuration details for the specified cart.

Inputs: cart_key (required). Returns: object

health_checkA

Check the health status of the Mouser MCP server.

Returns: A dictionary with the server status and API configuration info.

Inputs: no named parameters. Returns: object

list_order_historyA

List order history for the past N days.

Retrieves a summary of past orders including order numbers, dates, statuses, and totals. Useful for tracking order history and status.

Inputs: days. Returns: object

search_by_keywordA

Search for parts using keyword search.

Search across part numbers, manufacturers, and descriptions to find electronic components. Returns up to 50 results per request with pricing, availability, datasheets, and specifications.

Inputs: keyword (required), records, start_record. Returns: object

search_by_part_numberA

Search for a specific part by exact part number.

Performs an exact match search for a Mouser or manufacturer part number. Returns detailed part information including pricing tiers, availability, datasheets, and specifications.

Inputs: part_number (required). Returns: object

update_cart_itemA

Update the quantity of an item in the cart.

Changes the quantity of an existing cart item. To remove an item, set quantity to 0.

Inputs: cart_key (required), quantity (required), mouser_part_number (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health check, two distinct search types (keyword vs part number), cart operations (get, add, update), order options, order retrieval, and order history. There is no overlap or potential confusion between them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., health_check, search_by_keyword, add_to_cart, list_order_history). The naming is uniform and predictable throughout the set.

    Tool Count4/5

    With 9 tools covering search, cart, and order management, the count is well-scoped for an e-commerce electronics component server. It is slightly on the lower side but each tool earns its place, and the set feels complete without unnecessary extras.

    Completeness4/5

    The tool surface covers the main workflows: searching parts, managing a cart, and viewing orders. A minor gap is the lack of a tool to create a new cart (add_to_cart assumes an existing cart) and possibly a part detail view separate from search, but overall it covers essential e-commerce operations adequately.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for JLCPCB/LCSC component search, live stock and pricing, datasheets, and PCB/3D printing ordering via authenticated API.
      28
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps the Universal Commerce Protocol (UCP) Discovery and Catalog capabilities, letting you search and compare products across UCP merchants directly from Claude.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the Elsevier Developer APIs. Gives Claude Code access to Scopus, ScienceDirect, and other Elsevier academic databases.
      6
      15
      MIT