Developer · Local MCP server
MemAuthority
Git-backed long-term memory authority for AI agents via MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.iasi777/memauthority- Version
- 1.3.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- MCP Bundle (.mcpb)
- Published
- 2026-09-03
- Updated
- 2026-09-03
- Publisher
- iasi777 (GitHub)
- Repository
- github.com/iasi777/memauthority
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-x64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-arm64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-x64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-arm64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-x64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
| MCP Bundle (.mcpb) | https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-arm64.mcpbSHA-256 checksum stated | 1.3.2 | stdio |
How to connect MemAuthority
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-x64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-arm64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-x64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-arm64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-x64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
MemAuthority runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-arm64.mcpb version 1.3.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Melt MCP ServerMelt: value-leak discovery and lead capture for Claude, Cursor, and MCP-compatible agents. | Local · stdio |
| Mem ContextTemporal memory MCP server with LanceDB vector search, weight-decay scoring, and LLM consolidation. | Local · stdio |
| Mem0 CloudA hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):... | Remote · HTTP |
| MemantoMCP server for Memanto - persistent semantic memory for any MCP-compatible agent. | Local · stdio |
| MemCellLiving memory for AI coding agents: recall before acting, report outcomes so confidence is earned. | Remote & Local · HTTP, stdio |
| MemdocsGit-native project memory for AI assistants with audit compliance. | Local · stdio |
| MementoLocal-first, LLM-agnostic memory layer for AI assistants. | Local · stdio |
| MementoAgent memory MCP server with 4-type cognitive memory, hybrid search, and TTL-based forgetting. | Local · stdio |