Skip to main content
Glama

Related Servers

Alternatives to codelore-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude Code with deep access to an Obsidian vault through 28 tools for structural analysis, semantic retrieval, and git-backed timeseries tracking. It transforms your vault into a live knowledge base that Claude can search, navigate, and reason about using its knowledge graph.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Give Claude (and any MCP client) real agent access to your Obsidian vault — graph traversal, Dataview queries, daily-note awareness, and more.
      25
      22 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to search, read, list, and inspect an Obsidian vault stored in a GitHub repository through callable MCP tools, including during unattended scheduled runs.
      10,776 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude with read, search, and write access to an Obsidian vault through MCP tools.
      10,776 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude AI direct access to your Obsidian vault, enabling natural language search, note creation, file management, and automated workflows.
      10,776 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Bidirectional MCP server that connects Claude with an Obsidian vault, enabling note management, full-text search, graph traversal, and daily notes operations.
      3,358 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: estimation, exploration, search, ingestion, syncing, etc. There is no overlap or ambiguity in their purposes.

    Naming Consistency5/5

    All tool names follow the verb_noun snake_case pattern consistently (e.g., estimate_cost, explore_repo, find_todos). Even informal terms like 'todos' fit the pattern.

    Tool Count5/5

    10 tools cover the full lifecycle of repository ingestion and querying without being excessive or thin. The count is well-scoped for the server's purpose.

    Completeness4/5

    The tool set covers estimation, ingestion, exploration, search, syncing, and annotation assistance. Missing a delete tool, but the core workflows are complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues