kx-mcp-core
The assembly layer of the KX MCP composition container: a FastMCP 3.x parent that mounts pluggable backend bundles (KDB-X, KDB.AI, or your own) into one served MCP surface, and the home of the container's control plane — inbound authentication, the authorization seam, and per-dispatch audit.
Install it when you are assembling an MCP server from KX backend bundles:
uv add kx-mcp-core kx-mcp-kdbx # from PyPI
All the packages version in lockstep; pin them together (
kx-mcp-core==0.5.0) when you depend on a version. See the deployment guide.
What's in the box
make_parent(name, auth=None)— builds the parent server; inbound auth (KX_MCP_AUTH:unset/static/jwks/oidc_proxy/entra) and the audit middleware attach here.mount_bundle/try_mount_bundle— mount a bundle'sbuild_server()under a namespace; thetry_variant disables an unreachable backend instead of crashing the container.- The
kx-mcplauncher — the zero-code path:kx-mcp --bundles kdbx,kdbai(a bundle named<name>is the importable packagekx_mcp_<name>). kx_mcp_core.auth—current_principal()(the validated inbound principal, visible to mounted tools), the@authorizePEP-1 capability decorator,AuditMiddleware, and re-exports of the sharedkx-auth-coreseams so bundle imports stay stable.
Minimal glue
from kx_mcp_core import make_parent, load_build_server, try_mount_bundle
app = make_parent("kx-mcp")
try_mount_bundle(app, load_build_server("kx_mcp_kdbx"), namespace="kdbx")
app.run(transport="streamable-http", host="127.0.0.1", port=8000)
Or no glue at all:
uvx --from kx-mcp-core --with kx-mcp-kdbx kx-mcp --bundles kdbx
Documentation
The full docs live in the kx-mcp-server-container
repository, under docs/: the deployment guide,
the auth reference
(inbound modes, outbound strategies, authorization), and the
extender guide
for writing your own bundle — plus a reference downstream build
(demos/extending/)
showing a standalone project that assembles a server from these wheels.
All workspace packages version in lockstep from release tags — pin kx-mcp-core and your bundles
to the same version.
1 maintainer
Metadata
1 maintainer
Release files for kx-mcp-core 0.5.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 | Actions Reset |
|---|---|---|---|---|
| kx_mcp_core-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for kx_mcp_core-0.5.0-py3-none-any.whl |
Release files / kx_mcp_core-0.5.0-py3-none-any.whl
| Download URL | kx_mcp_core-0.5.0-py3-none-any.whl |
|---|---|
| Size | 65.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6936f76259847244bda23020d0f916461f27b901202cf7db9af042fc859dcc9
|
|
BLAKE2b-256 checksum How to use checksums |
f922a4afe07a97d79da4f22c91b1253a5abb38786706e2684eeb87f2a334991c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for kx-mcp-core 0.5.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
