Skip to main content
Glama
jgstew

bigfix-root-mcp

by jgstew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bigfix-root-mcp

No user-submitted related servers found.

    Related Servers

    • invgate-mcp

      wdelcant
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for InvGate Asset Management, enabling natural language queries for assets, people, computers, servers, software, and API health.
      12
      3 npm
      1
      MIT

    • servicenow-mcp

      ausper-tech
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.
      7
      MIT

    • MSSQL-MCP

      esasiyun17
      A
      license
      A
      quality
      C
      maintenance
      Security-first, read-only MCP server for Microsoft SQL Server, enabling safe natural-language querying of databases.
      5
      4 npm
      MIT

    • dspace-mcp

      mpasternak
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that enables natural language querying of DSpace 7+ repositories via the REST API, allowing users to search, retrieve items, and analyze repository data.
      28 PyPI
      2
      MIT

    • Quickbase MCP

      josemsantiago
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Quickbase that enables natural-language queries, schema exploration, data export, and saved report execution by auto-scanning app metadata and sample data on startup.
      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

    B3.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource or operation (get/list/find content, computers, actions, operators, sites, qna). The main overlaps are the relevance-evaluation trio (session_relevance_query, client_query/qna_eval_client_relevance) and the client_query wrapper versus client_query_submit/client_query_results, but the descriptions explain scope and targeting differences well enough to select correctly.

    Naming Consistency3/5

    Many names follow a verb_noun or qna_verb_noun pattern, but the set mixes verb-first (get_content, list_operators, find_computers) with noun-phrase names (client_query, session_relevance_query, applicable_fixlets, whoami) and noun_verb order in api_get. It remains readable thanks to clear domain prefixes, but it is not a single predictable convention.

    Tool Count3/5

    27 tools is heavy for a single MCP server and sits above the usually comfortable 3-15 range. The BigFix root-server domain is broad (content, computers, actions, relevance, qna, server info), so most tools map to distinct subdomains, but the count is still at the borderline-heavy end.

    Completeness3/5

    Read coverage is fairly strong: content, operators/roles, computers, actions, sites, server info, relevance evaluation, and a read-only API escape hatch are all present. However, the surface omits action lifecycle operations (take/stop/delete action) and content import/deployment, and api_get is explicitly read-only, so the toolset cannot complete the primary BigFix management workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources