Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STATEWAVE_URLYesBase URL of the Statewave API serverhttp://localhost:8100
STATEWAVE_API_KEYNoOptional API key for authenticating with Statewave

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
statewave_ingest_episodeA

Write a single normalized event ('episode') into Statewave's raw memory log for a subject. This is a write: the episode is stored immediately but is NOT yet retrievable as durable memory — call statewave_compile_subject afterward to distil episodes into the compiled memories that statewave_get_context and statewave_search_memories read. Idempotent: re-ingesting an idempotency_key already seen for the subject does not create a duplicate. Returns the stored episode id, its idempotency_key, and a duplicate boolean indicating whether an existing episode was matched. Use it to capture a durable fact, decision, message, or system event you want remembered.

statewave_search_memoriesA

Search a subject's compiled, durable memories by free-text query and return the most relevant ones, ranked by relevance. Read-only. This searches distilled memories, NOT raw episodes — newly ingested episodes only appear here after statewave_compile_subject has run. Returns an array of memory records (id, subject, kind, content) ordered most-relevant first; an empty array means nothing matched. Use it to look up specific remembered facts; prefer statewave_get_context when you instead want prompt-ready context assembled to a token budget.

statewave_get_contextA

Assemble a compact, ranked context bundle for a subject, tailored to the task described in query. Read-only. Designed to be injected into an agent/LLM prompt in place of stuffing raw chat history or whole files: it returns only the most relevant distilled facts and procedures, fit to a token budget. Returns a context bundle with assembled_context (ready-to-prompt text), structured facts and procedures arrays, and a token estimate. Prefer this over statewave_search_memories when you want prompt-ready context rather than a raw ranked list of memories.

statewave_get_timelineA

Retrieve a subject's raw episodes in chronological order (oldest to newest). Read-only. Unlike statewave_search_memories (ranked, compiled memories), this returns the underlying event log unmodified — use it for audit trails, change-logs, debugging what was ingested, or replaying history. Optionally bound the window with since/until and filter to specific event kinds. Returns an array of episode records (id, kind, text, occurred_at, source), capped by limit; an empty array means no episodes matched the filters.

statewave_compile_subjectA

Compile a subject's accumulated raw episodes into durable, retrievable memories. This is the step that makes ingested episodes searchable: statewave_ingest_episode stores raw episodes, and this distils them into the compiled memory that statewave_get_context and statewave_search_memories read. Triggers a compile job on the server and returns its summary (subject and status). By default it is a no-op when there are no new episodes since the last compile; set force to recompile anyway. Call it right after ingesting episodes you want to become retrievable.

statewave_list_subjectsA

List the memory subjects this Statewave instance knows about, with per-subject episode and memory counts. Read-only. Use it to discover which subject id to pass to the other tools (e.g. repo:owner.name) — especially in chat clients that have no repository context. Returns a paginated array of subjects (subject id, episode_count, memory_count) plus a total count; page through larger instances with limit/offset.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/smaramwbc/statewave-connectors'

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