Mouser Electronics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOUSER_DEBUG | No | Enable debug logging | false |
| MOUSER_API_TIMEOUT | No | Request timeout in seconds | 30 |
| MOUSER_API_BASE_URL | No | Base URL for Mouser API | https://api.mouser.com/api/v1 |
| MOUSER_PART_API_KEY | Yes | API key for part search | |
| MOUSER_ORDER_API_KEY | Yes | API key for cart/orders |
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 |
|---|---|
| health_checkA | Check the health status of the Mouser MCP server. Returns: A dictionary with the server status and API configuration info. |
| 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. |
| 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. |
| get_cartA | Retrieve shopping cart contents by cart key. Gets the current state of a shopping cart including all items, quantities, pricing, and totals. |
| 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. |
| 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. |
| 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. |
| get_orderA | Get order details by order number. Retrieves complete order information including status, items, totals, shipping details, and tracking information. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| component_search_workflow | Guide for searching and purchasing electronic components. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_server_status | Get the Mouser MCP server status and configuration. |
TDQS
Scored across 9 tools
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.
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.
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.
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.