MEMGRAPH-MCP
Provides SQLite-backed memory storage with vector indexing for retrieval, enabling persistent project memory and artifact storage through MCP resources and tools.
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., "@MEMGRAPH-MCP create a run to refactor the authentication module"
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.
Agent System
A durable multi-agent orchestrator with:
explicit run graphs and checkpoint/resume
orchestrator-controlled parallel delegation
bounded research swarm execution
coding, review, repair, CI, and approval loops
project memory in backing stores exposed through MCP resources and tools
a real SQLite vector index for memory retrieval
a pluggable external research backend with Tavily support
Scope
This implementation targets the MCP 2025-11-25 spec baseline with the official Python MCP SDK and a FastMCP server for the memory surface. For local development it runs over stdio. For remote deployment, see docs/remote_auth.md.
Related MCP server: ellmos-homebase-mcp
Layout
app/runtime: run state, scheduler, orchestrator loop, checkpointingapp/planner: planning and graph revision helpersapp/agents: node executors for research, code, review, repair, CI, synthesis, approvalapp/memory: SQLite-backed memory, retrieval, and artifact indexapp/mcp_server:FastMCPresources, tools, prompts, and server entrypointtests: acceptance and unit coverage
Local usage
uv sync --group dev
uv run pytest
uv run agent-system-mcpRetrieval and research backends
Memory entries are indexed into a local SQLite vector table using
sqlite-vec.The default embedding provider is
auto: it prefers a realsentence-transformersmodel and falls back to the deterministic hash provider only if the model cannot load.Research uses an in-memory corpus backend when a node provides
inputs.corpus.If
TAVILY_API_KEYis set, corpus-free research nodes can use the Tavily backend for external web research.If no corpus and no Tavily key are available, research returns bounded empty findings instead of inventing sources.
Embedding configuration
AGENT_SYSTEM_EMBEDDING_PROVIDER=auto|sentence-transformers|hashAGENT_SYSTEM_EMBEDDING_MODEL=sentence-transformers/all-MiniLM-L6-v2AGENT_SYSTEM_EMBEDDING_CACHE_DIR=/path/to/cacheAGENT_SYSTEM_EMBEDDING_LOCAL_ONLY=true|false
Example:
AGENT_SYSTEM_EMBEDDING_PROVIDER=sentence-transformers uv run agent-system create-run "improve scheduler"Local transport
Development uses the MCP stdio transport.
Remote deployment
Remote deployment is intentionally documentation-only in v1. The server documents an OAuth 2.1-compatible consent path and keeps local stdio as the default development mode.
Full documentation
state.md: current project state, changes since creation, and roadmap
docs/getting_started.md: fastest path to a working local run and MCP server
docs/operator_guide.md: full system overview, operations, and best practices
docs/developer_custom_graphs.md: Python API usage, custom graph design, and node payload reference
docs/codex_mcp_usage.md: how Codex should use this MCP for large-app planning, memory, and checkpointed execution
examples/plan_large_app.py: example of generating a large-app blueprint and run programmatically
Available Tools
10 toolscheckpoint_runBIdempotent
Apply a small state patch and create an explicit checkpoint.
Inputs: run_id (required), state_patch_json (required). Returns: object
create_runA
Create a new orchestrator run from a high-level goal and optional JSON spec.
Inputs: goal (required), spec_json. Returns: object
get_file_contextBRead-onlyIdempotent
Read file context from the orchestrator workspace.
Inputs: paths (required), include_neighbors. Returns: object
plan_goalBRead-onlyIdempotent
Generate a large-app execution blueprint from a high-level goal and optional JSON spec.
Inputs: goal (required), spec_json. Returns: object
record_decisionCIdempotent
Record a high-value architectural or implementation decision.
Inputs: title (required), run_id (required), node_id (required), rationale (required), +2 more. Returns: object
record_failure_modeAIdempotent
Record a reusable failure pattern or bug signature.
Inputs: run_id (required), node_id (required), summary (required), signature (required), +1 more. Returns: object
resume_runAIdempotent
Resume an orchestrator run until completion, pause, or failure.
Inputs: run_id (required). Returns: object
search_project_memoryARead-onlyIdempotent
Search project memory by query string and optional type filters.
Inputs: query (required), kind, limit, status. Returns: result
write_project_memoryCIdempotent
Write a durable memory entry with provenance to the backing store.
Inputs: key (required), kind (required), run_id (required), node_id (required), +5 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools target distinct actions or resources, but plan_goal and create_run both take a high-level goal and optional JSON spec, making their boundaries unclear. Similarly, search_project_memory and list_related_artifacts both retrieve stored information in overlapping ways. Descriptions help clarify intent, but some pairs could still lead to misselection.
All tools follow a consistent verb_noun snake_case pattern, such as resume_run, write_project_memory, record_decision, and create_run. The naming is uniform and predictable across the entire toolset.
Ten tools is a well-scoped count for an orchestrator and memory management server. Each tool covers a meaningful operation without the set feeling bloated or overly sparse.
The core lifecycle is covered: creating and resuming runs, checkpointing, planning, memory read/write, and recording decisions/failures. Minor gaps exist, such as no explicit run status/query tool or delete operation for memory entries, but agents can generally work within the provided surface.
Maintenance
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
The AI orchestration agent for modern software teams.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceShared memory and orchestration for coding agents, enabling persistent knowledge, multi-agent coordination, and a canonical workflow across MCP-compatible AI clients.83-

ellmos-homebase-mcpofficial
AlicenseCqualityBmaintenanceEnables local-first LLM orchestration with persistent memory, knowledge management, routing, swarm patterns, API probing, tests, automation planning, and plugin discovery via a stdio MCP server, using SQLite for offline storage.51173 npm2MIT- AlicenseNot gradedqualityDmaintenanceA production-grade multi-agent workflow orchestrator built on the Model Context Protocol, featuring planner/executor/critic agents, durable run state, and replayable traces.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous multi-agent orchestration using directed acyclic graph workflows to interact with external developer infrastructure such as Git, Postgres, and Docker through safety-gated MCP servers.Apache 2.0