mcp-memory-libsql
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIBSQL_URL | No | The URL of the libSQL database. Use 'file:/path/to/database.db' for local SQLite databases or 'libsql://your-database.turso.io' for remote libSQL databases | file:/memory-tool.db |
| LIBSQL_AUTH_TOKEN | No | Authentication token for remote libSQL databases (e.g., Turso) |
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 new entities with observations and optional embeddings |
| search_nodesC | Search for entities and their relations using text or vector similarity |
| read_graphB | Get recent entities and their relations |
| create_relationsC | Create relations between entities |
| delete_entityA | Delete an entity and all its associated data (observations and relations) |
| delete_relationC | Delete a specific relation between entities |
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 6 tools
Every tool has a clearly distinct purpose: create_entities and create_relations handle creation of different data types, delete_entity and delete_relation handle deletion of different data types, read_graph retrieves recent data, and search_nodes performs searches. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern using snake_case: create_entities, create_relations, delete_entity, delete_relation, read_graph, and search_nodes. The naming is predictable and uniform throughout the set.
With 6 tools, this server is well-scoped for a memory/graph database system. Each tool serves a clear and necessary function (create, delete, read, search) without being too sparse or bloated, fitting typical expectations for such a domain.
The toolset covers core CRUD operations for entities and relations (create, delete, read, search), but lacks explicit update tools for modifying existing entities or relations. Agents can work around this by deleting and recreating, but it's a minor gap in lifecycle coverage.