statecore-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Store a durable fact about this project or user. Use for preferences, decisions, constraints, and anything worth knowing next session. Deterministic and audit-tracked. Notes (the default path) are capped at 500 characters; pass consolidate=true for longer conversational context, accepted up to 2000 characters and distilled in the background. |
| recallA | Retrieve project memory relevant to a query, packed into a character budget. Returns the distilled digest, believed facts, recent events, and a budget report of what was left out. Call at the start of a session or before relying on past context. |
| factsA | List everything currently believed about this project, grouped, with fact ids. Use to review or audit the memory. |
| whyA | Explain why a fact is believed: its source evidence and the full version chain, including superseded and retired versions. Pass a factId from facts or recall. |
| forgetA | Suppress a fact by factKey. The record is retired, not deleted — the audit chain is preserved. |
| handoffA | Record where this session stopped — a summary, open questions, and next steps — before ending or compacting. The next session (in this client or any other MCP client) receives it at the top of recall; each handoff supersedes the previous one on an auditable chain (why on the returned handoffId walks it). Pass clear=true to retire the active handoff instead. |
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 6 tools
Each tool has a clear, non-overlapping role: remember writes durable facts, handoff captures session-ending state, recall retrieves relevant memory, facts enumerates beliefs, why traces provenance, and forget retires facts. No two tools could be easily confused even without deep inspection.
Most tools use a single imperative verb (remember, handoff, recall, forget), which is consistent and predictable. However, 'facts' is a plural noun and 'why' is an interrogative, deviating slightly from the verb pattern; they remain intuitive in context.
Six tools is a well-scoped set for a memory/state system. Each tool covers a distinct operation (write, session handoff, query, audit list, provenance, delete) without redundancy or bloat.
The surface covers the full memory lifecycle: storing facts, retrieving them, listing current beliefs, explaining provenance, handling session handoffs, and suppressing obsolete facts. There are no obvious missing operations for the stated purpose.