Obsidian Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesB | Create multiple new entities in the knowledge graph |
| create_relationsB | Create multiple new relations between entities in the knowledge graph. Relations should be in active voice |
| add_observationsB | Add new observations to existing entities in the knowledge graph |
| delete_entitiesA | Delete multiple entities and their associated relations from the knowledge graph |
| delete_observationsB | Delete specific observations from entities in the knowledge graph |
| delete_relationsA | Delete multiple relations from the knowledge graph |
| read_graphB | Read the entire knowledge graph |
| search_nodesC | Search for nodes in the knowledge graph based on a query |
| open_nodesC | Open specific nodes in the knowledge graph by their names |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific operations on the knowledge graph: adding/deleting observations, creating/deleting entities/relations, opening/reading/searching nodes. No overlap exists; for example, 'create_entities' and 'create_relations' are distinct, and 'open_nodes' and 'search_nodes' serve different access functions.
All tools follow a consistent verb_noun pattern with snake_case throughout: 'add_observations', 'create_entities', 'delete_relations', etc. The naming is predictable and readable, with verbs like 'add', 'create', 'delete', 'open', 'read', and 'search' applied consistently to their respective nouns.
With 9 tools, the count is well-scoped for managing a knowledge graph, covering core operations like CRUD for entities, relations, and observations, plus graph access. Each tool earns its place without bloat, fitting a typical range of 3-15 tools for this domain.
The tool set provides strong coverage for knowledge graph management, including create, read, delete, and search operations. A minor gap exists in update capabilities (e.g., no 'update_entities' or 'update_relations'), but agents can work around this by deleting and recreating, and core workflows are well-supported.