SPDK Python Bindings and Scripts
Overview
The Storage Performance Development Kit (SPDK) provides a set of tools and libraries for writing high performance, scalable, user-mode storage applications. This directory contains Python bindings and scripts that facilitate interaction with SPDK components.
Installation
Examples below are using UV.
An extremely fast Python package and project manager, written in Rust.
$ uv venv
$ source .venv/bin/activate
Then, you can install spdk from PyPI with:
uv pip install spdk
or install from source with:
git clone https://github.com/spdk/spdk.git
cd spdk
uv pip install python/
Getting Started
From a shell:
spdk-rpc rpc_get_methods
From a Python interpreter:
>>> from spdk.rpc.client import JSONRPCClient
>>> client = JSONRPCClient(server_addr, port)
>>> client.rpc_get_methods()
For more information, see https://spdk.io/doc/jsonrpc.html
Model Context Protocol (MCP)
The Model Context Protocol (MCP) lets you build servers that expose data and functionality to LLM applications in a secure, standardized way. Think of it like a web API, but specifically designed for LLM interactions.
MCP servers can:
- Expose data through Resources (think of these sort of like GET endpoints; they are used to load information into the LLM's context)
- Provide functionality through Tools (sort of like POST endpoints; they are used to execute code or otherwise produce a side effect)
- Define interaction patterns through Prompts (reusable templates for LLM interactions)
- And more!
The SPDK MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with SPDK APIs, enabling advanced automation and interaction capabilities for developers and tools.
$ uv venv
$ source .venv/bin/activate
$ uv pip install spdk[mcp]
or locally
$ uv pip install python/[mcp]
You can install this server in Claude Desktop and interact with it right away by running:
mcp install server.py
Alternatively, you can test it with the MCP Inspector:
mcp dev server.py
Release files for spdk 26.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spdk-26.9.tar.gz | 78.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spdk-26.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 181.5 kB
Release files / spdk-26.9.tar.gz
| Download URL | spdk-26.9.tar.gz |
|---|---|
| Size | 78.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
153df191f1bdfcea37fc40def69983943d2249b50d86bb80e99cfa84cc62cc78
|
|
BLAKE2b-256 checksum How to use checksums |
ed921f3fdd4d8e74152f45e26883e1982f5a99398037469cd28595fcc4f2629c
|
| 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 25, 2026.
Transparency logRelease files / spdk-26.9-py3-none-any.whl
| Download URL | spdk-26.9-py3-none-any.whl |
|---|---|
| Size | 103.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42037d98845c82e9317bc8b3c7521af3eb785e44cb5baf13c40a103d5df04f49
|
|
BLAKE2b-256 checksum How to use checksums |
6d2c5440e5b3e489823d051bcf4e2c32c061b57886241a874cdf01899126ee6f
|
| 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 25, 2026.
Transparency log