
Seam Runtime
io.github.BlackhatShifteyPublished by GitHub account BlackhatShifteyv1.3.1Updated Oct 24, 2026
SEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP.
Overview
SEAM is a local-first memory runtime that gives an AI assistant persistent memory with retrieval and provenance over MCP.
- What you can do
- Store and recall agent memory in a local SQLite database, with an optional Postgres/pgvector vector adapter for embeddings-based retrieval. Retrieve stored memories and inspect where they came from through glassbox provenance. Runs entirely on the user's machine over stdio, keeping memory local by default.
- When to use it
- Worth adding when you want an assistant to keep memory across sessions on your own machine, and to be able to trace where a recalled memory came from. Useful for local-first agent setups that prefer SQLite over a hosted memory service.
- Requirements
- Runs as a local process via uvx from the PyPI package seam-runtime. Optionally set SEAM_DB_PATH to choose the SQLite memory database location; it defaults to a per-user data directory. Optionally set SEAM_PGVECTOR_DSN to use Postgres/pgvector instead of the built-in SQLite vector store.
Installation
In SourceWeft
- Open Seam Runtime in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.3.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.