Ask GorillaDesk (gorilladesk-mcp)
Related Servers
Alternatives to Ask GorillaDesk (gorilladesk-mcp)
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the FieldRoutes pest-control / lawn-care operations platform — talk to your data from Claude, Cursor, or any MCP client.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server enabling pest and lawn owners to ask FieldRoutes questions in plain English, with owner-shaped tools and a hosted connect vault.MIT

InvoiceFlash MCPofficial
FlicenseNot gradedqualityCmaintenanceRead-only MCP server that connects to an InvoiceFlash MySQL database, exposing clients, invoices, and quotes as tools for natural language querying via Claude Desktop or Claude Code.-- AlicenseAqualityCmaintenanceA read-only MCP server that enables querying and introspection of any Gadget app via GraphQL. It allows users to list models, inspect fields, and fetch records directly within AI tools like Claude and Cursor.930 npm1MIT
- AlicenseAqualityDmaintenanceA read-only MCP server that connects AI assistants to the OfficeRnD coworking and flex-space management platform. It enables natural language queries for community members, space bookings, billing records, and office resources.51MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for the Helcim payment API, letting AI agents safely query customers, invoices, card transactions, subscriptions, and more without risking financial mutations.MIT
TDQS
Scored across 19 tools
There is overlap between natural-language query tools (e.g., how_much_money, who_owes_me_money) and generic search tools (e.g., search_invoices, search_customers), though descriptions mitigate confusion with 'Prefer' hints. A few pairs like search_customers/find_customer and search_jobs/whats_on_the_schedule are nearly interchangeable and could lead to misselection.
The set mixes natural-language question phrases (how_much_money, who_are_my_technicians) with standard verb_noun patterns (search_customers, get_job). Each style is internally consistent, but the lack of a unified naming convention makes it harder to predict tool names across the whole server.
19 tools is slightly over the ideal 3-15 range but appropriate for the breadth of the GorillaDesk domain (customers, jobs, invoices, payments, estimates, services, users). The two-layer design (answer-oriented vs. data-access) adds functionality but also inflates the count.
The toolkit covers the core entities needed for a read-only business assistant. Minor gaps exist, such as missing get_* tools for payments, estimates, services, and users, but the search tools likely return sufficient detail for most 'ask' scenarios.