merch-store-mcp
Related Servers
Alternatives to merch-store-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP-capable agent to drive a real Chrome browser through stdio or HTTP, supporting navigation, page reading, interaction, scrolling, JavaScript execution, and replaying saved step-by-step recipes.24Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.1Apache 2.0
- AlicenseDqualityAmaintenanceConnects to an already-running Chrome/Chromium instance over CDP and exposes 75 browser-automation tools over newline-delimited MCP JSON-RPC on stdin/stdout, covering navigation, forms, keyboard/mouse input, screenshots, cookies, storage, tabs and frames, assertions, and retry/batch/step composition. It does not launch a browser itself, requiring a localhost debugging port on the existing instance.75MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-driven browser automation from any MCP client by pairing with a Chrome extension, translating tool calls into WebSocket commands to drive Chrome without an Electron host.3,989 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnects local stdio MCP servers to an existing Chrome 144+ session, preserving the user's signed-in sessions, cookies, tabs, and extension environment without launching a second browser. It provides tab control, semantic snapshots, screenshots, pointer, keyboard, form selection, scrolling, navigation, and waiting tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive individually named Chrome profiles, providing tools for tabs, navigation, page interaction, screenshots, JavaScript evaluation, console logs, and network inspection over stdio without a TCP port.-
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.