protocol-mcp
MCP that connects to wetlab protocol resources, including protocols.io
Getting started
Please refer to the documentation, in particular, the API documentation.
You can also find the project on BioContextAI, the community-hub for biomedical MCP servers: protocol-mcp on BioContextAI.
Installation
You need to have Python 3.10 or newer installed on your system. If you don't have Python installed, we recommend installing uv.
There are several alternative options to install protocol-mcp:
1. Use uvx to run it immediately
After publication to PyPI:
uvx protocol_mcp
Or from a Git repository:
uvx git+https://github.com/biocontext-ai/protocol-mcp.git@main
2. Include it in one of various clients that supports the mcp.json standard
If your MCP server is published to PyPI, use the following configuration:
{
"mcpServers": {
"protocol-mcp": {
"command": "uvx",
"args": ["protocol_mcp"]
}
}
}
In case the MCP server is not yet published to PyPI, use this configuration:
{
"mcpServers": {
"protocol-mcp": {
"command": "uvx",
"args": ["git+https://github.com/biocontext-ai/protocol-mcp.git@main"]
}
}
}
For purely local development (e.g., in Cursor or VS Code), use the following configuration:
{
"mcpServers": {
"protocol-mcp": {
"command": "uvx",
"args": [
"--refresh",
"--from",
"path/to/repository",
"protocol_mcp"
]
}
}
}
If you want to reuse and existing environment for local development, use the following configuration:
{
"mcpServers": {
"protocol-mcp": {
"command": "uv",
"args": ["run", "--directory", "path/to/repository", "protocol_mcp"]
}
}
}
3. Install it through pip:
pip install --user protocol_mcp
4. Install the latest development version:
pip install git+https://github.com/biocontext-ai/protocol-mcp.git@main
Contact
If you found a bug, please use the issue tracker.
Citation
t.b.a
Metadata
Release files for protocol-mcp 0.1.3
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 |
|---|---|---|---|---|
| protocol_mcp-0.1.3.tar.gz | 167.4 kB | With provenance | Details for protocol_mcp-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| protocol_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for protocol_mcp-0.1.3-py3-none-any.whl |
Total release size: 188.6 kB
Release files / protocol_mcp-0.1.3.tar.gz
| Download URL | protocol_mcp-0.1.3.tar.gz |
|---|---|
| Size | 167.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb70352e572e6ef4d51cfd6886bb6eb76f0bbdcd476e307bf92c666f7c693c89
|
|
BLAKE2b-256 checksum How to use checksums |
6420f5ce7074e063cf6689d688309043e8966eb3cd75dc4c83fb5190172aa2d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 27, 2026.
Transparency logRelease files / protocol_mcp-0.1.3-py3-none-any.whl
| Download URL | protocol_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3324014795ca7f625a5c6a828a5f2f9056f0b7b3530c9cdf42a151cc0954b1a2
|
|
BLAKE2b-256 checksum How to use checksums |
fbbab2f5d5712fcb3476abb3904e7be5ff8464e09f407cdfa0e6711e1ede4000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 27, 2026.
Transparency logSecurity for protocol-mcp 0.1.3
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for protocol_mcp-0.1.3.tar.gz
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 Feb 27, 2026.
Transparency logA 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.