LogicMem MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGICMEM_API_KEY | Yes | API key for LogicMem, obtained from logicmem.io settings. | |
| LOGICMEM_BASE_URL | No | Base URL of the LogicMem MCP server. | https://mcp.logicmem.io |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logicmem_memory_logA | Store a new memory. The agent's memory is permanent and searchable across sessions. Be specific — include who, what, when, why. |
| logicmem_memory_recallC | Search memory for relevant entries. |
| logicmem_memory_sessionB | Full memory session briefing — recall + sentiment + constraints + intelligence + gaps. |
| logicmem_memory_statsA | Get memory system stats — total entries, categories, storage. |
| logicmem_memory_healthA | Check if the LogicMem memory server is healthy. |
| logicmem_memory_outcomeB | Record whether a stored memory was useful. Feeds the DPO training pipeline. |
| logicmem_memory_reflectB | Self-critique: evaluate a draft answer against retrieved memories. |
| logicmem_a2a_registerC | Register this agent in the A2A registry. |
| logicmem_a2a_heartbeatD | Send a heartbeat to the A2A registry. |
| logicmem_a2a_list_agentsA | List all registered agents for a client_id. |
| logicmem_a2a_write_sharedC | Write a memory to the shared A2A pool. |
| logicmem_a2a_syncB | Check for new shared memories from other agents since last sync. |
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 12 tools
All 12 tools have clearly distinct purposes, split into two coherent groups: memory operations (log, recall, stats, session, health, outcome, reflect) and A2A operations (register, heartbeat, list_agents, write_shared, sync). No overlapping functionality.
Tool names follow a consistent pattern: `logicmem_<group>_<action>`. Memory tools use `memory_` and A2A tools use `a2a_`. Verbs are descriptive (log, recall, stats, etc.), making the pattern predictable.
With 12 tools covering memory management and agent-to-agent communication, the count is well-scoped. Each tool serves a distinct function without redundancy, fitting the server's purpose.
The set covers core memory operations (store, recall, stats, session, outcome, reflect, health) and A2A operations (register, heartbeat, list, write shared, sync). Minor gaps exist, such as no explicit delete/update for memories, but the design suggests permanence.