digikey-list-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| digikey_search_partsC | Search DigiKey for discovery candidates using standard pricing. |
| digikey_get_partA | Get current exact product, variation, stock, lifecycle, and pricing data from DigiKey. |
| digikey_compare_partsA | Fetch exact current details for two or more parts for an attributed comparison. |
| digikey_find_alternatesB | Return DigiKey substitutions and recommendations as unverified candidates. |
| digikey_list_mylistsC | List the authenticated user's DigiKey MyLists. |
| digikey_get_mylistB | Read one DigiKey MyList and its current list-line data. |
| digikey_validate_mylistB | Refresh every MyList line against exact DigiKey product data and report warnings. |
| digikey_preview_mylist_changesB | Validate exact SKUs and return an expiring, signed preview without changing DigiKey. |
| digikey_apply_mylist_changesA | Apply exactly one previously reviewed preview to DigiKey MyLists idempotently. |
| digikey_update_mylist_lineB | Preview or explicitly confirm replacement of one existing MyList line. |
| digikey_remove_mylist_lineA | Delete one MyList line only when the user explicitly confirms the exact IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct resource+action pairs, but the MyList mutation family (validate_mylist, preview_mylist_changes, apply_mylist_changes, update_mylist_line) has fuzzy boundaries since all deal with previewing/confirming line changes. Similarly get_part, compare_parts, and find_alternates overlap since compare could be done by repeated get_part calls, though descriptions do clarify intent.
Every tool uses the digikey_ prefix followed by a consistent snake_case verb_noun pattern (search_parts, get_mylist, apply_mylist_changes). No mixed conventions or casing deviations.
11 tools is well within the ideal 3-15 range and each tool maps to a concrete catalog or MyList workflow step with no obvious filler.
The surface covers catalog lookup (search/get/compare/alternates) and MyList lifecycle (list/get/validate/preview/apply/update/remove) thoroughly. Minor gaps remain, such as no explicit tool to create a new MyList or add a fresh line outside the preview/apply flow.