Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

Related Servers

Alternatives to Mouser MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      A 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.
      9
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools to search the Mouser Electronics parts catalog via keyword, part number, and manufacturer queries using the Mouser Search API.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables searching Mouser Electronics parts, reviewing BOMs, managing carts, and checking order history through natural language. Order placement is opt-in and requires typing APPROVE into a server-shown confirmation prompt before any order is submitted.
      14
      51 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse products, look up orders, and place orders through MCP tools, with API-key authentication, rate limiting, and idempotent order operations.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves a product store's catalog over MCP tool calls so agents can search products, add items to a cart, inspect the cart, and complete checkout without parsing full HTML pages. This keeps action payloads and token usage far smaller than DOM scraping, especially as catalogs grow, and also works through Chrome's native document.modelContext API.
      MIT

    TDQS

    C2.8/5.0

    Scored across 27 tools

    Disambiguation2/5

    Several tool pairs appear to do the same thing: deprecated v1 and v2 variants of search/manufacturerlist and keywordandmanufacturer/partnumberandmanufacturer coexist, plus get_order_by_ordernumber vs get_orderhistory_webordernumber both fetch order details. An agent could easily misselect between the deprecated duplicates or between post_cart and post_cart_items_update, though descriptions provide some guidance.

    Naming Consistency2/5

    Naming mixes verb_resource patterns (get_cart, post_order, get_order_countries) with path-derived names (post_order_item_createcartfromorder, get_orderhistory_bydatefilter) and version prefixes (v2_get_search_manufacturerlist, v2_post_search_keywordandmanufacturer). No single predictable convention holds across the set.

    Tool Count3/5

    27 tools is on the heavy side for a procurement/ordering domain, and roughly five of them are deprecated v1 duplicates that could be dropped. The remaining surface is plausible, but the count is inflated by redundant version pairs.

    Completeness4/5

    The set covers cart operations, order submission (new and from prior order), order options/currencies/countries, part and manufacturer search, and order history lookups. Coverage is solid for the ordering domain with only minor gaps such as explicit order cancellation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues