Skip to main content
Glama
zivhdinfo

mcp-view

by zivhdinfo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-view

No user-submitted related servers found.

    Related Servers

    • kairan

      ukwhatn
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI agents publish markdown/HTML to a browser viewer with session management, revision diffs, and live updates via a single tool call.
      2
      MIT

    • Copilot Leecher

      xiangxiaobo
      F
      license
      A
      quality
      Not graded
      maintenance
      An MCP server that enables users to review and refine AI outputs through a local web UI, returning feedback as free tool call results to save on GitHub Copilot premium requests. It allows for multiple rounds of iterative improvements within a single request session.
      1
      30
      -

    • better-mcp

      erquier
      A
      license
      A
      quality
      B
      maintenance
      A universal MCP server that provides AI agents with structured tools for filesystem, database, shell, and git operations, enabling seamless interaction with projects.
      19
      MIT

    • ToolCenter MCP

      toolcenter-dev
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive MCP server providing 15 web tools including search, scraping, screenshots, SEO audits, and DNS/SSL checks through a single installation. It delivers clean, LLM-optimized outputs so AI agents can focus on reasoning rather than parsing raw HTML.
      15
      9 npm
      MIT

    • noit-mcp-server

      Yuki-az-23
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to manage STAR-pattern architecture diagrams, creating, updating, listing, and building interactive viewers via tool calls.
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct phase: planning before work, reporting after work, and standalone diagramming. Even though all produce web pages, their intended invocation context is clearly separated. No overlap that would confuse an agent.

    Naming Consistency5/5

    All three tools share a consistent 'view_' prefix followed by a specific noun (plan, report, diagram). This creates a predictable pattern that makes it easy to guess the tool for a given need. No mixed conventions.

    Tool Count5/5

    3 tools is well-scoped for a focused presentation server. Each tool covers a distinct need and none feel redundant. This falls comfortably in the ideal range.

    Completeness5/5

    The server's domain is showing plans, reports, and diagrams on a web page. It covers the before-work, after-work, and standalone diagram cases. Optional diagram inclusion in plan/report fills any cross-cutting need, so no gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources