About Statewave
Statewave is an MCP server that makes Statewave memory available to coding assistants, agent frameworks, and IDE extensions. Its five tools ingest episodes, search and retrieve subject context, browse timelines, and compile memories, with a vendor-neutral design and a minimal stdio transport.
Key features
- 01Ingest deduplicated episodes
- 02Search memories by subject
- 03Retrieve ranked subject context
- 04Browse filtered episode timelines
- 05Compile subject memories
Use cases
- 01Persist agent context across sessions
- 02Retrieve relevant subject context for a prompt
- 03Review a subject's episodes over time
MCP support
Exposes five Statewave memory tools to MCP-compatible clients through a minimal stdio JSON-RPC 2.0 server. It also provides a tool-listing mode and can be used within an existing MCP runtime.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README@statewavedev/mcp-server
Statewave MCP server — exposes Statewave memory to MCP-compatible clients (coding assistants, agent frameworks, IDE extensions).
Part of the Statewave Connectors ecosystem. Vendor-neutral by design — no IDE, model provider, or hosted dependency assumptions.
What's here
STATEWAVE_MCP_TOOLS— the canonical tool surface (5 tools, JSON Schema input)StatewaveClient— thin HTTP client for the Statewave v1 API (auth, tenant, typed errors)dispatchTool— input-validating dispatcher that maps a tool call to aStatewaveClientmethodstartMcpServer— minimal stdio JSON-RPC 2.0 transport, plus a--list-toolsmode
Tools
| Tool | Purpose |
|---|---|
statewave_ingest_episode | Ingest a single normalized episode (deduped on idempotency_key). |
statewave_search_memories | Search compiled memories by free-text query within a subject. |
statewave_get_context | Retrieve compact, ranked context for a subject — the default tool to use inside a prompt. |
statewave_get_timeline | Chronological episodes for a subject; filterable by kinds, since, until. |
statewave_compile_subject | Trigger compilation of a subject so newly ingested episodes become recallable. |
Usage
# As a CLI subcommand (via @statewavedev/connectors-cli)
statewave-connectors mcp start --list-tools # print the JSON Schema surface and exit
statewave-connectors mcp start # stdio JSON-RPC 2.0 server (requires STATEWAVE_URL)
# Or programmatically inside an existing MCP runtime
import { StatewaveClient, dispatchTool } from "@statewavedev/mcp-server";
const client = new StatewaveClient({ url: process.env.STATEWAVE_URL!, apiKey: process.env.STATEWAVE_API_KEY });
const { result } = await dispatchTool(client, "statewave_get_context", {
subject: "repo:owner/name",
query: "repo conventions and recent changes",
});
Status
v0.1.0 preview — minimal stdio transport included. See RELEASE_NOTES.md.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.