merch-store-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERCH_STORE_URL | No | URL of the store to connect to. Default: https://twilio-mcp-store.ngrok.dev | https://twilio-mcp-store.ngrok.dev |
| MERCH_STORE_LAUNCH | No | Set to '0' to disable launching Chrome automatically. Enabled by default. | |
| MERCH_STORE_CDP_URL | No | Chrome DevTools Protocol endpoint to attach to. Default: http://127.0.0.1:9222 | http://127.0.0.1:9222 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_statusA | Check the bridge: which page is connected, whether native WebMCP is live in this Chrome, and which store tools are registered. Call this first if anything looks wrong. |
| store_openA | Navigate the connected page to a store path, e.g. '/', '/checkout', '/drop', '/docs'. Most journeys do not need this — the page's own navigate_to tool is usually the right one. |
| store_read_logA | Read the store's live tool-call log — the same entries the page shows in its console panel. Use it to confirm what the store actually did before reporting success. |
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 targets a distinct concern: store_status checks connection/bridge health, store_open handles navigation, and store_read_log inspects the execution log. There is no overlap in purpose or ambiguous boundaries between them.
All tools share the store_ prefix and use snake_case, creating a predictable pattern. Minor variation exists between noun-style (store_status) and verb-style (store_open, store_read_log), but the convention is uniform enough for an agent to infer behavior.
Three tools is on the lower end but well-scoped for a lightweight bridge/debugging server. Each tool serves a clear and necessary role, and the count aligns with the server's narrow purpose.
The server covers the core diagnostic workflow: check connection, navigate if needed, and verify via logs. It lacks direct control or configuration tools, but those appear intentionally delegated to the page's own tools, so no significant gaps for its intended use.