Skip to main content
Glama
jayson-svg

BackCrew FieldRoutes MCP Server

by jayson-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BackCrew FieldRoutes MCP Server

No user-submitted related servers found.

    Related Servers

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

    • ServiceTitan MCP Server

      jrhoades1
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to query ServiceTitan data about technician jobs and business performance via natural language, while protecting customer personal information.
      -

    • 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

    • fieldwork-mcp

      daisydaines
      A
      license
      C
      quality
      B
      maintenance
      Enables pest control business owners using Fieldwork to ask plain-English questions about customers, invoices, product usage, schedules, and technicians, returning clear answers from the Fieldwork API. Read-only access with no ability to modify jobs, customers, or payments.
      28
      MIT

    • Argos-MCP

      AraneaDev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to securely interact with PostgreSQL, MySQL, SQLite, and SQL Server databases, featuring read-only mode, query validation, SSH tunneling, and field redaction for production-safe data access.
      2
      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.5/5.0

    Scored across 39 tools

    Disambiguation5/5

    Every tool is clearly either a search returning IDs for a specific entity or a get returning full records for given IDs. Entities are disjoint, and special tools like get_ticket_addons and resolve_employee_alias have distinct purposes. No ambiguity exists.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: search_<entity> and get_<entity> for every entity. Exceptions like get_ticket_addons and resolve_employee_alias still use the same verb_noun style, maintaining high consistency.

    Tool Count2/5

    With 39 tools, the server exceeds the 25+ threshold considered too many. While each entity pair is logical, the large number makes the tool surface heavy and could be streamlined with a generic search/get pattern.

    Completeness5/5

    As a read-only server, it provides search and get for all major FieldRoutes entities including customers, appointments, tickets, subscriptions, routes, payments, and more. Entity-specific addons and alias resolution fill any remaining gaps, making the read surface complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources