Agentage Memory MCP Server for Claude
Remote Agentage Memory MCP server giving Claude one shared, portable memory across every AI you use - search, read, write, edit, list, and delete plain Markdown notes you own, over Streamable HTTP with OAuth 2.1.
Open the source and read safety notes before installing.
Safety notes
- The memory__write, memory__edit, and memory__delete tools create, modify, and remove your stored notes; review actions before granting broad access.
Privacy notes
- Notes you read or write are stored server-side in your Agentage Memory and mirrored locally as Markdown you can export anytime; note contents pass through model context.
Prerequisites
- agentage account (sign in at memory.agentage.io)
- OAuth 2.1 authentication (PKCE + Dynamic Client Registration, handled in the connect flow)
- Network access to memory.agentage.io (HTTPS required)
- Claude Desktop 0.7.0+ or Claude Code with MCP (HTTP transport) support
Schema details
- Install type
- cli
- Troubleshooting
- No
- Estimated setup
- 1 minute
- Difficulty
- beginner
- Website
- https://memory.agentage.io
Full copyable content
{
"agentage-memory": {
"url": "https://memory.agentage.io/mcp",
"transport": "http"
}
}About this resource
Content
Connect Claude to Agentage Memory, the shared memory layer for every AI. One Markdown memory that Claude, Cursor, and ChatGPT can all read and write through MCP, mirrored locally as plain .md files you own and can export anytime. The remote server speaks Streamable HTTP with OAuth 2.1, PKCE, and Dynamic Client Registration, so connecting is a one-time browser sign-in.
Features
- One shared memory across Claude, Cursor, ChatGPT, and any MCP client
- Plain-Markdown notes you own, mirrored locally and exportable anytime
- Full-text search across your memory (memory__search)
- Read, write, edit, list, and delete notes (memory__read / write / edit / list / delete)
- Remote hosted server - no local install or runtime to maintain
- OAuth 2.1 + PKCE + Dynamic Client Registration for secure, per-client access
Use Cases
- Carry context, decisions, and preferences between different AI tools
- Build a durable personal or team knowledge base your AIs read and update
- Search past notes before starting new work
- Keep an owned, exportable Markdown record instead of vendor-locked memory
Installation
Claude Code
- Run: claude mcp add --transport http agentage-memory https://memory.agentage.io/mcp
- Verify installation: claude mcp list
- Authenticate with your agentage account (OAuth flow opens in browser)
Claude Desktop
- Open your Claude Desktop configuration file
- Add the Agentage Memory server configuration (HTTP transport, URL https://memory.agentage.io/mcp)
- Restart Claude Desktop
- Authenticate with your agentage account (OAuth flow)
Configuration
{
"agentage-memory": {
"url": "https://memory.agentage.io/mcp",
"transport": "http"
}
}
Security
- OAuth 2.1 + PKCE required for access; unauthenticated requests return 401
- Protected Resource Metadata (PRM) is served for discovery
- Dynamic Client Registration issues per-client credentials
- Tokens are bearer credentials - store securely, never commit to a repo
Source citations
Add this badge to your README
Show that Agentage Memory MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/agentage-memory-mcp-server)How it compares
Agentage Memory MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Agentage Memory MCP Server for Claude Remote Agentage Memory MCP server giving Claude one shared, portable memory across every AI you use - search, read, write, edit, list, and delete plain Markdown notes you own, over Streamable HTTP with OAuth 2.1. Open dossier | Basic Memory MCP Server Local-first Basic Memory MCP server for giving Claude a persistent Markdown knowledge base with note editing, semantic search, recent activity, knowledge graph context, projects, schema tools, and optional cloud sync. Open dossier | AutoRFP.ai MCP Server for Claude Official AutoRFP.ai remote MCP server for read-only access to RFP projects, requirements, approved content library search, and organisation tags from Claude and other MCP clients via OAuth. Open dossier | Auxen MCP Server for Claude Official Auxen.ai remote MCP server for listing GPU models and instances, checking account balance, and provisioning or destroying inference instances from Claude via OAuth 2.1 or API keys. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | agentage | Basic Machines | AutoRFP.ai | Auxen AI |
| Added | 2026-06-18 | 2026-06-06 | 2026-06-14 | 2026-06-14 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The memory__write, memory__edit, and memory__delete tools create, modify, and remove your stored notes; review actions before granting broad access. | ✓Basic Memory MCP can create, edit, move, and delete notes in the configured project. The server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools. Edit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth. Imports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base. Auto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv. The optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication. | ✓The connection is read-only; it cannot create, edit, or delete AutoRFP.ai records. Each user inherits their own AutoRFP.ai permissions, so MCP results reflect that user's normal app access. OAuth tokens grant persistent read access until revoked in AutoRFP.ai or the MCP client. Do not share OAuth-approved connector sessions across users or paste access tokens into public issues. | ✓provision_model creates billable GPU instances; confirm model, region, and cost before approving tool calls. destroy_instance permanently removes running instances and cannot be undone through MCP. API keys prefixed auxen_live_* operate on production resources; use auxen_test_* keys in development. OAuth tokens grant persistent account access until revoked in Auxen or the MCP client. |
| Privacy notes | ✓Notes you read or write are stored server-side in your Agentage Memory and mirrored locally as Markdown you can export anytime; note contents pass through model context. | ✓Local notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research. Cloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine. The README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking. Logs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes. Keep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files. | ✓MCP tool results can expose RFP project names, requirement text, approved answer content, and organisation tag vocabulary. Search queries sent to the content library are processed by AutoRFP.ai under its own data-handling terms. Public support notes should describe connector scope, not full requirement or library excerpts. | ✓MCP tool results can expose account balance, instance IDs, model names, and deployment metadata. Provisioning requests are processed by Auxen.ai under its own data-handling and billing terms. Do not paste live API keys or OAuth tokens into public issues or shared chat logs. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.