How to run locally?
I use the command uv init linux-do-mcp under the root path src/linux-do-mcp/python
If you want to run this MCP Server locally, you can follow the step bellow:
cd to src/linux-do-mcp/python, and install the dependency
uv venv
.venv\Scripts\activate
uv add "mcp[cli]" httpx
pip install .
run the following command to test in dev env
mcp dev src/linux_do_mcp/main.py
1 maintainer
Metadata
1 maintainer
Release files for linux-do-mcp-steve 0.1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| linux_do_mcp_steve-0.1.0.5.tar.gz | 14.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| linux_do_mcp_steve-0.1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.6 kB
Release files / linux_do_mcp_steve-0.1.0.5.tar.gz
| Download URL | linux_do_mcp_steve-0.1.0.5.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac641a2bf512db505ad50f9988d1446ce0279ea6df8cdef6183e6a7479016a09
|
|
BLAKE2b-256 checksum How to use checksums |
cacf4d70e815d023c6de5481f3b2f5f09d42623fbc75a684dbc0161926a05a89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.26
|
Release files / linux_do_mcp_steve-0.1.0.5-py3-none-any.whl
| Download URL | linux_do_mcp_steve-0.1.0.5-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
298fd88345dd249d48cf76ec41c252489ba6e0a562477e5241ad34698c717dcd
|
|
BLAKE2b-256 checksum How to use checksums |
083b2bd3c1483ebbabaa2eb52414959b9b32d54bf9a35d07e581229ea19dad97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.26
|
Security for linux-do-mcp-steve 0.1.0.5
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.
