Skip to main content
Glama
ZachHandley

ZMCPTools

by ZachHandley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ZMCPTools

No user-submitted related servers found.

    Related Servers

    • Claude-Flow

      EarthmanWeb
      A
      license
      Not graded
      quality
      D
      maintenance
      Multi-agent AI orchestration platform for Claude Code that enables deploying and coordinating specialized agents in swarms with self-learning, fault-tolerant consensus, and enterprise security.
      15,746 npm
      2
      MIT

    • Frood

      SalesTeamToolbox
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An AI agent platform with tiered LLM routing, semantic memory, and 48 MCP tools for Claude Code, enabling multi-agent orchestration and enhanced agent capabilities.
      2
      -

    • Symphony of One MCP

      ai-wes
      A
      license
      A
      quality
      F
      maintenance
      A multi-agent orchestration system that enables multiple Claude instances to collaborate through a centralized hub with a shared workspace and real-time communication. It features integrated task management, role assignment, and persistent memory to facilitate complex, synchronized agent workflows.
      12
      3 npm
      4
      MIT

    • Twining MCP Server

      daveangulo
      A
      license
      A
      quality
      A
      maintenance
      Provides agent coordination for Claude Code through a shared blackboard, decision tracking with rationale, and local semantic search over git-trackable JSONL files. It enables users to assemble tailored context packages and manage a lightweight knowledge graph for complex development tasks.
      15
      159 npm
      7
      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

    C2.7/5.0

    Scored across 70 tools

    Disambiguation2/5

    Many tools overlap in purpose, especially legacy and modern versions (e.g., navigate_to_url vs navigate_and_scrape, take_screenshot vs interact_with_page). Multiple cleanup, orchestration, and browser session management tools have ambiguous boundaries, increasing the risk of misselection.

    Naming Consistency2/5

    Naming conventions are inconsistent: mix of snake_case and verb_noun (e.g., easy_replace, spawn_agent), deprecated tools mixed with current ones, and varied verb choices (list/get/find, create/delete/remove). No clear pattern is enforced.

    Tool Count2/5

    70 tools is excessive, especially with many legacy duplicates that should have been removed. The scope is broad but could be consolidated into fewer, more focused tools. The count is far beyond the typical well-scoped range.

    Completeness3/5

    The server covers many domains but lacks full CRUD in some areas (e.g., knowledge graph missing delete/update for relationships and memories). Legacy tools indicate dead ends, and while core workflows exist, notable gaps remain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources