Skip to main content
Glama
dawnmcp

DawnMCP

Official
by dawnmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DawnMCP

No user-submitted related servers found.

    Related Servers

    • LocalNest MCP

      wmt-mobile
      A
      license
      B
      quality
      C
      maintenance
      A local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.
      74
      14
      6
      MIT

    • Context Engine MCP Server

      Kirachon
      F
      license
      B
      quality
      A
      maintenance
      A local-first, agent-agnostic MCP server that provides semantic search, persistent memory, and automated code review capabilities for development workflows. It leverages the Auggie SDK to offer advanced tools for codebase indexing, implementation planning, and deterministic static analysis.
      52
      48
      -

    • codeweave

      MdAbdullahAlMahmud
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that indexes your codebase and provides AI assistants with deep context including file tree, full-text search, git history, dependencies, and stack detection, all without sending your code to third parties.
      15
      1
      MIT

    • itaca

      Lukapetro
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that indexes all projects on your machine and provides coding agents with briefings about each project's stack, services, and run instructions, so they can start sessions with context across all repos. No cloud, no accounts, no telemetry.
      8
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation3/5

    Most tools have clearly distinct purposes, but there are close overlaps among repo_explain_architecture, repo_explain_project, and repo_summarize_repository, as well as between repo_analyze_repository and repo_scan_files. Descriptions help, but an agent could confuse these similar-sounding tools.

    Naming Consistency4/5

    Names follow a consistent category_verb_noun pattern with underscores (e.g., documents_add_document, memory_search_memory, repo_index_repository). Minor deviations exist in plural/singular forms (search_documents vs add_document) and semantically similar verbs like 'explain' versus 'summarize', but overall the pattern is predictable.

    Tool Count3/5

    At 23 tools, the set is on the heavier side. The four domains each justify their existence, but the repo category has 11 tools, with several overlapping analysis/explanation options that could be consolidated. Still, it's within a workable range.

    Completeness4/5

    Documents and memory have near-complete CRUD coverage (missing document update), and repo tools cover scanning, indexing, analysis, and querying. Agent tools provide plan/execute/review/debug lifecycle. Minor gaps like no repository unindex or knowledge graph deletion, but core workflows are well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources