Memforge Memory

io.github.volsierPublished by GitHub account volsierv1.0.1Updated Oct 24, 2026

Team engineering memory for AI coding assistants. 47 MCP tools, pgvector semantic search.

The publisher's own server: Memory.fit

Overview

AI-generated overview

Gives AI coding assistants a shared team engineering memory backed by PostgreSQL and pgvector semantic search.

What you can do
Memforge Memory provides a team engineering memory layer for AI coding assistants, exposing a large set of MCP tools (the description states 47) for storing and retrieving engineering knowledge. Retrieval uses pgvector semantic search, so entries are matched by meaning rather than keywords. It runs locally over stdio and connects to a PostgreSQL database for storage.
When to use it
Worth adding when a team wants coding assistants to recall shared engineering context, such as past decisions, notes, or project knowledge, across sessions and members. Useful if you already run PostgreSQL with pgvector and want semantic recall rather than a per-user local memory.
Requirements
Runs as a local process via the npm package @memforgeai/memory-service over stdio, on desktop only. Requires a PostgreSQL connection string in DATABASE_URL, an embedding API key in OPENAI_API_KEY, an OpenAI-compatible embedding base URL in OPENAI_BASE_URL, and an embedding model name in OPENAI_EMBEDDING_MODEL. Network access is needed for the embedding API.
Before you install
The server requires the secret OPENAI_API_KEY, which is sent to the embedding endpoint configured in OPENAI_BASE_URL; if that URL points to a third party, embedding requests and the text being embedded go there. DATABASE_URL grants access to your PostgreSQL instance, so scope the credentials narrowly. The tools can write stored memory entries, so review what gets persisted.

Installation

In SourceWeft

  1. Open Memforge Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations