KeeperHub-PluginHub

KeeperHub is where you build and run onchain automations. You design workflows with triggers, parallel steps, transaction execution, DeFi protocol interactions, and notifications. Every run is logged so you always know what happened and when.

This project makes that entire layer available from inside the agent runtimes developers are already using. Connect your KeeperHub organisation to Eliza, OpenClaw, or Hermes and your agents can discover workflows, trigger runs, monitor execution, read step logs, work with templates and marketplace flows, and access KeeperHub's web3 features. All of this happens in plain language without leaving the agent interface.

The idea is simple. Agents handle conversation and decisions. KeeperHub handles the hard parts: scheduling, wallet custody, retries, parallel execution, and observability. The result is repeatable and auditable operations instead of fragile custom code that breaks the moment something unexpected happens onchain.

The alternative is building all of that by hand inside every agent. That means writing your own wallet management, handling nonces, building retry logic, and having no shared audit trail. This integration removes that problem entirely.

It works across three of the biggest agent runtimes. ElizaOS is one of the largest crypto AI agent frameworks with over 18,000 GitHub stars. OpenClaw is the biggest AI agent framework on its stack. Hermes is the runtime of choice for Telegram and terminal operators. One KeeperHub account works across all three.

Quick try demos are available via web chat and Telegram. Full setup instructions are available for all three runtimes if you want to connect your own KeeperHub organisation.

What The Plugin Does The package @elizaos/plugin-keeperhub wraps the KeeperHub MCP API as native ElizaOS actions. The current plugin exposes 26 actions across the full KeeperHub workflow lifecycle:

Workflow management: list, get, create, update, delete, search, and execute workflows. Execution monitoring: check execution status and view execution logs. Templates: search templates, inspect them, and deploy them into an organization. Integrations: list configured integrations and inspect wallet integrations. Protocol actions: read from Aave, Chainlink, Morpho, Uniswap, Compound, Lido, and other DeFi systems. Direct execution: transfer tokens, call contracts, and run conditional check-and-execute flows. Marketplace workflows: search public callable workflows and invoke them by slug. AI workflow generation: describe an automation in natural language and have KeeperHub generate the workflow definition. Documentation access: expose KeeperHub MCP docs directly to the agent.

We ship three integrations that all speak the same remote contract: KeeperHub’s hosted MCP at https://app.keeperhub.com/mcp using JSON-RPC (MCP 2024-11-05), Bearer organisation keys (kh_…), initialize, then tools/call. There is no custom REST surface in the middle; every workflow, template, execution, integration, and on chain helper path funnels through that one MCP session.

ElizaOS (@elizaos/plugin-keeperhub) is TypeScript on Bun inside the ElizaOS monorepo layout. Config is validated with Zod (key shape and kh_ prefix). A KeeperHubService subclasses Eliza’s Service: it holds the cached mcp-session-id, increments request ids, POSTs JSON-RPC, and parses tool output from the single text content block ( JSON.parse with a string fallback so partial or non-JSON replies still propagate). 401 and certain 404 “session expired” shapes tear down and re‑initialize, then retry the failing call—the same resilience idea as OpenClaw. 26 Actions delegate to that service (workflows CRUD plus execute/search, execution status/logs, templates, schemas, integrations, protocol reads, direct execution, marketplace, AI generation, docs). A Provider pushes organisation context into prompts so answers line up with what KeeperHub reports.

OpenClaw (openclaw-keepershub) is TypeScript built against the OpenClaw plugin SDK: TypeBox for 28 tool parameter schemas, openclaw.plugin.json for the manifest, and @keepershub/openclaw-keepershub on ClawHub for installs. KeeperHubClient is intentionally minimal: one MCP client per API key, lazy first request so gateway startup stays cold unless a tool fires, JSON.parse on MCP text payloads, transparent session refresh on expiry, optional logger injection behind a tiny interface so the plugin works with OpenClaw’s logger or console.

Hermes is Python, httpx, pyproject.toml, plugin.yaml with requires_env for KH_API_KEY, Hermes entry wiring, and pytest. Tool names and contracts are kept in lockstep with openclaw.plugin.json so behavior matches OpenClaw line for line (kh_status, workflows, execution, marketplace, etc.).

Quality and partners: Automated tests (bun test on TypeScript stacks, pytest on Hermes) cover client and tool routing. ElizaOS gives the canonical runtime, actions, providers, services model we extended. OpenClaw’s Gateway and tooling benefited us by exposing structured tools consumers can inspect at runtime. KeeperHub as the MCP host meant we focused on correct transport + parity rather than re‑implementing execution engines.