tarvo
tarvo is an intentionally small and narrow tool to make read-only queries of Jira, Github, and other services. It exists specifically to allow Agentic access to remote APIs in cases where MCP is specifically disallowed. Installation is:
uv add tarvo
There is a .env.example file that should be copied to .env and then edited to contain the credentials tarvo needs. Then running
tarvo doctor
will check the .env file completeness and run a small test query of the remote services.
Jira subcommands
tarvo jira get <KEY>
tarvo jira query [JQL] [--max-results N]
Examples:
tarvo jira get TARV-123
tarvo jira query 'status = "To Do"' --max-results 5
1 maintainer
Metadata
1 maintainer
Release files for tarvo 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tarvo-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / tarvo-0.2.2-py3-none-any.whl
| Download URL | tarvo-0.2.2-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e060c4e970d1be2b579c298740c25a7c5ed5d0062b47bdad9003a1f148079016
|
|
BLAKE2b-256 checksum How to use checksums |
eadaea5d25a6efe7f487d70b005a069c6f056f11542f64dcf036e7f10732d270
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 2, 2026.
Transparency log
