Skip to main content
Glama
gavinsomers

obsidian-mcp-context

by gavinsomers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to obsidian-mcp-context

No user-submitted related servers found.

    Related Servers

    • obsidian-mcp

      nakielski
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM clients to read, search, and write to a local Obsidian vault over MCP, with full-text search, vault analytics, health scoring, and policy-enforced file operations.
      MIT

    • Obsidian MCP Server

      andysama-work
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes an Obsidian notes vault as MCP services, enabling AI assistants to search, read, create, update, and delete notes and folders.
      8 npm
      1
      MIT

    • obsidian_mcp

      troxeldj
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables reading, writing, searching, and managing Obsidian vault notes through MCP tools and prompts, allowing AI agents to interact with local knowledge bases.
      -

    • Recalla

      Tensorboyalive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and search your Obsidian vault through a local MCP server, keeping everything private and local.
      Apache 2.0
    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

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a specific aspect of the vault context: get operations for different entity types (entity, note, person, project), list operations for distinct entity attributes (decisions, risks, open loops, tasks, etc.), and search operations. There is no meaningful overlap; every tool has a clearly distinct purpose.

    Naming Consistency5/5

    All tools follow a consistent verb_vault_noun pattern with snake_case (e.g., get_vault_entity_context, list_vault_entities, search_vault_blocks). The use of 'vault' as a prefix is uniform, and the verbs are limited to get, list, and search. Minor singular/plural variations (entity vs. entities) do not disrupt the predictable structure.

    Tool Count4/5

    With 19 tools, the server is slightly above the typical well-scoped range (3-15) but still reasonable given the breadth of entity types and operations. Each tool seems justified for the domain of vault context retrieval, so the count is appropriate.

    Completeness4/5

    The tool set covers a wide range of read operations: getting specific entity contexts, listing various entity attributes and events, and searching. Minor gaps exist, such as the absence of get operations for individual decisions, risks, or tasks (only list is available). However, agents can still retrieve needed information through filtering, so the surface is nearly complete for a read-only context server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources