Skip to main content
Glama
PineappleCare

jobber-mcp

by PineappleCare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jobber-mcp

No user-submitted related servers found.

    Related Servers

    • enterprise-agent-lab

      isaac-dev-ai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
      1
      -

    • Jobber MCP Server

      adeocode
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Claude, ChatGPT, and Copilot to query live Jobber data—clients, jobs, quotes, invoices, revenue, and schedule—using natural language, with read-only access and careful API budget management.
      MIT

    • meta-ads-mcp

      GodmodeNZ
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only Meta Ads reporting and diagnostics, plus safe, preview-before-apply mutations such as campaign creation, duplication, targeting replacement, and attribution changes.
      -

    • varco_mcp

      williamselmo1993
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools are mostly distinct by domain: auth, clients, invoices, quotes, jobs, schedule, requests, catalog, and team. There is mild overlap potential among find_client, search_records, and get_record, but their descriptions generally separate search-by-contact, bounded record search, and single-record fetch.

    Naming Consistency3/5

    Names are readable and consistently snake_case, but the naming convention is mixed: some tools use verb-led names like find_client and get_record, while others use noun-phrase names like jobs_summary and revenue_summary. There is no consistent verb_noun pattern across the set.

    Tool Count4/5

    16 tools is slightly above the ideal compact range, but the server covers a broad Jobber domain and each tool serves a distinct reporting, lookup, or auth purpose. The count feels reasonable rather than bloated.

    Completeness2/5

    The tool surface is almost entirely read-only: searches, summaries, history, and lookups. There are no create, update, delete, or workflow tools such as creating a quote, scheduling a visit, or recording a payment, so many common Jobber management tasks would dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources