keeperhub-hermes-plugin
A Hermes agent plugin for
KeeperHub — gives your agent kh_* tools to manage and
run on-chain automation workflows, browse templates and protocol actions, and
(opt-in) execute transactions, all over the KeeperHub MCP API.
Install
Recommended — Hermes plugin manager (no pip needed):
hermes plugins install KeeperHub/hermes-plugin --enable
Or via pip / PyPI:
pip install keeperhub-hermes-plugin
then enable it in your Hermes profile ~/.hermes/config.yaml:
plugins:
enabled:
- keeperhub
Either way, set your KeeperHub organization API key (prefix kh_, from
Settings → API Keys → Organisation) and restart Hermes:
export KH_API_KEY="kh_..."
The plugin's only dependency is httpx, which ships with Hermes — so the
clone-based install needs nothing extra.
Safety: read-only by default
By default the plugin registers read-only tools (list/get/search workflows, executions, templates, integrations, action schemas, status). Tools that change organization state or move funds on-chain are withheld until you opt in:
export KEEPERHUB_ENABLE_WRITES=true
The gate is structural — withheld tools are never registered, so the agent can neither call nor be delegated a tool that does not exist.
| Mode | Tools |
|---|---|
| Default (read-only) | kh_list_workflows, kh_get_workflow, kh_search_org_workflows, kh_search_workflows_marketplace, kh_get_execution_status, kh_get_execution_logs, kh_get_direct_execution_status, kh_search_templates, kh_get_template, kh_search_plugins, kh_get_plugin, kh_list_action_schemas, kh_search_protocol_actions, kh_list_integrations, kh_get_wallet_integration, kh_ai_generate_workflow, kh_tools_documentation, kh_status |
KEEPERHUB_ENABLE_WRITES=true adds |
kh_create_workflow, kh_update_workflow, kh_delete_workflow, kh_execute_workflow, kh_deploy_template, kh_call_workflow, kh_execute_protocol_action, kh_execute_transfer, kh_execute_contract_call, kh_execute_check_and_execute |
Try it
Ask your agent things like:
- "List my KeeperHub workflows"
- "Show me workflow
<id>" - "What action schemas and chains does KeeperHub support?"
- "Check my KeeperHub connection status" → runs
kh_status
Configuration
| Env var | Required | Description |
|---|---|---|
KH_API_KEY |
yes | KeeperHub organization API key (kh_…). |
KEEPERHUB_ENABLE_WRITES |
no | Set to true/1/yes/on to register write/exec tools. Default off. |
Development
pip install -e ".[dev]"
pytest -q
License
1 maintainer
Metadata
1 maintainer
Release files for keeperhub-hermes-plugin 1.0.0
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 | |
|---|---|---|---|---|
| keeperhub_hermes_plugin-1.0.0.tar.gz | 21.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keeperhub_hermes_plugin-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.8 kB
Release files / keeperhub_hermes_plugin-1.0.0.tar.gz
| Download URL | keeperhub_hermes_plugin-1.0.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92dc9b06b476eb3d20ad895a0dc8b200e298205198425c149444e8350b96ad1e
|
|
BLAKE2b-256 checksum How to use checksums |
c26185cf623ff0309b79a1de395793e0a5e51d6d197f9ebdef21b1ff62f6ee4a
|
| 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 17, 2026.
Transparency logRelease files / keeperhub_hermes_plugin-1.0.0-py3-none-any.whl
| Download URL | keeperhub_hermes_plugin-1.0.0-py3-none-any.whl |
|---|---|
| Size | 27.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd6034efa859cbc65529c8edabe638118c5822136d5484a8c5ca49e794c916c4
|
|
BLAKE2b-256 checksum How to use checksums |
caa665388e0494b11ba30c91daf1a072adfe06e4d183fda727eaa5d37aaed2a4
|
| 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 17, 2026.
Transparency logSecurity for keeperhub-hermes-plugin 1.0.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for keeperhub_hermes_plugin-1.0.0.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 Jun 17, 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.
