agentmem
Memory for coding agents that tracks whether each fact is still true — hypothesis, active, validated, deprecated, superseded.Read full description
ThezenmonsterLABSCO SUMMARY
Read-only on purpose, which narrows what a bad prompt can do.
Agent memory is the kind of store where a delete tool is a liability, and this one does not ship with any. The token is the whole access model — one bearer credential, claimed once — so treat losing it as losing the account, and paste only the token value into your client rather than the full header.
What it is
A paid remote MCP server for persistent agent memory, run by the vendor. There is no local process: you point a client at a URL and authenticate with a bearer token.
What you get
- A fixed tool surface for agent memory, plus analytics and search-readiness, reachable over Streamable HTTP
- A published server card at a
.well-knownURL, so a client can discover the server's capabilities before connecting - A deliberate capability boundary: no arbitrary shell execution, no arbitrary SQL, no deployment controls, no deletion tools, no edits to payment configuration
Requirements
Version 0.1.0, hosted at https://agentmemory.space/mcp over Streamable HTTP — nothing to install. Any client that supports remote Streamable HTTP servers will do; configure the URL and pass Authorization: Bearer <token>. The token is issued once, after checkout and a token claim, and goes in your client's secret field rather than a config file you might commit.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Starting an agent run with what earlier sessions learned
Memories are captured and reviewed in your Agentmemory workspace; the endpoint hands that recall to the agent through a fixed, read-only tool surface, so there is no store of your own to run.
02
Keeping a memory tool from being able to destroy anything
The surface has no deletion and no arbitrary query path, so a compromised prompt cannot clear the store.
03
Checking the capabilities before you commit
Read the published server card, which is public and needs no token.
BEFORE YOU INSTALL
What to know first
Requires
- A paid plan on agentmemory.space — the bearer token is issued only after checkout and a one-time token claim
- An MCP client that supports remote Streamable HTTP servers and sends an Authorization header
INSTALLATION
Connect your client
Paste it into your client, then supply credentials.
Server setup
Setup
Open https://agentmemory.space/pricing/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605.
Choose a plan and complete checkout.
Claim the one-time MCP bearer token from the hosted claim flow.
Paste only the token value into your MCP client secret field.
Configure the server URL as https://agentmemory.space/mcp in any MCP client that supports remote Streamable HTTP MCP servers and pass the bearer token in the Authorization header.
Hosted endpoint
ENDPOINT URL
https://agentmemory.space/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
