hive

Hive MCP Server provides a bridge between AI assistants and the Hive blockchain using the Model Context Protocol. It exposes a suite of tools that let you query account information, read posts, fetch histories, and manage content on Hive. When authenticated, it can perform actions such as voting, creating posts or comments, and sending tokens, all mediated via the MCP interface. The tools are designed to be called from an MCP client or integrated into AI workflows to enable informed, blockchain-aware interactions.

Key capabilities include reading data (get_account_info, get_post_content, get_posts_by_tag, get_posts_by_user, get_account_history, get_chain_properties, get_vesting_delegations), performing authenticated blockchain actions (vote_on_post, create_post, create_comment, send_token), cryptographic operations (sign_message, verify_signature), and encrypted messaging (encrypt_message, decrypt_message, send_encrypted_message, get_encrypted_messages). Use the authentication-dependent tools by supplying your Hive keys as environment variables or secure config, and ensure you never expose private keys in logs or version control.

Prerequisites:

• Node.js installed (npx available)
• Internet access to fetch MCP server package

Installation steps:

1. Install and run the MCP server via npx within your preferred environment. This example uses the Hive MCP server package provided in the README:

# Option A: Quick start with npx (no local install required)
npx -y @gluneau/hive-mcp-server

2. (Optional) Install locally for repeated runs:

npm install @gluneau/hive-mcp-server --save

3. Prepare environment variables for authentication (example shown in configuration). Ensure sensitive keys are stored securely.

export HIVE_USERNAME=your-hive-username
export HIVE_POSTING_KEY=your-hive-posting-private-key
export HIVE_ACTIVE_KEY=your-hive-active-private-key
export HIVE_MEMO_KEY=your-hive-memo-private-key

4. Run the server with the appropriate command and configuration (see mcp_config for details).

Security and configuration tips:

• Never commit private keys to source control. Use environment variables or a secrets manager.
• For production, consider using a dedicated secrets store and restricted IAM roles.
• The server exposes authenticated actions (vote, post, send tokens). Ensure your application enforces proper authentication and input validation.
• If you encounter issues with key formats, ensure keys are in the correct Hive key format and that the configured account has the necessary permissions.
• When debugging, use the MCP Inspector to test individual tools and observe responses from the server.