mcp-server-pgvector
Related Servers
Alternatives to mcp-server-pgvector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA self-hostable MCP server that provides permanent memory for AI agents using Postgres + pgvector for semantic search and Markdown file sync.0MIT
- AlicenseNot gradedqualityDmaintenanceMCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB547Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables hybrid semantic and keyword retrieval over your documents, using PostgreSQL and pgvector as the backend. It fuses rankings from both methods to provide high-quality search results to the language model.MIT
- AlicenseAqualityDmaintenanceA production-grade MCP server that gives AI agents safe, authenticated access to a PostgreSQL database.3MIT
- AlicenseNot gradedqualityCmaintenanceFramework-agnostic MCP server for agent memory with Postgres + pgvector, enabling persistent memory, recall, and task management across sessions.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing persistent AI memory using hybrid search (keyword + semantic vector) with SQLite storage and offline-first local embeddings.-
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: discovery (list_vector_tables, describe_vector_table), search (similarity_search, hybrid_search), data modification (upsert_embedding), indexing (create_vector_index), and diagnostics (explain_similarity_query). No two tools overlap in purpose.
All tools follow a consistent verb_noun snake_case pattern (list_, describe_, create_, upsert_, explain_) or use noun_verb for search operations. The naming style is uniform and predictable.
Seven tools is well within the ideal 3-15 range. Each tool earns its place, covering discovery, search, ingestion, indexing, and query analysis without redundancy.
The toolkit covers the core pgvector workflow: list tables, describe schema, create index, upsert vectors, search, and explain query plans. Minor gaps like a delete_embedding or drop_index tool are missing, but they are not essential for the primary use case.