Jamgate

io.github.amirj4mPublished by GitHub account amirj4mv0.20.0Updated Oct 24, 2026

A neutral memory quality-gate MCP server: save_memory, recall_memory, forget_memory over stdio.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

A local memory quality-gate MCP server that lets an assistant save, recall, and forget stored memories over stdio.

What you can do
Jamgate exposes three tools — save_memory, recall_memory, and forget_memory — over a local stdio connection. It acts as a memory quality gate, letting an assistant persist information, retrieve it later, and remove entries it no longer needs. It is a desktop-only local process, so the memory store lives on the user's machine rather than a remote service.
When to use it
Worth adding when an assistant should keep durable notes or context across sessions and the user wants that memory kept locally. Suitable for workflows where saving, recalling, and deleting remembered items is enough, without a hosted memory service.
Requirements
Runs as a local process on the user's machine, installed from the npm package jamgate over stdio. Desktop only; no web execution. No authentication, environment variables, or headers are declared.
Before you install
The server can write, read, and delete stored memories, so anything saved may persist on the local machine and be recalled later. Review what the assistant is allowed to remember, and confirm that forget_memory actually removes entries when needed.

Installation

In SourceWeft

  1. Open Jamgate 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.20.0LatestSep 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.