Skip to main content
Glama
Janadasroor

pg-mnemosyne-mcp

by Janadasroor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pg-mnemosyne-mcp

No user-submitted related servers found.

    Related Servers

    • ilma

      Brotal-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Framework-agnostic MCP server for agent memory with Postgres + pgvector, enabling persistent memory, recall, and task management across sessions.
      MIT

    • Multi Database MCP Server

      FreePeak
      A
      license
      Not graded
      quality
      A
      maintenance
      The Multi DB MCP Server is a high-performance implementation of the Database Model Context Protocol designed to revolutionize how AI agents interact with databases. Currently supporting MySQL and PostgreSQL databases.
      428
      MIT

    • MCP Agent Memory

      justanotherspy
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server that enables multiple AI agents to collaborate through a shared, concurrency-safe memory space. It supports advanced search, full CRUD operations, and automatic backups to facilitate asynchronous communication between agents.
      MIT

    • FastPostgresMCP

      llm-graph
      A
      license
      B
      quality
      D
      maintenance
      A blazing fast MCP server that enables AI agents to interact with multiple PostgreSQL databases, providing functionality to list tables, inspect schemas, execute queries, and run transactions.
      4
      65 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: schema initialization, CRUD for records, session management, and utility operations. There is no functional overlap between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using underscores, e.g., add_column, get_records, update_agent_session. The convention is uniform.

    Tool Count5/5

    With 12 tools, the surface is well-scoped for database management, covering setup, CRUD, session tracking, and utilities without being over- or under-engineered.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources