Skip to main content
Glama
thebgpikester

Mikes Moose MCP

by thebgpikester
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Mikes Moose MCP

No user-submitted related servers found.

    Related Servers

    • Grounded Code MCP

      michaelalber
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that gives AI coding assistants retrieval access to your personal knowledge base of books, standards, and docs, grounding their answers in sources you trust.
      MIT

    • exo

      guqing
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that ingests various data sources and uses LLMs to compile them into structured knowledge pages, enabling hybrid search and integration with AI coding tools like Claude Code and Cursor.
      14 npm
      1
      MIT

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      D
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      MIT

    • llms-mcp

      druellan
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes the llms.txt file and its referenced local or external resources from a project root to provide context for AI models. It automatically parses documentation links and URLs to make them accessible as additional MCP resources.
      1
      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.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a distinct role: search/lookup/class_tree for reference, example/practice for guidance, parse_log/tail_log for runtime analysis, and parse_mission for mission data. The only possible overlap is parse_log vs tail_log, but descriptions clearly separate full-session parsing from incremental tailing.

    Naming Consistency3/5

    All tools share the 'moose_' prefix and snake_case, but the suffix pattern mixes verbs (ingest, lookup, search, validate), nouns (example, practice, instances), and verb_noun compounds (parse_log, tail_log, parse_mission). This is readable but not a single consistent convention.

    Tool Count5/5

    With 11 tools, the server covers a comprehensive MOOSE workflow—indexing, querying, validating, log/mission parsing, and instance management—without excess. Each tool addresses a clear need, fitting well within the 3-15 sweet spot.

    Completeness4/5

    The tool set covers the major pillars of MOOSE development: framework reference, practice rules, runtime truth, mission truth, and validation. Minor gaps like removing indexed entries or listing all classes are workable via existing tools (e.g., re-ingest or search).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources