jobber-mcp
Related Servers
Alternatives to jobber-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityFmaintenanceConnects Claude to Jobber to manage clients, jobs, invoices, quotes, and scheduling through natural language.10-
- FlicenseNot gradedqualityCmaintenanceProvides a direct bridge between Claude and an authenticated Chrome session, enabling fetch requests with session cookies and JavaScript execution within live web pages.-
- AlicenseAqualityDmaintenanceEnables Claude to search jobs, manage proposals, messages, and contracts on Upwork via browser automation.18Apache 2.0
- FlicenseAqualityCmaintenanceGives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.8-
- AlicenseAqualityAmaintenanceConnects Claude to the customer side of Housecall Pro, letting you view estimates and invoices, check company details, and decline estimate options using the link your contractor sent.7115 npmMIT
- AlicenseAqualityDmaintenanceAttaches to your existing Chrome browser to allow Claude to see the active tab, interact via accessibility tree, and detect handoff triggers like 2FA and captchas.10MIT
TDQS
Scored across 7 tools
Each list tool targets a distinct resource (appointments, invoices, quotes, work requests), and the generic page reader, hub lister, and healthcheck are clearly separate utilities. No two tools overlap in purpose.
All tools share the jobber_ prefix and mostly follow verb_noun naming (list_, read_), but jobber_healthcheck deviates slightly from the verb_noun pattern. Overall the naming is predictable and consistent.
Seven tools is a tight, appropriate scope for a read-only Jobber Client Hub integration. Each tool covers a distinct need without redundancy, fitting well within the ideal 3-15 tool range.
The surface covers listing all four core resource types plus a generic page reader for details, hub configuration, and diagnostics. Missing structured get-by-id tools are worked around by jobber_read_page, so there are no critical gaps, though dedicated detail endpoints would be marginally more complete.