MemoryPatch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_record_eventA | Record immutable evidence. Reusing an external_id is idempotent only for identical event data. |
| memory_searchB | Search the FTS5 current-memory index. Active memories are returned unless include_removed is true. |
| memory_readB | Read one memory's exact current state, optionally including every immutable version. |
| memory_applyA | Apply semantic operations atomically and return server-generated diffs and evidence links. ADD uses subject/content. UPDATE refines without historical obsolescence; SUPERSEDE marks the prior state outdated; both use memory_id/expected_version/new_content. REMOVE uses memory_id/expected_version and is a soft deletion. Default policy requires evidence IDs. Raw SQL, raw diff text, and administrative rollback are never accepted here. |
| memory_historyB | Return every immutable version of a memory in ascending version order. |
| memory_patch_readA | Read a committed patch, semantic operations, evidence links, generated diff, and rollback relationship. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AppleLamps/MemoryPatch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server