Skip to main content
Glama
jbrasero

MCP para Primavera Unifier

by jbrasero

Related Servers

Alternatives to MCP para Primavera Unifier

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely inspect Oracle Database schemas, objects, and PL/SQL source with a strict read-only guard, without ever modifying data.
      10 npm
      MIT
    • 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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Confluence, GitHub, Jira, Figma, Outlook, Teams, and browser automation for AI clients, enabling safe discovery, retrieval, and summarization of company knowledge without modifying source systems.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only querying and schema inspection of Oracle Database 10g through MCP tools or a Claude Code skill, with SELECT/WITH enforcement, row limits, timeouts, and audit logging.
      -

    TDQS

    C2.9/5.0

    Scored across 18 tools

    Disambiguation3/5

    Several tools are essentially 'validate shell then chain reads into a dashboard' (project_health, risk_center, cost_sheet_budget, schedule_health, project_autopilot_snapshot, approval_control, compare_projects), so an agent can easily misselect among them. Descriptions differentiate focus (cost vs risk vs schedule vs approvals), which helps, but the boundaries remain fuzzy. BP-record tools (inspect_bp, list_bp_records, find_bp_record) also partially overlap.

    Naming Consistency4/5

    All tools share the unifier_ prefix and snake_case, giving a predictable, readable convention. Minor deviation: some are verb_noun (list_shells, find_bp_record, compare_projects) while others are noun-phrases (project_health, risk_center, cost_sheet_budget), but the style is uniformly lowercase snake_case. No camelCase/snake_case mixing.

    Tool Count3/5

    18 tools sits in the heavy-but-borderline band. Primavera Unifier is a broad, complex domain (shells, BPs, cost sheets, schedules, documents, permissions), so the count is defensible, but several dashboard-style tools arguably could be consolidated. It is not egregiously bloated, yet above the comfortable 3-15 range.

    Completeness3/5

    The surface is heavily read/analysis-oriented with broad coverage of shells, BPs, cost sheets, schedules, documents, and permissions. However, write operations are thin: only create_contract_with_attachments plus the generic rest_request escape hatch, with no explicit update/delete tools or workflow approve/reject actions. Core read workflows are covered but lifecycle write coverage has notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues