John CEO Agentic Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport (when MCP_TRANSPORT=http). Default 8080. | 8080 |
| DATABASE_URL | No | CockroachDB connection string (required if MEMORY_STORE=cockroach). Should use sslmode=verify-full. | |
| MEMORY_STORE | No | Storage backend: 'memory' (ephemeral), 'file' (JSON file), 'cockroach' (CockroachDB). Default 'file'. | file |
| MCP_TRANSPORT | No | Transport mode: 'stdio' for standard input/output, 'http' for HTTP server. Defaults to 'stdio'. | stdio |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP/Lambda authentication. Optional. | |
| CRDB_ADMIN_USER | No | CockroachDB admin user for ccloud bootstrap script. Optional. | |
| MCP_AUTH_USER_ID | No | When MCP_AUTH_TOKEN is set, this is the bound userId for ACL. Optional. | |
| USE_FAKE_BEDROCK | No | Set to '1' to use a deterministic local intelligence instead of Amazon Bedrock for offline demos/testing. | |
| CRDB_CLUSTER_NAME | No | CockroachDB cluster name used by the ccloud bootstrap script. Default 'agentic-memory'. | agentic-memory |
| CRDB_ADMIN_PASSWORD | No | CockroachDB admin password for ccloud bootstrap script. Optional. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_writeA | Persist something worth remembering about a user (a preference, fact, commitment, or event). Bedrock derives a short summary, tags, importance (salience), and kind. Call this whenever the user reveals durable information you should recall in future sessions. |
| memory_searchA | Semantic search over a user's memories via CockroachDB vector indexing, re-ranked by similarity, importance, recency, and reinforcement. Recalled memories are reinforced. |
| memory_recall_contextB | Returns the most critical memories for a query, greedily packed to fit a token budget, as a ready-to-inject context block. |
| memory_forgetA | Runs the maintenance pass: related memories are merged by Bedrock into one canonical memory, contradicted items are forgotten, and stale low-importance memories decay away. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: write persists, search retrieves, recall_context packs, forget maintains. There is no overlap in functionality, reducing risk of misselection.
All tools follow a consistent memory_verb pattern (memory_write, memory_search, memory_recall_context, memory_forget). The naming is predictable and uniform, simplifying agent tool selection.
Four tools is a tightly scoped set that covers the core memory operations without redundancy. Each tool earns its place, fitting the recommended 3-15 range.
The set covers the full memory lifecycle: create/write, retrieve/search, recall context for injection, and forget/maintenance for updates and deletions. No obvious gaps for the stated purpose of persistent user memory.