KeeperHub

You can run KeeperHub's MCP Server to manage and execute blockchain automation workflows using a flexible client interface. It supports full CRUD for workflows, AI-assisted generation, asynchronous execution with status checks and logs, exposed MCP resources, and API key authentication to keep access secure.

How to use

You will connect an MCP client to the KeeperHub MCP Server to manage workflows and run them. Use the HTTP/SSE transport when you want remote agents to communicate over the network, or use the standard input/output (stdio) transport for local clients that interact directly with the process. In either case, you perform operations to create, read, update, delete, or execute workflows, and you can generate workflows from natural language prompts.

How to install

Prerequisites: make sure you have a modern runtime environment with Node.js and npm or pnpm installed if you plan to run from source or install via package managers. You will also need a KeeperHub API key to authorize access.

# Build the Docker image (recommended for quick setup)
docker build -t keeperhub-mcp .

# Run the server in Docker with your KeeperHub API key
docker run -i --rm \
  -e KEEPERHUB_API_KEY=your_api_key_here \
  keeperhub-mcp

# Run the server locally with Node (if you prefer running from source)
KEEPERHUB_API_KEY=your_api_key_here pnpm start

# Development mode with hot reloading (optional)
KEEPERHUB_API_KEY=your_api_key_here pnpm dev

Additional configuration and usage notes

The server can operate in two transport modes. In stdio mode, the server communicates with local AI clients via standard input and output. In HTTP/SSE mode, the server exposes an HTTP API with Server-Sent Events for remote agents.

Configuration and security

Environment variables control access and mode of operation. The following variables are shown in examples and must be provided as needed.

{
  "KEEPERHUB_API_KEY": "your_api_key_here",
  "KEEPERHUB_API_URL": "https://app.keeperhub.com",
  "PORT": 3000,
  "MCP_API_KEY": "your_secure_mcp_key"
}

Endpoints and authentication

When running in HTTP mode, the server exposes endpoints for health checks, events, and messaging. All HTTP requests must include an Authorization header with a Bearer token to authenticate as an MCP client.

Available tools

list_workflows

Retrieve a paginated list of workflows within the organization. Supports limit and offset to control results.

get_workflow

Fetch detailed information for a single workflow by its ID.

create_workflow

Create a new workflow with a name, optional description, and optional nodes and edges to define the workflow graph.

update_workflow

Update the properties or structure of an existing workflow, including its name, description, nodes, and edges.

delete_workflow

Remove a workflow by its ID from the organization.

generate_workflow

AI-assisted generation of a new workflow from a natural language prompt, with optional modification of an existing workflow.

execute_workflow

Start asynchronous execution of a workflow, with optional input data.

get_execution_status

Poll the status of an ongoing workflow execution.

get_execution_logs

Retrieve logs for a completed or in-progress workflow execution.

keeperhub://workflows

Resource endpoint exposing a list of workflows within the organization.

keeperhub://workflows/{id}

Resource endpoint exposing details for a specific workflow by ID.