vera-mcp
vera-mcp is the Model Context Protocol adapter for VERA archives and
libraries. It depends on vera-doc for search/storage and vera-ingest for
viewer helpers (pages, figures, regions). It exposes those capabilities as MCP
tools without owning retrieval implementation.
Install
python -m pip install "vera-mcp>=0.3.0"
# or
python -m pip install "vera-cli[mcp]>=0.3.0"
See the vera-mcp documentation for installation, client setup, tool contracts, and API reference.
See the MCP guide.
Metadata
Release files for vera-mcp 0.3.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 | |
|---|---|---|---|
| vera_mcp-0.3.1.tar.gz | 5.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vera_mcp-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 kB
Release files / vera_mcp-0.3.1.tar.gz
| Download URL | vera_mcp-0.3.1.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a5a73bc4986abc0340fd09f81274479f4301a5081fae68837f7a2efa4e7b7a0
|
|
BLAKE2b-256 checksum How to use checksums |
2ae1df980d4051a74565ae0ccfefce20b89ecaeb003a44fe91ee78fb0dd075f6
|
| 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 25, 2026.
Transparency logRelease files / vera_mcp-0.3.1-py3-none-any.whl
| Download URL | vera_mcp-0.3.1-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
982925d0852adcc9ae1232ae6f0333d204aa08ec99fda7702d516c602cc40f7f
|
|
BLAKE2b-256 checksum How to use checksums |
40a0eba9752a1bea44dc97ea481c5fb70e74eb55bf477104d8fc1424fed7ac4d
|
| 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 25, 2026.
Transparency log