cortex-memory-mcp
cortex-memory-mcp is the thin stdio bridge for Cortex's generic agent-memory
contract. It calls the hosted Cortex HTTP API; it does not contain a local
memory database or memory dashboard.
Run
CORTEX_API_KEY=ck_live_... uvx cortex-memory-mcp
CORTEX_BASE_URL defaults to Cortex production. A scoped connection key derives
its identity, capabilities, accessible spaces, and default space from
/v1/whoami; keys are never MCP tool arguments.
Writes are disabled by default. Set CORTEX_MCP_ENABLE_WRITES=true to register
remember, correct, move, and confirmed forget tools. Other settings:
CORTEX_MCP_PROFILE=generic|integration(defaultgeneric)CORTEX_MCP_TIMEOUT_SECONDS=25CORTEX_MCP_WRITE_TIMEOUT_SECONDS=25CORTEX_MCP_DEFAULT_USER_IDonly for legacy dedicated keys without exact user scopeCORTEX_MCP_ALLOW_USER_OVERRIDE=trueonly for approved private integration use
Hosted streamable HTTP exposes the same generic contract at the Cortex API base
URL plus /mcp, using the same scoped key as an x-api-key header.
Source version 0.2.0 uses the stable Python MCP SDK 2.x. It negotiates MCP
2026-07-28 through server/discover by default and remains compatible with
legacy initialize-based clients.
1 maintainer
Release files for cortex-memory-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cortex_memory_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / cortex_memory_mcp-0.2.0-py3-none-any.whl
| Download URL | cortex_memory_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
464cd6c74e6e3a10c17ad8b85d95c05ad18738ea57e9ab60414a501e389dbe5f
|
|
BLAKE2b-256 checksum How to use checksums |
a7a8b62e7d3f6f50a43888f22bc4d442bbb676582d28adc55c02364b498c4130
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jul 29, 2026.
Transparency log
