Developer · Local MCP server
Heartwood Memory - governed memory for AI agents
Heartwood Memory - governed AI agent memory; signed provenance. BUSL-1.1; not OSI open source.
Visit Heartwood Memory - governed memory for AI agents's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jermayne36/heartwood-memory- Version
- 0.2.9
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- jermayne36 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jermayne36) · how
- Website
- heartwoodmemory.com/
- Repository
- github.com/jermayne36/heartwood-memory
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | heartwood-memory | 0.2.9 | stdio |
How to connect Heartwood Memory - governed memory for AI agents
Heartwood Memory - governed memory for AI agents runs locally from a Python package published to PyPI: heartwood-memory version 0.2.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx heartwood-memory. It reads these environment variables: HEARTWOOD_DB_PATH (required), HEARTWOOD_TENANT and HEARTWOOD_MCP_ALLOWED_TOOLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"heartwood-memory": {
"command": "uvx",
"args": [
"heartwood-memory"
],
"env": {
"HEARTWOOD_DB_PATH": "<value>",
"HEARTWOOD_TENANT": "<value>",
"HEARTWOOD_MCP_ALLOWED_TOOLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| HealthchecksInspect, create and adjust Healthchecks cron and uptime checks, and read why one failed. | Local · stdio |
| HealthchecksioManage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io. | Remote · HTTPLive check: ✓ handshake |
| Heartbeat - dead-man switch for cron jobs & AI agentsDead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed. | Remote · HTTPLive check: ✓ handshake |
| Heartbeat MonitorDead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job. | Remote · HTTPLive check: ✗ no handshake |
| HeddleContent-addressed contracts and a verification cache that cut agent context by skipping proven code. | Local · stdio |
| HefestoAIPre-commit code quality guardian. Detects semantic drift in AI-generated code. | Remote · HTTPLive check: ✓ handshake |
| HEIDESDeterministic code analysis harness giving AI agents senses, memory and judgment for code. | Local · stdio |
| HeirmosPersistent memory shared across Claude, ChatGPT, Grok and other MCP clients. | Remote · HTTPLive check: sign-in required |