A specialized MCP server that tracks your Python development sessions, errors, fixes, and coding patterns using a persistent knowledge graph. This helps you build a searchable database of your development learnings, solutions, and insights.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-agentmemory","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Memory Graph MCP Server for Python Development A specialized MCP server that tracks your Python development sessions, errors, fixes, and coding patterns using a persistent knowledge graph. This helps you build a searchable database of your development learnings, solutions, and insights. ## Usage with Visual Studio Code ### Setup Add this to your `mcp.json` (you need to have uv installed): #### UVX (Recommended) ```json { "servers": { "agentmemory": { "command": "uvx", "args": [ "mcp-agentmemory", "--memory-file-path", "<directory where to story your memories, default ~/.mcp/>" ] } } } ``` The server creates two files in the specified directory: - `agentmemory.json`: Snapshot of the current knowledge graph - `agentmemory.log.jsonl`: Append-only event log for durability ## Core Concepts ### Entities Entities represent the building blocks of your development knowledge: - **Features**: Projects or tasks you're working on - **Sessions**: Individual development work periods - **Errors**: Persistent error tracking with fingerprinting - **Patterns**: Reusable solutions and coding patterns - **Modules/Classes/Functions**: Code structure elements Example: ```json { "name": "user-authentication", "entityType": "Feature", "tags": ["backend", "security"], "description": "JWT-based user authentication system" } ``` ### Relations Relations connect your development knowledge to show how different pieces relate: - `implements`: A session implements a feature - `encounters`: A feature encounters an error - `fixed_by`: An error is fixed by a pattern - `depends_on`: Dependencies between modules/features Example: ```json { "from": "session:abc123", "to": "user-authentication", "relationType": "implements" } ``` ### Observations Observations store your actual development insights and knowledge: - **note**: General observations and learnings - **snippet*…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.