Skip to main content
Glama
JobBOSS2 MCP server

JobBOSS2 MCP server

Related Servers

Alternatives to JobBOSS2 MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides structured access to Dolibarr ERP/CRM API endpoints via the Model Context Protocol, supporting CRUD operations on resources like thirdparties, products, and orders.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      It exposes documented local WHMCS API tools, operational BI reports, and guarded administrator-approved operations over Model Context Protocol, with read-only default access and write execution requiring scoped approval.
      MIT
    • F
      license
      B
      quality
      Not graded
      maintenance
      Facilitates secure and type-safe interactions with both v1 and v2 of the Glide API, allowing users to manage app data and perform CRUD operations on tables via a Model Context Protocol interface.
      6
      5
      -

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    The generic resource tools (describe/list/get/create/update) and the report-specific tools are mostly distinct, and the two domain operations are clearly unique. Some ambiguity exists between generic create/get and create_report/get_report, but the descriptions clarify the report tools are for submitted report requests.

    Naming Consistency3/5

    All tools share the jobboss2_ prefix, but the suffix pattern is inconsistent: bare verbs (list, get, create, update), verb_noun (describe_resource, create_report, get_report), noun_lookup (issuing_materials_lookup), and a phrasal verb (transfer_stock_to_job). This is readable but not a predictable verb_noun convention.

    Tool Count5/5

    Nine tools is a reasonable size for a JobBOSS2 wrapper: generic CRUD, resource introspection, report submission/retrieval, and two domain-specific stock actions. Each tool addresses a distinct operation without excessive fragmentation.

    Completeness3/5

    The generic surface covers describe/list/get/create/update but omits delete, which is a notable gap for full lifecycle coverage. Report tools support submit and retrieve but no listing or cancellation, and the report schema is explicitly undefined, leaving agents with potential dead ends.