Vector Memory Mcp Server

Created By
Xsaven7 months ago
Vector Memory MCP Server A secure, vector-based memory server for Claude Desktop using sqlite-vec and sentence-transformers. This MCP server provides persistent semantic memory capabilities that enhance AI coding assistants by remembering and retrieving relevant coding experiences, solutions, and knowledge. ✨ Features 🔍 Semantic Search: Vector-based similarity search using 384-dimensional embeddings 💾 Persistent Storage: SQLite database with vector indexing via sqlite-vec 🏷️ Smart Organization: Categories and tags for better memory organization 🔒 Security First: Input validation, path sanitization, and resource limits ⚡ High Performance: Fast embedding generation with sentence-transformers 🧹 Auto-Cleanup: Intelligent memory management and cleanup tools 📊 Rich Statistics: Comprehensive memory database analytics 🔄 Automatic Deduplication: SHA-256 content hashing prevents storing duplicate memories 📈 Access Tracking: Monitors memory usage with access counts and timestamps for optimization 🧠 Smart Cleanup Algorithm: Prioritizes memory retention based on recency, access patterns, and importance
Overview

What is Vector Memory MCP Server?

Vector Memory MCP Server is a secure, vector-based memory server designed for Claude Desktop, utilizing sqlite-vec and sentence-transformers to provide persistent semantic memory capabilities. It enhances AI coding assistants by remembering and retrieving relevant coding experiences, solutions, and knowledge.

How to use Vector Memory MCP Server?

To use the Vector Memory MCP Server, install it via the uv package manager and configure it with Claude Desktop. You can run it directly using the command: uvx vector-memory-mcp --working-dir /path/to/your/project.

Key features of Vector Memory MCP Server?

  • Semantic Search: Vector-based similarity search using 384-dimensional embeddings.
  • Persistent Storage: SQLite database with vector indexing via sqlite-vec.
  • Smart Organization: Categories and tags for better memory organization.
  • Security First: Input validation, path sanitization, and resource limits.
  • High Performance: Fast embedding generation with sentence-transformers.
  • Auto-Cleanup: Intelligent memory management and cleanup tools.
  • Rich Statistics: Comprehensive memory database analytics.
  • Automatic Deduplication: Prevents storing duplicate memories using SHA-256 content hashing.

Use cases of Vector Memory MCP Server?

  1. Storing coding experiences and solutions for easy retrieval.
  2. Enhancing team workflows by sharing coding conventions and deployment procedures.
  3. Supporting individual developers in learning and growth by storing insights and debugging discoveries.

FAQ from Vector Memory MCP Server?

  • Can I use it for all programming languages?
    Yes, it is designed to store and retrieve memories related to any programming language.

  • Is it secure?
    Yes, it includes various security features such as input validation and path sanitization.

  • How does semantic search work?
    It uses sentence-transformers to convert memories into vectors that capture semantic meaning, allowing for effective similarity searches.

Server Config

{
  "mcpServers": {
    "vector-memory": {
      "command": "uvx",
      "args": [
        "vector-memory-mcp",
        "--working-dir",
        "/absolute/path/to/your/project"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
Xsaven
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago