Skip to main content
Glama
chrischall

jobber-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jobber-mcp

No user-submitted related servers found.

    Related Servers

    • firefox

      llyfn
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to drive your everyday logged-in browser session — opening and closing tabs, navigating, clicking, typing, scrolling, filling forms, uploading files, taking screenshots, and reading page text, console output and network requests. It runs through a local native-messaging bridge, scoping each client session to its own window behind yours.
      49 npm
      2
      MIT

    • Scrapeline

      surypratapsingh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to read, extract, crawl, and export data from open browser tabs and specified URLs locally, including logged-in sessions, structured page data, contacts, images, sitemaps, and Shopify catalogues.
      MIT

    • chrome-bridge

      bbauersjt
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides a direct bridge between Claude and an authenticated Chrome session, enabling fetch requests with session cookies and JavaScript execution within live web pages.
      -

    • browser-mcp-server

      vicktor12
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to control Google Chrome using local Playwright sessions to navigate, click, fill forms, take screenshots, and read pages, with security guards and an audit log.
      6
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    The five list_* tools each target a clearly distinct resource (invoices, quotes, work requests, appointments, hubs), and healthcheck is unmistakably an operational probe. The only overlap is jobber_read_page, a generic fallback that can also fetch invoices/quotes/work_requests pages, though its description frames it as a detail-page/none-shown fallback rather than a competing list tool.

    Naming Consistency4/5

    All tools share the jobber_ prefix and snake_case, with a dominant verb_noun pattern (list_invoices, list_hubs, read_page). jobber_healthcheck breaks the verb_noun mold slightly by being a verb-less compound, but it is a minor, readable deviation within an otherwise uniform scheme.

    Tool Count5/5

    Seven tools is well-scoped for a read-only Jobber Client Hub viewer: one list tool per resource plus a generic page reader and a connectivity probe. No tool appears redundant or filler.

    Completeness4/5

    The read-only surface covers the main hub resources (appointments, invoices, quotes, work requests, hubs) and jobber_read_page compensates for detail views and unlisted layouts, so agents can resolve most queries. Gaps remain (e.g., no client/job listing and no direct single-invoice fetch), but these are minor for a deliberately read-only server.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources