Workflow MCP Server
This server provides workflow management tools with specialized memory storage, task evaluation, environment verification, and reasoning capabilities.
Memory Storage (
mem_save): Record structured project memories withwhat,why,outcome, and optional context fields to<projectPath>/.memory/memory.json. Automatically handles FIFO eviction based on token count to maintain a ~1000 token budget.Task Evaluation (
evaluate_task): Assess task complexity to determine if tasks are multi-step, have unclear requirements, can be broken into subtasks, or have high bug risk.Environment Verification (
env_verify): Mandatory safety check before package installation to block unsafe operations and ensure proper environment validation.Thought Processing (
think): Log complex reasoning processes or cache internal thoughts for reference without making external changes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Workflow MCP Server save that we installed pandas for data analysis and it worked with our current Python version"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Installation
npm install
npm run buildRelated MCP server: Sequential Thinking MVP Server
Configuration
Add this server to your MCP client configuration. Example:
{
"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.jsonif missing
mem_save behavior
Inputs:
projectPath(string): absolute project path provided by the AIentries(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: trueand a short summary.
License
MIT
Available Tools
1 toolmem_saveC
Record workflow memories with FIFO eviction (keep ≤ 1000 tokens)
Inputs: projectPath (required), entries (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
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.
Maintenance
Related MCP Connectors
Verify npm packages before your AI agent installs them: hallucinations, advisories, API drift.
Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools.
AI-powered spec-to-task decomposition and execution orchestration for coding agents.
Policy-aware AI execution, verification, cost, and trajectory evidence for agents.
Related MCP Servers
- AlicenseBqualityNot gradedmaintenanceProvides structured sequential thinking capabilities for AI assistants to break down complex problems into manageable steps, revise thoughts, and explore alternative reasoning paths.29-
- AlicenseBqualityNot gradedmaintenanceEnables AI assistants to perform structured, step-by-step reasoning by breaking down complex problems into numbered thoughts, with support for revising previous steps and exploring alternative reasoning paths.5-
- AlicenseNot gradedqualityDmaintenanceProvides a 'reflect' tool that creates cognitive checkpoints for AI assistants, forcing structured step-by-step reasoning through complex problems to improve accuracy and maintain context during task execution.14 npm6MIT
- FlicenseBqualityBmaintenanceEnables AI coding assistants to run a machine-verified DESIGN→PLAN→EXECUTE→VERIFY→COMPLETE workflow with human approval gates, state integrity checks, and DAG task scheduling.7-