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

    • 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
      Not graded
      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 npm
      MIT

    • browser-for-claude

      lldartsll
      F
      license
      A
      quality
      C
      maintenance
      Gives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.
      8
      -
    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.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    The five list_* tools each target a clearly distinct resource (invoices, appointments, hubs, quotes, work requests), and healthcheck is unique. The only overlap is jobber_read_page, which can also surface invoices/quotes/appointments pages, so an agent must decide between a list tool and the generic page reader, though the description frames it as a detail-page/fallback path.

    Naming Consistency5/5

    Every tool uses the same jobber_ prefix with snake_case and a verb_noun shape (list_invoices, list_appointments, list_hubs, list_quotes, list_work_requests, read_page), with healthcheck the sole minor deviation as a single-word diagnostic.

    Tool Count5/5

    Seven tools is well-scoped for a read-only Jobber Client Hub bridge: five list tools, one raw page reader, and one connectivity check, each earning its place with no redundancy.

    Completeness4/5

    The surface covers the read-only hub domain across invoices, quotes, appointments, work requests, hubs, and diagnostics, and read_page backstops anything not directly listed. Gaps are minor: no filtered/search listing and no dedicated single-item getter beyond read_page, and write operations are intentionally absent.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources