Skip to main content
Glama
sangaraju1988

amu-pgvector

by sangaraju1988
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to amu-pgvector

No user-submitted related servers found.

    Related Servers

    • mcp-postgres-guard

      vladshykanov
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI agents to securely interact with PostgreSQL databases with least-privilege scopes, PII masking, and human approval for writes.
      4
      MIT

    • memgate

      Denizayhan04
      A
      license
      Not graded
      quality
      C
      maintenance
      Access control, conflict resolution, and audit for shared agent memory. Policy-gated memory tools over Postgres + pgvector, exposed via MCP.
      1
      Apache 2.0

    • butler-memory-mcp

      AndyYang12345
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing layered, PostgreSQL-backed long-term memory for AI agents with versioned, audited writes and sensitive candidate filtering. Agents persist only explicitly requested facts, preferences, and project context via MCP tools.
      Apache 2.0
    • nlqdb by nlqdb

      nlqdbofficial

      nlqdb
      A
      license
      A
      quality
      A
      maintenance
      Analytical memory for AI agents: a real Postgres your agent connects to over MCP and queries in plain English — GROUP BY, JOIN, aggregate over what it remembered, not just top-k vector recall.
      7
      2
      Functional Source , Version 1.1, ALv2 Future

    • pgmnemo

      pgmnemo
      A
      license
      Not graded
      quality
      A
      maintenance
      Agent memory as a PostgreSQL extension: hybrid HNSW+BM25 recall, write-time provenance gates, and outcome-weighted confidence. The MCP server exposes ingest and recall tools over stdio for Claude Code, Codex CLI, and Gemini CLI.
      8
      Apache 2.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools map to distinct operations: a pre-write conflict check, a write, and a semantic read. amu_check_conflict and amu_search both read from the AMU store, which could momentarily overlap, but their descriptions (exact metric_name/hash match vs. natural-language similarity query) clearly separate them.

    Naming Consistency4/5

    All tools share a consistent amu_ prefix and use lowercase snake_case, so the set reads as a coherent family. Minor deviation: amu_check_conflict follows verb_noun while amu_record and amu_search are bare verbs, but this is still readable and predictable.

    Tool Count4/5

    With only 3 tools the surface is on the lean side, but each tool is well-scoped to a distinct step of the AMU lifecycle (record, retrieve, conflict-check), so nothing feels redundant or padded. It is slightly under-provisioned rather than excessive.

    Completeness3/5

    The core write/search/conflict-check loop is covered, but there is no way to fetch or list an AMU by identifier or metric_name outside of a semantic query, and no update/delete path (which may be intentional for immutable, lineage-gated memory). These are notable gaps an agent would hit when trying to enumerate or revisit known AMUs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources