Skip to main content
Glama
BackCrew Housecall Pro MCP Server

BackCrew Housecall Pro MCP Server

by jayson-svg

Related Servers

Alternatives to BackCrew Housecall Pro MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects your own Housecall Pro account to Claude Code, ChatGPT, Cursor and other AI agents so you can schedule jobs, assign technicians, send estimates and invoices, and review schedules or aged receivables in plain language. Works on any Housecall Pro plan without a Housecall Pro API key or developer setup.
      7
      45 PyPI
      Elastic 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Connects 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.
      7
      213 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connect an AI assistant to your Jobber account to query clients, jobs, invoices, and more in plain English, with optional write actions for creating clients and jobs.
      12
      MIT

    TDQS

    B3.2/5.0

    Scored across 30 tools

    Disambiguation4/5

    Tools are mostly distinct with clear resource+action separation (jobs, estimates, invoices, leads, customers, materials). Some potential confusion exists between get_schedule and list_events (both relate to scheduling/calendar), and between list_job_line_items and list_invoices line items, but the descriptions differentiate them adequately. list_job_invoices vs list_invoices also has slight overlap but the scoping differs.

    Naming Consistency5/5

    All 30 tools follow the consistent verb_noun pattern (list_*, get_*), with list_ prefixed collection endpoints and get_ prefixed singular resource fetches. The naming is uniform, predictable, and follows standard REST resource conventions throughout.

    Tool Count4/5

    30 tools is on the heavier side, but the domain (a field service management platform) genuinely spans many resource types: customers, jobs, estimates, invoices, leads, employees, materials, price book, schedule, tags, and company settings. Each list/get pair earns its place for the breadth of the CRM/job management domain, though it borders on the high end.

    Completeness2/5

    The entire tool surface is read-only (every single tool is readonly-owner tier). There are no create, update, or delete operations anywhere. This is a severe gap for a job-management platform where agents would realistically need to create customers, schedule jobs, create estimates, or invoice customers. The surface lacks all write capabilities and even some reads like customer contact details or job-specific customer info.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues