warm-claude-tool (Python)
Backs Anthropic's client-side memory tool (memory_20250818) with WARM: Claude's /memories directory is stored in a warm-mcp server and every file is searchable by meaning.
Install
pip install warm-claude-tool # plus a warm-mcp binary: npx -y writerslogic-warm-mcp, or uvx warm-mcp
Quickstart
import anthropic
from warm_memory_tool import WarmMemoryToolSync
client = anthropic.Anthropic()
with WarmMemoryToolSync.connect(command="warm-mcp") as memory: # or url="http://127.0.0.1:8765/mcp"
runner = client.beta.messages.tool_runner(
model="claude-sonnet-5-5",
max_tokens=1024,
messages=[{"role": "user", "content": "Remember that Acme Corp prefers email follow-ups."}],
tools=[memory, memory.recall_tool()],
)
print(runner.until_done().content)
Needs ANTHROPIC_API_KEY, so it is not run by the docs check; the tool itself is tested offline against a real warm-mcp in tests/.
Options
WarmMemoryTool (async, BetaAsyncAbstractMemoryTool) and WarmMemoryToolSync (BetaAbstractMemoryTool) take the same arguments to connect(...).
| Name | Type | Default | Meaning |
|---|---|---|---|
command, args, env |
str, list, dict | none | Start warm-mcp over stdio |
url, token |
str, str | none, WARM_MCP_TOKEN |
Connect to a shared warm-mcp --transport http |
namespace |
str | none | One store per user (server needs --namespace-arg) |
max_view_chars |
int | 16000 | Longest view result before paging with view_range |
edit_retries |
int | 25 | Compare-and-set retries when another writer edits the same file |
request_timeout |
float | 60.0 | Seconds per MCP request |
Compatibility
Python 3.10+, anthropic >= 1.16, mcp 2.3 to <3, a warm-mcp server. Tested on Python 3.12 (31 tests against a real warm-mcp).
Reference
Commands, safety rules and semantic recall: Anthropic memory tool on WARM. TypeScript sibling: ../typescript.
Metadata
Release files for warm-claude-tool 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| warm_claude_tool-0.1.0.tar.gz | 15.1 kB | With provenance | Details for warm_claude_tool-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| warm_claude_tool-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for warm_claude_tool-0.1.0-py3-none-any.whl |
Total release size: 33.0 kB
Release files / warm_claude_tool-0.1.0.tar.gz
| Download URL | warm_claude_tool-0.1.0.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a34a3715ebf6411260f2b1911c0e13d670fe836b6d218bae22f1fc38818b1955
|
|
BLAKE2b-256 checksum How to use checksums |
c99d2ca5389753edeaf1f4f37496d94dcb5024770fb5e84dc03d02b6f0964d01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logRelease files / warm_claude_tool-0.1.0-py3-none-any.whl
| Download URL | warm_claude_tool-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca5295ebecf91638f68e37395a29ec14014201803d546ed979d8f18de83d30c0
|
|
BLAKE2b-256 checksum How to use checksums |
b6fd0d2cbcf9df38c6d2ca6409781e73dfec811718cfd82cd36ef327649a8e43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for warm-claude-tool 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for warm_claude_tool-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.