Skip to main content
Glama
chrischall

Housecall Pro MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Housecall Pro MCP

No user-submitted related servers found.

    Related Servers

    • BackCrew Housecall Pro MCP

      jayson-svg
      A
      license
      B
      quality
      B
      maintenance
      Connects AI assistants to Housecall Pro to look up and manage customers, jobs, invoices, and more through natural language. Operates in read-only mode by default with optional write capabilities.
      30
      1
      MIT

    • FieldRoutes MCP Server

      glbryce7795
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to look up customers, check routes, view appointments, pull service history, and access FieldRoutes data directly in conversation.
      -

    • jobber-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude to read appointments, invoices, quotes, and work requests from a Jobber Client Hub. Read-only, uses a local browser bridge to access the customer portal.
      7
      548 npm
      MIT

    • JobNimbus MCP Server

      drummouse
      F
      license
      B
      quality
      D
      maintenance
      Connects Claude to your JobNimbus account via API, enabling management of contacts, jobs, notes, and other CRM entities through natural language.
      19
      -
    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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: company lookup, estimate/invoice retrieval, estimate decline/approve, health check, and link listing. The only minor overlap is get_estimate including company info, but that's complementary rather than confusing.

    Naming Consistency5/5

    All tools follow the consistent pattern housecallpro_ + verb_noun (e.g., get_estimate, decline_estimate, list_links). Verbs are lowercase and snake_case throughout, making the naming predictable and scannable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose—reading and acting on estimates/invoices plus administrative utilities. Each tool earns its place, and the count sits comfortably in the ideal 3-15 range.

    Completeness4/5

    The core lifecycle is covered: retrieve documents, decline an estimate, and access company details. The main gap is the lack of a tool to list all estimates/invoices (only get by ID), and payment is not addressed, but these are minor given the server's customer-facing scope.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources