Skip to main content
Glama
commair-tools

mcp-servicefusion

by commair-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-servicefusion

No user-submitted related servers found.

    Related Servers

    • Service Fusion MCP

      SinthetikIndustries
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to read and create customers, jobs, estimates, invoices, calendar tasks, equipment, technicians, and reference data through the documented Service Fusion REST API, handling OAuth 2.0 and pagination automatically.
      24
      160 npm
      MIT

    • ServiceFusion MCP Server

      rashidazarang
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with ServiceFusion's field service management platform through standardized MCP operations. Supports complete customer and job management including creating work orders, managing customer records, and accessing service data with OAuth 2.0 authentication.
      -

    • Zoho FSM MCP Server

      LogeshR15
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with Zoho Field Service Management, allowing operations on work orders, requests, contacts, and more via natural language.
      24
      -

    • FieldEdge MCP Server

      BusyBee3333
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive access to the FieldEdge field service management platform through over 87 tools and 16 React applications. It enables users to manage customers, jobs, scheduling, and invoicing through natural language or integrated UI components.
      -
    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/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action (customer, job, estimate, invoice, equipment, tech, etc.) with no overlap in functionality. The create, get, and search prefixes clearly separate intents.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_customer, get_job_details, search_customers). Naming is uniform and predictable across the entire set.

    Tool Count5/5

    16 tools is appropriate for a field service management API covering customer, job, estimate, invoice, equipment, and lookup functions. Each tool serves a necessary purpose without bloat.

    Completeness3/5

    The tool set covers creation and retrieval for core entities but lacks update and delete operations for customers, jobs, estimates, and invoices. This is a notable gap for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources