Skip to main content
Glama
rushireddy143

customplanview MCP server

Related Servers

Alternatives to customplanview MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Model Context Protocol server for Parseable that lets MCP-capable clients discover, query, and manage Parseable datasets and alerts using natural language. Supports both stdio and HTTP transports.
      48 npm
      4
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables local text analysis, statistical calculations, and system information retrieval via the Model Context Protocol over stdio.
      -
    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for accessing Productive.io API endpoints (projects, tasks, comments, todos), tailored for read-only operations, providing streamlined access to essential data while minimizing token consumption
      18
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables querying Teamhood workspaces, users, boards, items, and time logs through the Teamhood Open API, running locally via stdio so your API key stays on your machine.
      10
      -

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: list all portfolios, get one by identifier, and search by text query. No two tools could reasonably be confused for the same operation, and the descriptions make the boundaries explicit.

    Naming Consistency5/5

    All tools follow the same predictable pattern: the planview_ prefix plus verb_noun (list_portfolios, get_portfolio, search_portfolios). The convention is consistent in both prefix and snake_case style.

    Tool Count4/5

    Three tools is a minimal but reasonable set for a portfolio-focused read surface. It is slightly under-scoped for a server named customplanview, which might be expected to cover more Planview entities.

    Completeness3/5

    The read surface for portfolios is fairly complete with list, get, and search, but there are no create, update, or delete operations. For a portfolio management domain, those missing lifecycle operations are a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues