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
      C
      maintenance
      A read-only MCP server for InvGate Asset Management, enabling natural language queries for assets, people, computers, servers, software, and API health.
      12
      7 npm
      1
      MIT

    • servicenow-mcp

      ausper-tech
      A
      license
      A
      quality
      C
      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
      A
      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
      A
      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.
      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

    A4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation: server info, session relevance, client query lifecycle (submit/results/combined), sites, computer groups, operators, dashboard variables, and a generic API GET. The three client query tools are clearly separated by their role in the workflow, and session_relevance_query vs client_query is explicitly server-side vs client-side.

    Naming Consistency2/5

    Naming is inconsistent: most tools use verb_noun (get_server_info, list_sites, get_operator), but there are noun phrases (session_relevance_query, client_query, client_query_results), an object-verb (client_query_submit, api_get), and a standalone verb (whoami). This mixing of verb-first and noun-first patterns makes the set harder to predict.

    Tool Count5/5

    11 tools is well within the ideal range for a domain-specific server. Each tool serves a distinct need, from connectivity checks to relevance queries, client data collection, and resource lookups. No tool feels superfluous, and the count is appropriate for a read-only BigFix root server interface.

    Completeness5/5

    The tool surface comprehensively covers the read-only querying and inspection domain: server info, session relevance, client relevance, sites, computer groups, operators, dashboard variables, and a generic API escape hatch. The powerful session_relevance_query and api_get cover any gaps for listing or deep inspection, and the absence of mutating tools is consistent with the stated read-only nature.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources