dropify-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_brandA | Fuzzy-match an artist or brand name against Dropify's tracked brands. Returns the brand name, its Dropify page, how many stores are tracked, and which store (if any) is free. |
| official_storesB | List every official store Dropify tracks for a brand, with region, whether it's free on Dropify, and the official store URL when Dropify exposes one. |
| restock_alert_linkA | Get the Dropify page where a user sets restock/drop alerts for a brand, plus a one-line how-to. |
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 3 tools
Each tool serves a clearly distinct step: resolving a brand, enumerating its official stores, and retrieving the alert setup page. There is no meaningful overlap in purpose, even though find_brand and restock_alert_link both return a Dropify page.
All names use snake_case, which is consistent, but the pattern is mixed: find_brand is verb_noun while official_stores and restock_alert_link are noun phrases. The conventions remain readable but are not fully predictable.
Three tools is well-scoped for a focused read-only lookup server covering brand discovery, store listing, and alert links. Each tool has a clear place and there is no unnecessary surface area.
The surface covers the core lookup workflow: find a brand, inspect its official stores, and get the restock alert link. A minor gap is the lack of a browse/list-all-brands operation if fuzzy matching fails, but agents can work around it with the existing tools.