Pg-Mnemosyne MCP
A Model Context Protocol (MCP) server that provides AI assistants with a robust "super memory", task tracker, and dynamic PostgreSQL database management capabilities.
⚡ Quick Start
-
Install the package globally:
- Windows:
pip install pg-mnemosyne-mcp
- macOS / Linux:
pipx install pg-mnemosyne-mcp
(If you prefer standard pip or don't havepipx, run:pip install pg-mnemosyne-mcp --break-system-packages)
- Windows:
-
Auto-configure all your AI agents (Claude, Gemini, Qwen, Cursor, etc.) at once:
pg-mnemosyne init --dsn "postgresql://user:password@localhost:5432/postgres"
(Be sure to replace
userandpasswordwith your actual PostgreSQL username and database password!) -
Restart your AI agents. You're done!
Features
- High-Performance: Uses cached connection pooling (
asyncpg.create_pool) for instant sub-millisecond database queries. - Dynamic Projects: The AI can create new databases for different projects on the fly.
- Dynamic Schema: The AI can modify table schemas dynamically to adapt to changing memory needs.
- Standard Memory Tracker: Built-in support for tracking, updating, and deleting memory items with tags.
- Advanced Task Management: Dedicated tasks schema with fields for status transitions, priority, and deadlines.
- Multi-Agent Coordination: Centralized session tracking preventing duplicate coding and file-editing conflicts.
- Raw SQL Execution: Gives AI ultimate flexibility for complex queries and DDL operations.
Setup
Users will need to provide their PostgreSQL credentials using the PG_BASE_DSN environment variable. This is a standard connection string:
postgresql://<USERNAME>:<PASSWORD>@<HOST>:<PORT>/<DEFAULT_DB>
Where to configure this (Client Setup)
The exact location depends on which AI client you are using. You need to add the server configuration to your client's MCP settings file.
For Claude Desktop:
- Mac:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
For Cursor:
- Go to
Settings>Features>MCPand add a new MCP server, or edit your project's.cursor/mcp.json.
For Roo Code / Cline (VS Code):
- Edit the MCP settings file located at
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json(Mac) or the equivalent Windows path.
For Gemini CLI & Qwen CLI:
- Open your global configuration file (usually located at
~/.gemini/settings.jsonor~/.qwen/settings.json). - Alternatively, use the CLI:
gemini mcp add pg-mnemosyne "/path/to/pg-mnemosyne" -e PG_BASE_DSN="postgresql://user:pass@localhost:5432/postgres" -s user # OR qwen mcp add pg-mnemosyne "/path/to/pg-mnemosyne" -e PG_BASE_DSN="postgresql://user:pass@localhost:5432/postgres" -s user
For Claude Code CLI:
- The easiest way is to add it via the CLI:
claude mcp add pg-mnemosyne "/path/to/pg-mnemosyne" -e PG_BASE_DSN="postgresql://user:pass@localhost:5432/postgres" -s user
- Manually, it lives in your global config at
~/.claude.json.
For Codex CLI:
- The easiest way is to add it via the CLI:
codex mcp add pg-mnemosyne --env PG_BASE_DSN="postgresql://user:pass@localhost:5432/postgres" -- pg-mnemosyne
- Manually, it lives in your global config at
~/.codex/config.toml(TOML format).
For Windsurf IDE:
- Edit your global config at
~/.codeium/windsurf/mcp_config.json. - Alternatively, click the Hammer (MCP) icon in the Cascade panel and select Configure.
For Antigravity CLI (agy): Antigravity uses a plugin-based system. To add the server:
- Create a plugin directory:
mkdir -p ~/.gemini/config/plugins/pg-mnemosyne - Create
~/.gemini/config/plugins/pg-mnemosyne/mcp_config.jsonwith the Standard Template below. - Add an entry to your
~/.gemini/config/import_manifest.jsonunder the"imports"array:{ "name": "pg-mnemosyne", "source": "manual", "components": ["mcpServers"] }
Configuration Template (Claude Desktop, Cursor, Roo Code, Gemini CLI, Claude Code, Antigravity, Windsurf):
{
"mcpServers": {
"pg-mnemosyne": {
"command": "pg-mnemosyne",
"env": {
"PG_BASE_DSN": "postgresql://postgres:my_password@localhost:5432/postgres"
}
}
}
}
For OpenCode:
- Edit your OpenCode configuration file located at
~/.config/opencode/opencode.jsonc.
Configuration Template (OpenCode):
{
"mcp": {
"pg-mnemosyne": {
"type": "local",
"command": ["pg-mnemosyne"],
"environment": {
"PG_BASE_DSN": "postgresql://postgres:my_password@localhost:5432/postgres"
}
}
}
}
Running the Server (Standalone)
pg-mnemosyne run
This starts the MCP server using standard input/output.
CLI Usage
The pg-mnemosyne command also acts as a standalone CLI for managing your data and configuring agents.
Auto-Initialization
You can automatically configure all supported AI agents (Claude, Gemini, Qwen, Cursor, etc.) with a single command:
pg-mnemosyne init --dsn "postgresql://user:pass@localhost:5432/postgres"
Manual Record Management
You can add and list records directly from your terminal:
# Add a record
pg-mnemosyne add my_project_db todo "Finish the documentation"
# List records
pg-mnemosyne list my_project_db --type todo
🤝 Multi-Agent Coordination & Advanced Tasks
Pg-Mnemosyne includes specialized schemas to help complex multi-agent setups (e.g. Gemini CLI, Codex CLI, Roo Code, Claude Desktop) coordinate on the same project:
📋 Professional Tasks Schema
Spin up a dedicated tasks table with fields for statuses (backlog, todo, in_progress, blocked, done), priority levels (low, medium, high, critical), tags, and deadlines:
pg-mnemosyne init-todo my_project_db
🛰️ Agent Coordination Hub
Avoid merge conflicts, double-coding, and redundant compiler troubleshooting by initializing the shared agent_sessions coordination table:
pg-mnemosyne init-coordination my_project_db
When active, agents use the update_agent_session and get_active_sessions MCP tools to register their current editing files and active subtasks, creating a real-time bulletin board for mutual visibility!
Available MCP Tools
create_project_db(db_name: str): Creates a new isolated PostgreSQL database.init_schema(db_name: str): Initializes the baserecordstable.init_todo_schema(db_name: str): Initializes a professionaltaskstable.init_coordination_schema(db_name: str): Initializes the multi-agentagent_sessionstable.add_column(db_name: str, table: str, column_name: str, data_type: str): Dynamically adds a column to any table.add_record(db_name: str, type: str, content: str, tags: list[str]): Adds a memory/todo record.get_records(db_name: str, type: str = None, limit: int = 50): Retrieves recent records.update_record(db_name: str, record_id: int, content: str = None, tags: list[str] = None, status: str = None): Partially updates a record.delete_record(db_name: str, record_id: int): Deletes a record by ID.update_agent_session(db_name: str, agent_name: str, active_task: str, active_file: str = None, status: str = "active"): Registers/updates active agent state.get_active_sessions(db_name: str): Lists active agent coordination sessions.run_sql(db_name: str, query: str): Runs arbitrary SQL (SELECT, INSERT, DDL, etc.).
Metadata
Release files for pg-mnemosyne-mcp 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pg_mnemosyne_mcp-0.1.6.tar.gz | 887.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pg_mnemosyne_mcp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 899.4 kB
Release files / pg_mnemosyne_mcp-0.1.6.tar.gz
| Download URL | pg_mnemosyne_mcp-0.1.6.tar.gz |
|---|---|
| Size | 887.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b53093a6d7d64779ab9f7fb0f9ec4f2f9998ecad2ec1ee1054302cfd330e41a
|
|
BLAKE2b-256 checksum How to use checksums |
b81ecf45a09004fb746cbc1170a30e9f223f73caf460668c6ace61d033e74e77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logRelease files / pg_mnemosyne_mcp-0.1.6-py3-none-any.whl
| Download URL | pg_mnemosyne_mcp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6016cac222c57a7ebb41904fa98e0d57c8ed0bdf180594dd85297a8ccfbfd17a
|
|
BLAKE2b-256 checksum How to use checksums |
4d251724d3ccb3181721b3ac290f796972bdb8da1b96b3bff071074ca4f3acdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logSecurity for pg-mnemosyne-mcp 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pg_mnemosyne_mcp-0.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.