Mcp Server
Give your coding agent durable visual memory and a knowledge graph stored in a local JSON file across long refactor sessions.
Overview
Visual Memory Context MCP is a MCP server for the Build phase that provides visual memory, context storage, and knowledge graph tools for agents.
What is this MCP server?
- Visual memory and context storage exposed as MCP tools
- Knowledge graph capabilities backed by configurable memory.json path
- npm package visual-memory-context-server v1.0.1 with stdio transport
- ALLOWED_DIRECTORIES scopes filesystem access for safer local graphs
- Pairs with long-horizon Claude Code threads that need entity relationships
- Server version 1.0.1
- npm identifier visual-memory-context-server
What problem does it solve?
Long agent sessions forget decisions, diagrams, and relationships unless you manually re-paste context every time.
Who is it for?
Indie developers building agent-heavy workflows who want local, file-backed knowledge graphs without a cloud memory vendor.
Skip if: Teams needing enterprise ACLs, hosted vector search at scale, or zero local file configuration.
What do I get? / Deliverables
The agent can read and write structured memory and graph nodes in your chosen memory.json within allowed directories.
- File-backed visual memory and graph storage for agents
- Scoped directory access for safer local context ops
- Repeatable entity and relationship recall across sessions
Recommended MCP Servers
Journey fit
Agent-tooling is the primary shelf because persistent memory and graph context directly extend what MCP hosts can recall while building features. This subphase covers memory servers, context stores, and agent-side state that reduce repeated explanations in multi-day indie projects.
How it compares
Local knowledge-graph memory MCP, not a code-indexing skill or full RAG database product.
Common Questions / FAQ
Who is visual memory context MCP for?
Builders using Claude Code or similar agents who need persistent structured memory and graph links across sessions on their own machine.
When should I use visual memory context MCP?
Use it during build and operate when you want the agent to retain entities, relationships, and visual context for ongoing product work.
How do I add visual memory context MCP to my agent?
Add the npm stdio server visual-memory-context-server to MCP settings, set MEMORY_FILE_PATH and ALLOWED_DIRECTORIES, then restart your host.