espresso-mcp
Related Servers
Alternatives to espresso-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for querying Percolate's specialty coffee database with read-only access to 1,100+ coffees, tasting profiles, brew recipes, pairings, and recommendations.840 npmMIT
- AlicenseAqualityDmaintenanceA read-only MCP server that wraps the coffee.pryzm.gg public API to calculate effective prices of coffee drinks after discounts, enabling users to find the cheapest coffee deals, search for discounts, and verify receipt prices.32MIT
- FlicenseAqualityBmaintenanceMCP server that recommends coffee based on preferences (mood, milk, caffeine, temperature) from a static menu; includes tools for listing menu, recommending, and explaining recommendations.3-
- AlicenseAqualityDmaintenanceAn MCP server for Gaggiuino-modified espresso machines, enabling monitoring, shot analysis, and profile management.47 npm1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for the Roastify Developer API, letting AI agents browse the coffee catalog and generate packaging artwork, with paid tools settled in Bitcoin Lightning.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that archives Decent DE1 espresso shots from Visualizer.coffee into SQLite and provides analysis tools for shots, beans, and profiles via MCP.GPL 3.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: get_cafe_details retrieves by ID, find_espresso_near searches by coordinates, search_cafes uses text filters, score_cafe applies the algorithm to arbitrary inputs, list_great_roasters covers roasters, and list_anti_patterns provides contrast examples. No two tools overlap in a confusing way.
All tool names follow the same verb_noun pattern in snake_case (get_, find_, search_, score_, list_). The verbs are specific and consistent with the action performed, making the naming predictable and intuitive.
Six tools is well within the ideal range for a domain-specific server. Each tool covers a distinct aspect of cafe discovery and scoring, and none feel redundant or superfluous. The count aligns with the server's focused purpose.
The toolset provides complete coverage for the espresso cafe domain: finding cafes (by location or criteria), retrieving detailed information, scoring cafes algorithmically, and accessing supporting data (roasters and anti-patterns). There are no obvious dead ends or missing core operations.