Skip to main content
Glama
jayson-svg

BackCrew Jobber MCP Server

by jayson-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to BackCrew Jobber MCP Server

No user-submitted related servers found.

    Related Servers

    • Jobber MCP Server

      friendlygeorge
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to access and manage Jobber field-service data including clients, jobs, invoices, and quotes through natural language interactions.
      6
      33 npm
      MIT

    • 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.
      1
      MIT

    • 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

    • jobkeepr-mcp

      dandyer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and manage a Jobkeepr field service business including jobs, customers, scheduling, estimates, invoices, and payments via MCP.
      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

    A3.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource (clients, account, jobs, invoices, quotes, properties, users) with either list or get operations. There is no ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_clients, get_job, get_invoice). No deviations or mixed conventions.

    Tool Count5/5

    With 12 tools, the set is well-scoped for a read-only server focused on core entities of a field service management platform. Not too many, not too few.

    Completeness4/5

    The tools cover read operations for all major entities (clients, jobs, invoices, quotes, properties, users). Missing write operations and potentially entities like visits, but the read-only scope is clearly stated and consistently implemented.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources