pg-mnemosyne-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PG_BASE_DSN | Yes | Standard PostgreSQL connection string: postgresql://<USERNAME>:<PASSWORD>@<HOST>:<PORT>/<DEFAULT_DB> |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_project_dbB | Creates a new PostgreSQL database for a project. |
| init_schemaC | Initializes the base 'records' table in the specified database. |
| init_todo_schemaC | Initializes a professional 'tasks' table in the specified database. |
| init_coordination_schemaC | Initializes the 'agent_sessions' table for multi-agent coordination. |
| update_agent_sessionA | Updates or registers the active task and state of an agent in the database (thread-safe upsert). |
| get_active_sessionsC | Retrieves all registered agent coordination sessions ordered by last active time. |
| add_columnB | Adds a new column to a table dynamically. |
| run_sqlC | Executes arbitrary SQL queries and returns results as JSON. |
| add_recordC | Adds a new memory/task record. |
| get_recordsC | Retrieves recent records from the database. |
| delete_recordC | Deletes a record from the database by its ID. |
| update_recordC | Updates a record in the database by its ID. Only non-None fields will be updated. |
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 12 tools
Each tool has a distinct purpose: schema initialization, CRUD for records, session management, and utility operations. There is no functional overlap between tools.
All tools follow a consistent verb_noun pattern using underscores, e.g., add_column, get_records, update_agent_session. The convention is uniform.
With 12 tools, the surface is well-scoped for database management, covering setup, CRUD, session tracking, and utilities without being over- or under-engineered.
Core record CRUD and session management are present, but there are no specific tools for task CRUD (only init_todo_schema) and no schema deletion or modification beyond add_column. Gaps require use of run_sql.