Skip to main content
Glama
plugandship-mcp

plugandship-mcp

Official
by plugandship

Related Servers

Alternatives to plugandship-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients such as Claude, Cursor, VS Code and Codex search a hand-checked directory of MCP servers, AI plugins and agent tools, returning summaries, copy-paste install configs and setup guides. Also supports keyword and category browsing plus troubleshooting guide lookups, working offline from a bundled snapshot when needed.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Search and inspect 50,000+ Agent Skills (SKILL.md) for Claude Code, Codex and other agents, with trending, curated picks, author lookup and pinned install metadata. Read-only. The server lives in the repo's mcp/ folder, which is open source under MIT (mcp/LICENSE), and is published to npm as omgskills-mcp.
      5
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language search of 378 curated AI agent frameworks, developer tools, and automation repositories from inside Claude Code, Cursor, Codex, or any MCP-compatible client, returning matching repos with descriptions instead of manual GitHub browsing. Also exposes category listing, stats, and single-repo lookup.
      -
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.
      3
      49 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct role: list_best surfaces curated topic rankings, search_tools queries the index, get_tool fetches one slug's detail, and trending ranks new items by star velocity. The only mild overlap is between list_best and trending, both being ranked lists, but their framing (topic vs recency) keeps them separable.

    Naming Consistency4/5

    Three tools follow a clean verb_noun pattern (list_best, search_tools, get_tool). trending breaks the pattern with a bare gerund/noun, a minor deviation but not confusing.

    Tool Count4/5

    Four tools is on the lean side but fits a compact directory/index API where search plus detail plus two curated views is the core surface. Nothing feels redundant or dead-weight.

    Completeness4/5

    The lifecycle of discover (search_tools/list_best/trending) and inspect (get_tool) is covered, and list_best with no topic effectively enumerates topics. Minor gaps exist, such as tag/language filtering or explicit topic enumeration, but the core workflow is intact.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues