Yaozh MCP Stdio Proxy
Local stdio MCP proxy for the remote Drug MCP streamable-http service.
It is intended for MCP clients that only support stdio. The proxy runs locally and forwards MCP tool calls to the remote HTTP MCP endpoint.
MCP client
-> local stdio proxy
-> remote streamable-http MCP service
The proxy does not store API keys or results. Authentication, permissions, quota and audit logs are still handled by the remote MCP service.
Install And Run With uvx
After publishing this package to PyPI:
uvx yaozh-mcp-stdio --url http://<server-ip>/mcp --api-key <token>
Recommended usage with environment variables:
MCP_HTTP_URL="http://<server-ip>/mcp" \
MCP_API_KEY="<token>" \
uvx yaozh-mcp-stdio
Windows PowerShell:
$env:MCP_HTTP_URL="http://<server-ip>/mcp"
$env:MCP_API_KEY="<token>"
uvx yaozh-mcp-stdio
MCP Client Config
Pass token by environment variables:
{
"mcpServers": {
"drug-mcp": {
"command": "uvx",
"args": [
"yaozh-mcp-stdio"
],
"env": {
"MCP_HTTP_URL": "http://<server-ip>/mcp",
"MCP_API_KEY": "<token>"
}
}
}
}
Or pass token by arguments:
{
"mcpServers": {
"drug-mcp": {
"command": "uvx",
"args": [
"yaozh-mcp-stdio",
"--url",
"http://<server-ip>/mcp",
"--api-key",
"<token>"
]
}
}
}
Options
yaozh-mcp-stdio --help
--url Remote streamable-http MCP URL. Default reads MCP_HTTP_URL.
--api-key Bearer token. Default reads MCP_API_KEY.
--timeout Remote request timeout in seconds. Default reads MCP_PROXY_TIMEOUT or 120.
Local Development
Install editable:
pip install -e .
yaozh-mcp-stdio --url http://127.0.0.1/mcp --api-key <token>
Build package:
python -m pip install --upgrade build twine
python -m build
twine check dist/*
Publish to TestPyPI:
twine upload --repository testpypi dist/*
Publish to PyPI:
twine upload dist/*
Metadata
Release files for yaozh-mcp-stdio 0.1.1
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 | Actions |
|---|---|---|---|---|
| yaozh_mcp_stdio-0.1.1.tar.gz | 3.2 kB | Without provenance | Details for yaozh_mcp_stdio-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| yaozh_mcp_stdio-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for yaozh_mcp_stdio-0.1.1-py3-none-any.whl |
Total release size: 7.4 kB
Release files / yaozh_mcp_stdio-0.1.1.tar.gz
| Download URL | yaozh_mcp_stdio-0.1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa747d88f39d0f593309ac177a3cdf2e26ac6e975b71ae9ff22389b91c26709c
|
|
BLAKE2b-256 checksum How to use checksums |
4218be811d50e99ee7ac8a5bec8ee4f0afecbfe00179b90b2c7121f846a5a1b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Release files / yaozh_mcp_stdio-0.1.1-py3-none-any.whl
| Download URL | yaozh_mcp_stdio-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
423a799c1210e1e1d40e72d62a455ab0e6f58c38116e752e4b8a6f401ed0b7ce
|
|
BLAKE2b-256 checksum How to use checksums |
db2bb0b8c63ea926f8bb254025e999d4c42f8684b5a8ab0343b98e4a8c01ee5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Security for yaozh-mcp-stdio 0.1.1
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.