MCP.so
Sign In

Lipsky Memory MCP

@Lipdog

About Lipsky Memory MCP

Multi-project memory MCP - A Model Context Protocol server for managing project memory and context

Basic information

Category

Memory & Knowledge

Transports

stdio

Publisher

Lipdog

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Lipsky Memory MCP?

Lipsky Memory MCP is a Model Context Protocol server designed to manage project memory and context. It persists data using a Turso database and is currently working in the Cline environment, making it suitable for AI assistants that need to track project entities, relationships, and transactional context.

How to use Lipsky Memory MCP?

Set the LIBSQL_URL and LIBSQL_AUTH_TOKEN environment variables to configure the Turso database connection. The server is invoked as an MCP tool within a host environment like Cline; no specific startup command is provided in the README.

Key features of Lipsky Memory MCP

  • Project context management
  • Entity and relationship tracking
  • Memory persistence using Turso
  • Transaction support

Use cases of Lipsky Memory MCP

  • Maintaining long-term memory across AI assistant sessions for a project
  • Tracking relationships between project components, tasks, or concepts
  • Persisting contextual data that survives conversation restarts

FAQ from Lipsky Memory MCP

What does Lipsky Memory MCP do?

It manages project memory and context, storing entities, relationships, and transactional data in a Turso database for AI assistants.

What dependencies or runtime does it require?

It requires a Turso database instance and the LIBSQL_URL and LIBSQL_AUTH_TOKEN environment variables to connect.

Where is data stored and persisted?

All data is stored in the Turso database configured by the LIBSQL_URL environment variable.

Are there any known limits or issues?

The README notes connection issues in the HyperChat environment as a known issue.

What transport or authentication does it use?

No transport or authentication details beyond the Turso database token are specified in the README.

Comments

More Memory & Knowledge MCP servers