keeperhub-ai-tools-mcp-server

Files (1)

• SKILL.md

SKILL.md (first lines)

# MCP Server

## Overview
Documentation for MCP Server integration and usage within the KeeperHub ecosystem.

[AI Tools](https://docs.keeperhub.com/ai-tools)

The KeeperHub MCP server exposes tools over the Model Context Protocol, enabling AI agents to create, execute, and monitor blockchain automation workflows.

### Remote (recommended)
Connect directly to KeeperHub’s hosted MCP server. No local process or CLI installation needed.

`claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp`

`claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp`

Then run /mcp inside Claude Code to complete the OAuth authorization via browser. KeeperHub will ask you to approve access, and the token is stored automatically.

`/mcp`

For headless or CI environments where browser auth is not available, pass an API key:

`claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp \ --header "Authorization: Bearer kh_your_key_here"`

`claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp \ --header "Authorization: Bearer kh_your_key_here"`

### Via Claude Code Plugin
Install the [Claude Code Plugin](https://docs.keeperhub.com/ai-tools/claude-code-plugin) for additional skills and slash commands on top of the MCP tools. The plugin connects to the same remote endpoint.

### Local via kh CLI (deprecated)
The [kh CLI](https://github.com/KeeperHub/cli) can run a local MCP server over stdio via kh serve --mcp. This is deprecated in favor of the remote endpoint above and will be removed in a future release.

`kh`

`kh serve --mcp`

## Authentication
The MCP endpoint supports two authentication methods:
OAuth 2.1 (browser-based): When you add the remote MCP server, Claude Code discovers the OAuth metadata at /.well-known/oauth-authorization-server and opens a browser for authorization. Tokens are managed automatically (1-hour access tokens, 30-day refresh tokens).

`/.well-known/oauth-authorization-server`

API keys (headless): Pass an organization API key (kh_ prefix) as a Bearer token. Create one at [app.keeperhub.com](https://app.keeperhub.com) under Settings > API Keys > Organisation tab.

`kh_`

## Organization Scoping
Each MCP connection is scoped to a single organization. The org is determined by your authentication method:
- OAuth: The org active in your browser session when you approve the authorization request.
- API key: The org the key was created in (visible on the API Keys page).
All tools operate within this org — listing workflows, creating workflows, executing, and viewing integrations. There is no way to access another org’s resources from the same connection.

### Switching Organizations
To work with a different org, re-authenticate:
OAuth (Claude Code): Switch your active org at [app.keeperhub.com](https://app.keeperhub.com) using the org switcher, then reconnect the MCP server. In Claude Code, remove and re-add the server:

`claude mcp remove keeperhub claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp`

`claude mcp remove keeperhub claude mcp add --transport http keeperhub https://app.keeperhub.com/mcp`

Complete the OAuth flow again — the new active org will be captured.
API key: Create a separate API key in the target org and update the MCP server configuration with the new key.

### Working with Multiple Organizations
If you regularly work across multiple orgs, add a separate MCP server entry for each:

`{ "mcpServers": { "keeperhub-acme": { "type": "http", "url": "https://app.keeperhub.com/mcp", "headers": { "Authorization": "Bearer kh_acme_key" } }, "keeperhub-personal": { "type": "http", "url": "https://app.keeperhub.com/mcp", "headers": { "Authorization": "Bearer kh_personal_key" } } } }`

`{ "mcpServers": { "keeperhub-acme": { "type": "http", "url": "https://app.keeperhub.com/mcp", "headers": { "Authorization": "Bearer kh_acme_key" } }, "keeperhub-personal": { "type": "http", "url": "https://app.keeperhub.com/mcp", "headers": { "Authorization": "Bearer kh_personal_key" } } } }`

Each server entry has its own tool namespace, so the AI agent can distinguish which org to target based on the server name.

### Workflow Management
`list_workflows`

`limit`

`offset`

`get_workflow`

`create_workflow`

`list_action_schemas`

`update_workflow`

`enabled: false`

`delete_workflow`

`force: true`

### Execution
`execute_workflow`

`get_execution_status`

`get_execution_logs`

### I Generation
`ai_generate_workflow`

### Action Schemas
`list_action_schemas`

`web3`

`discord`

`sendgrid`

`webhook`

`system`

### Plugins
`search_plugins`

From nickthelegend/keeperhub-skills, MIT.

More from nickthelegend/keeperhub-skills