Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
recallA

Surface the most relevant past lessons, decisions, and rules for a task, ranked by semantic similarity. Returns {count, memories:[{id, scope, score, text}]}, where score is rerank confidence (higher = more relevant). Use at the start of a task or whenever unsure how the user wants something done, instead of guessing. Read-only — to save a new memory use note.

noteA

Record a decision, finding, or correction into memory mid-task so it can be recalled in future sessions. Returns {ok, noted}. The text is captured as a candidate and deduped against existing knowledge by the background pipeline. Use when the user states a durable preference or you learn something worth keeping; not for transient chatter. To retrieve memories use recall.

statusA

Report the health of the verifiable-memory system. Returns {agentDid, logEntries, logIntegrity, merkleRoot} — the agent's did:key identity, transparency-log size, its integrity ('ok' or a reason), and the current Merkle root. Use for a fast health/identity check. For a full per-memory credential audit use verify; for the signed log commitment use tree_head.

verifyA

Cryptographically verify every stored memory's W3C Verifiable Credential and the integrity of the hash-chained transparency log. Returns a summary of memories checked, how many are valid, and any failure reasons. Use to detect tampered or poisoned memories before trusting them. This is the deep audit; status is the lightweight check.

receiptA

Produce an RFC 6962-style cryptographic proof that a specific memory is committed in the signed transparency log. Returns the inclusion receipt (leaf index, audit path, tree size, signed root). Use to prove to a third party that a memory existed and was logged. Requires the memory's id — get ids from recall.

tree_headA

Return the current signed Merkle tree head — the log's tamper-evident commitment to every memory so far. Returns {rootHash, treeSize, signature, ...}. Use as the anchor a verifier checks inclusion receipts against, or to detect log forks. Pair with receipt.

progressA

Summarize momentum, stalls, and dependencies across the user's projects as a narrative. Returns {narrative}. Use to orient at session start or when the user asks 'where are we'. Read-only synthesis of project-state memory.

review_pendingA

List always-load (Layer-A) rules awaiting human approval before they enter the always-on context. Returns {pending}. Use to see what the system wants to promote. Approval itself is a human action via the cogmem review CLI, not this tool.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
User modelcogmem's evolving model of the user

Latest Blog Posts

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/writerslogic/cogmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server