Workflow MCP Server
# Memory MCP
This repository implements a small MCP server that exposes a `mem_save` tool for recording structured memory entries to a per-project JSON file (`.memory/memory.json`). The server is intentionally simple: it stores entries provided by the AI and enforces a token-budgeted FIFO eviction policy.
<a href="https://glama.ai/mcp/servers/@Artin0123/workflow-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@Artin0123/workflow-mcp/badge" alt="Workflow Server MCP server" />
</a>
## Installation
```powershell
npm install
npm run build
```
## Configuration
Add this server to your MCP client configuration. Example:
```json
{
"mcpServers": {
"memory-mcp": {
"command": "node",
"args": ["/path/to/mcp/dist/server.js"]
}
}
}
```
## Features
This server does not summarize or decide what to store by itself. User should decide when to call `mem_save`.
- Tool: `mem_save` — record memories for a project (JSON storage)
- Token estimation and FIFO eviction to keep estimated tokens ≤ 1000
- Auto-creates `.memory/memory.json` if missing
## mem_save behavior
Inputs:
- `projectPath` (string): absolute project path provided by the AI
- `entries` (array): list of memory entry objects. Each entry has:
- `what` (string)
- `why` (string)
- `outcome` (string)
- `task_context`, `constraints`, `dependencies` (optional strings)
Storage:
- Memory is stored at `<projectPath>/.memory/memory.json`:
{
"entries": [ ... ],
"meta": {
"total_entries": number,
"estimated_tokens": number,
"last_updated": "YYYY-MM-DD"
}
}
Token estimation (approximate):
- Chinese chars ≈ 1.3 tokens each
- English letters ≈ 0.3 tokens each
- Other symbols ≈ 0.6 tokens each
Eviction policy:
- After appending new entries, the server computes an estimated total token usage.
- If the total exceeds 1000 tokens, it removes the oldest entries (FIFO) one-by-one until the total is ≤ 1000.
Return value:
- On success the tool returns a JSON text message with `success: true` and a short summary.
## License
MITTDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as recording workflow memories with FIFO eviction, and no other tools exist to cause confusion.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'mem_save' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is too few for a server named 'Workflow MCP Server', which implies a broader scope for managing workflows. A single memory-saving tool does not provide the expected functionality for creating, managing, or executing workflows, making it an extreme mismatch for the apparent domain.
The tool surface is severely incomplete for a workflow server. It only offers memory saving with no tools for creating workflows, listing workflows, updating workflows, deleting workflows, or executing workflows. This leaves major gaps that will cause agent failures in handling workflow-related tasks.