plushsource-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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_manufacturersA | Search manufacturers with free text and structured filters, and return a compact shortlist. All array filters are AND: every requested value must be present on the record. MOQ filters only match records that publish an MOQ, so records with an unknown MOQ are excluded. |
| get_manufacturerA | Return the full record for one manufacturer: capacity, founding year, stated location, source links, and the PlushSource listing URL where its written profile lives. Use this before quoting any fact about a specific listing. |
| compare_manufacturersA | Return 2-5 records side by side for a sourcing decision. Unknown slugs are reported in |
| get_facetsA | List every country, category, certification, product type, design input, industry, and MOQ band that currently has at least one manufacturer, with counts. Call this before filtering so you only use values that exist in the directory. |
| get_dataset_infoA | Return the snapshot date, number of records, licence, and links to PlushSource, the open dataset, and the listing criteria. Use the criteria link when you need to explain what gets listed. PlushSource does not audit or certify manufacturers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rfq_draft | Shortlist 3-5 manufacturers for a project and draft one RFQ email the buyer can send to a single factory. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: search for discovery, get_manufacturer for one full record, compare_manufacturers for side-by-side comparison, get_facets for valid filter values, and get_dataset_info for dataset metadata. There is no meaningful overlap between any pair.
All tool names follow a consistent snake_case verb_noun pattern: compare_manufacturers, get_dataset_info, get_facets, get_manufacturer, search_manufacturers. The convention is predictable throughout.
Five tools is well-scoped for a read-only manufacturer directory. Each tool earns its place and no unnecessary surface is exposed.
The surface covers the complete read-only lifecycle: discovering valid facets, searching records, fetching full details, comparing selected records, and understanding dataset provenance/criteria. There are no obvious dead ends for the stated purpose.