Developer · Remote MCP server
WorkingMemory
Persistent personal memory for AI assistants - save, search, and recall across every MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.workingmemory/memory- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-17
- Updated
- 2026-07-17
- Publisher
- ai.workingmemory
- Namespace
- Namespace verified by the MCP Registry via the domain workingmemory.ai · how
- Website
- workingmemory.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.workingmemory.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- workingmemory 1.0.0 · protocol 2025-11-25
- Tools discovered
- 4:
save_memory,search_memory,manage_memory,capture_memory - Checked on
- 2026-10-05
How to connect WorkingMemory
WorkingMemory is a remote MCP server: there is nothing to install. Its endpoint is https://app.workingmemory.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| Workflow GeneratorArchitecture diagram with concurrency capacity and bottleneck estimates from any codebase. | Local · stdio |
| Workflow MCPSession-bound Docker workflow server through Codex. State is discarded with the container. | Local · stdio |
| Workflows MCP ServerStore, query, and create YAML workflow playbooks for LLM agents. | Local · stdio, HTTP |
| WorkflowyCreate, update, complete nodes, search & replace with regex and dry run, usage reports, transforms. | Local · stdio |
| WORKMINEX402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers. | Remote · HTTPLive check: ✓ handshake |
| WORKS Public VerifierIndependent static verification for exact immutable public GitHub commits. | Remote · HTTPLive check: ✓ handshake |
| Workspace ToolsSandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data. | Remote · HTTPLive check: ✗ no handshake |
| Workspace ToolsResearch honeypot. Logs connections and tool arguments; injects instructions. Read README first. | Remote · HTTPLive check: ✗ no handshake |