Skip to main content
Glama
vbabchenkov

corp-resourcing

by vbabchenkov

Related Servers

Alternatives to corp-resourcing

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Workday HCM data such as workers, organizations, locations, job profiles, and cost centers through MCP tools an LLM can call.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables language models to safely explore lakehouse tables and governed metrics, run guarded read-only SQL, and inspect pipeline health and data-contract violations through MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only access to GitLab and Jira data through MCP, allowing users to list projects, merge requests, issues, and search Jira tickets via natural language queries. Provides safe, structured access to project management data without write permissions.
      36 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to company data across PostgreSQL, MongoDB Atlas, and flat files through MCP tools, allowing AI assistants to query and retrieve information via natural language.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and LLM agents to query operational databases through a read-only MCP gateway with table whitelisting, automatic row limits, sensitive-data masking, and audit logging.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and AI agents to perform defensive security posture assessments, privilege escalation surface audits, and post-quantum cryptography readiness checks through read-only diagnostic tools.
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools partition the space cleanly: team-level utilization, project facts, and people availability. The descriptions explicitly cross-reference one another and warn against misuse, so an agent should not confuse them.

    Naming Consistency4/5

    find_projects and find_people follow a consistent find_* pattern, but utilization_summary breaks the verb pattern with a noun-based name. All names use snake_case and are readable, so the inconsistency is minor.

    Tool Count4/5

    Three tools is slightly lean but appropriate for a focused read-only resourcing and staffing lookup server. Each tool addresses a distinct need: team summary, project lookup, and people lookup.

    Completeness4/5

    For a query-oriented resourcing tool, the surface covers the main use cases: overall team utilization, specific project facts, and individual availability. It lacks update/create operations and deeper project-staffing queries, but those appear outside its stated scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues