`dbx-tools-graphiti`

Run Graphiti REST, MCP, model routing, and PostgreSQL-backed graph memory from one Python runtime. The build synchronizes the upstream REST and MCP source plus the pinned PostGraph driver from Graphiti PR 1777 into the generated package tree, so the published wheel has no direct Git dependencies.

Both upstream surfaces come from the same Graphiti commit:

graph-service from server/
mcp-server from mcp_server/

Run

UVICORN_HOST=0.0.0.0 \
UVICORN_PORT=8000 \
uv run uvicorn dbx_tools.graphiti.main:app

From the repository root, the local launcher starts the unified runtime:

DATABRICKS_CONFIG_PROFILE=<profile> \
MODEL_NAME=databricks-gpt-5-nano \
bash scripts/run-graphiti-python.sh

The combined application exposes:

FastAPI documentation at /docs
OpenAPI at /openapi.json
REST health and Graphiti routes, including /healthcheck, /search, and ingestion endpoints
Streamable HTTP MCP at /mcp/

Configure Graphiti through the shared environment contract used by the Node runtime and CLI.

Databricks Model Resolution

The process creates one generated auth client and one generated model client at startup. It resolves the fuzzy chat model, ranks embedding endpoints by the configured name, embedding class, and dimensions, then resolves both endpoint routes. REST and MCP reuse the same Graphiti model clients, while the auth client injects refreshed Databricks headers into every model request.

Use From A Notebook

Use the same resolved option names without starting Uvicorn:

from dbx_tools.graphiti.runtime import GraphitiRuntime

async with GraphitiRuntime.from_options(
    {
        "profile": "MY-PROFILE",
    }
) as runtime:
    graphiti = runtime.graphiti

When databaseUrl is omitted, the runtime starts bundled PostgreSQL with pgvector and persists it under graphitiHome, or the platform data directory when no home is configured. The owned PostgreSQL process stops with the runtime, while its data remains for the next start.

Pass a regular PostgreSQL URL to use an existing database. A passwordless non-local URL, Lakebase resource path, or Lakebase project name is resolved by the generated Node Lakebase client. It injects a fresh short-lived credential whenever the asyncpg pool opens a physical connection, without persisting that credential in the URL.

Composition Boundary

dbx_tools.graphiti.main adds FastAPI REST and MCP surfaces around the same importable runtime. Shared environment options are parsed through generated PythonMonkey bindings and mapped into both upstream settings objects.

Metadata

Release files for dbx-tools-graphiti 0.9.50

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dbx-tools-graphiti 0.9.50
File	Size	Uploaded
dbx_tools_graphiti-0.9.50.tar.gz	537.0 kB	Oct 7, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for dbx-tools-graphiti 0.9.50
File	Interpreter	ABI	Platform	Reset
dbx_tools_graphiti-0.9.50-py3-none-any.whl 577.1 kB Oct 7, 2026	Python 3	none	any	Details

Total release size: 1.1 MB

Release files / dbx_tools_graphiti-0.9.50.tar.gz

Download URL	dbx_tools_graphiti-0.9.50.tar.gz
Size	537.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`9b1375c8e80f4d6cfe1a6f1e9046ceec3e28a18e5d4eca56247364292b1aac94`
BLAKE2b-256 checksum How to use checksums	`a9dd4ea62971651a708833c9b6c5646f66c3cf07421d79f09390722e8f7df23c`
Upload date	Oct 7, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/reggie-db/dbx-tools
Publishing commit: github.com/reggie-db/dbx-tools/tree/7211540a941420f7f2b2dea7df37ef4b6ddcd30e

Workflow

Publishing configuration: github.com/reggie-db/dbx-tools/blob/7211540a941420f7f2b2dea7df37ef4b6ddcd30e/.github/workflows/release.yml
Publishing logs: github.com/reggie-db/dbx-tools/actions/runs/37554007054/attempts/1

Artifact

Subject: dbx_tools_graphiti-0.9.50.tar.gz
SHA-256 checksum: 9b1375c8e80f4d6cfe1a6f1e9046ceec3e28a18e5d4eca56247364292b1aac94 Verifying attestations

Release files / dbx_tools_graphiti-0.9.50-py3-none-any.whl

Download URL	dbx_tools_graphiti-0.9.50-py3-none-any.whl
Size	577.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`005dbd5e48f47e0119c7f38ff456b2719a0a8bd9aadcdfe36f2b881b23176c26`
BLAKE2b-256 checksum How to use checksums	`a53b04f6064c4371a363a2bb5d2f44b8373ca47bff5b6111e43b7ac0f5ebed89`
Upload date	Oct 7, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/reggie-db/dbx-tools
Publishing commit: github.com/reggie-db/dbx-tools/tree/7211540a941420f7f2b2dea7df37ef4b6ddcd30e

Workflow

Publishing configuration: github.com/reggie-db/dbx-tools/blob/7211540a941420f7f2b2dea7df37ef4b6ddcd30e/.github/workflows/release.yml
Publishing logs: github.com/reggie-db/dbx-tools/actions/runs/37554007054/attempts/1

Artifact

Subject: dbx_tools_graphiti-0.9.50-py3-none-any.whl
SHA-256 checksum: 005dbd5e48f47e0119c7f38ff456b2719a0a8bd9aadcdfe36f2b881b23176c26 Verifying attestations