Syntarus MCP
MCP server exposing least-privilege search, provenance inspection, and write
tools for Syntarus memory. It reads SYNTARUS_API_KEY and, optionally,
SYNTARUS_USER_ID from the process environment. Do not put API keys in an MCP
configuration file.
Install and run
After installing the published package:
SYNTARUS_API_KEY=sk_mem_... \
SYNTARUS_USER_ID=customer_123 \
uvx syntarus-mcp
The server exposes search_memory, inspect_memory_provenance, and
remember. Destructive deletion is intentionally left to the authenticated
application SDK rather than an ambient MCP tool.
For a local checkout before the first PyPI release:
uvx --from ./sdk/mcp syntarus-mcp
1 maintainer
Release files for syntarus-mcp 0.2.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 | |
|---|---|---|---|
| syntarus_mcp-0.2.0.tar.gz | 2.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| syntarus_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.3 kB
Release files / syntarus_mcp-0.2.0.tar.gz
| Download URL | syntarus_mcp-0.2.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d2f58cca7a9e15121e07bcc82a72408f8858b3ab48c20d88986dab38bae8c60
|
|
BLAKE2b-256 checksum How to use checksums |
9db8198dde90672da65842c797ec78a6a37dcbb284b774dbcf30b3cfe7ed6978
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logRelease files / syntarus_mcp-0.2.0-py3-none-any.whl
| Download URL | syntarus_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39079a0af0ce349a326b188070d36aa4edebcfea300c7bc32044d4f343d1b90c
|
|
BLAKE2b-256 checksum How to use checksums |
d619c6471e51e153429d1a02622fedccc4bd222ad00712f6d354e2326b278ba2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency log
