bss-mcp
[!WARNING] This project is being discontinued in favor of a server-side MCP API.
An MCP server wrapping bssclient, exposing read-only BSS investigation-order data to AI assistants (e.g. Claude Desktop) for debugging.
Requires Python 3.11+.
Tools
| Tool | Description |
|---|---|
get_ermittlungsauftraege |
List investigation orders (limit, offset; limit=0 uses the server default) |
get_ermittlungsauftraege_by_malo |
Investigation orders for a Marktlokation ID |
get_aufgabe_stats |
Task status statistics across all Aufgaben types |
get_all_ermittlungsauftraege |
Fetches all investigation orders by iterating pages (package_size controls page size, default 100) |
Installation
pip install bss-mcp
For use with Claude Desktop or another MCP client, pipx installs the server as a standalone executable:
pipx install bss-mcp
Configuration
Set environment variables or place them in a .env file in the working directory from which the MCP server is launched (for Claude Desktop this is typically the user's home directory):
| Variable | Required | Description |
|---|---|---|
BSS_URL |
Yes | Base URL of the BSS server, e.g. https://basicsupply.example.de/ |
BSS_AUTH_TYPE |
No (default: basic) |
basic or oauth |
BSS_USER |
If basic auth | Username |
BSS_PASSWORD |
If basic auth | Password |
BSS_CLIENT_ID |
If OAuth | OAuth client ID |
BSS_CLIENT_SECRET |
If OAuth | OAuth client secret |
BSS_TOKEN_URL |
If OAuth | Token endpoint URL |
Usage
Run the server directly:
bss-mcp
Or add to your MCP client config (e.g. Claude Desktop). Use the full path to the executable if bss-mcp is not on the PATH seen by the client:
{
"mcpServers": {
"bss": {
"command": "bss-mcp",
"env": {
"BSS_URL": "https://basicsupply.example.de/",
"BSS_AUTH_TYPE": "basic",
"BSS_USER": "...",
"BSS_PASSWORD": "..."
}
}
}
}
Development
This project follows the Hochfrequenz Python template — see it for general setup instructions (uv, CI, PyPI publishing).
Install the dev dependencies with uv:
uv sync --group dev
Common tasks (the PYTHONPATH=src prefix makes the src layout importable):
PYTHONPATH=src uv run --group tests pytest # run tests
PYTHONPATH=src uv run --group type_check mypy --show-error-codes src/bss_mcp --strict # mypy --strict
PYTHONPATH=src uv run --group linting ruff check . # ruff (lint)
PYTHONPATH=src uv run --group coverage coverage run -m pytest # coverage (≥ 80 %)
uv run --group linting ruff format . # ruff (format)
PYTHONPATH=src uv run --group linting ruff check --select I . # ruff (import sort)
Metadata
Release files for bss-mcp 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bss_mcp-0.2.2.tar.gz | 183.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bss_mcp-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 188.5 kB
Release files / bss_mcp-0.2.2.tar.gz
| Download URL | bss_mcp-0.2.2.tar.gz |
|---|---|
| Size | 183.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7abe914c6ce53a600dc562729f1b607058e2beeb156883ebd5ec44555fa1440
|
|
BLAKE2b-256 checksum How to use checksums |
79d96d3618dcc81831ce9705c813b773186cb1ab56632081ef6f4d57d246ab2e
|
| 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 Aug 19, 2026.
Transparency logRelease files / bss_mcp-0.2.2-py3-none-any.whl
| Download URL | bss_mcp-0.2.2-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a4cdb04d71db212757f876cfde116203ae1f92d970a86ed7a661c60c683d4fb
|
|
BLAKE2b-256 checksum How to use checksums |
ac7b80ed2cc0163aca83539076f65910f05b52e60664eb5ec7b7dea571130564
|
| 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 Aug 19, 2026.
Transparency log