Provides a bridge to Hive with data access, actions, and encrypted messaging via the Model Context Protocol.
Configuration
View docs{
"mcpServers": {
"gluneau-hive-mcp-server": {
"command": "npx",
"args": [
"-y",
"@gluneau/hive-mcp-server"
],
"env": {
"HIVE_MEMO_KEY": "your-hive-memo-private-key",
"HIVE_USERNAME": "your-hive-username",
"HIVE_ACTIVE_KEY": "your-hive-active-private-key",
"HIVE_POSTING_KEY": "your-hive-posting-private-key"
}
}
}
}Hive MCP Server provides a bridge that lets AI assistants interact with the Hive blockchain through the Model Context Protocol. It enables querying account data, retrieving posts, voting, posting, messaging, and encrypted communications, empowering AI to operate on Hive with authenticated actions when configured.
You connect to the Hive MCP Server through an MCP client or an integrated AI assistant. Use the available tools to fetch account details, read posts by tag or user, vote on content, create posts or comments, transfer HIVE or HBD, and manage encrypted messages. You can also sign and verify messages with Hive keys to prove identity. When you enable authentication, you can perform actions that require posting or active keys.
Prerequisites: ensure you have Node.js and npm installed on your system. You will run the MCP server through a local runtime via a standard MCP client configuration.
Install the MCP server client locally using npm and start it through the specified runtime command. The server is designed to be run through a lightweight CLI invocation and wired into your MCP client configuration.
Start the MCP server using the command and arguments shown in the configuration snippet.
Authentication and security: for actions that modify the Hive blockchain (such as posting, voting, or sending tokens), configure environment variables with your Hive keys. Do not share private keys or commit them to version control. Use safe storage for credentials and rotate keys as needed.
Configuration and environment: your MCP client will read the environment variables you provide for identity and permissions. The server exposes a range of tools for data retrieval, cryptographic operations, and encrypted messaging.
Troubleshooting: verify your environment variables are correctly set, confirm the MCP server is reachable by your client, and check for any authentication errors in the client logs. If you encounter cryptographic or messaging issues, ensure the correct key type is used for signing or decryption.
Examples of common workflows include fetching account data, retrieving recent posts by a user, creating a new Hive post, and sending a small token transfer with an accompanying encrypted message.
npx @modelcontextprotocol/inspector npx @gluneau/hive-mcp-server{
"mcpServers": {
"hive": {
"command": "npx",
"args": ["-y", "@gluneau/hive-mcp-server"],
"env": {
"HIVE_USERNAME": "your-hive-username",
"HIVE_POSTING_KEY": "your-hive-posting-private-key",
"HIVE_ACTIVE_KEY": "your-hive-active-private-key",
"HIVE_MEMO_KEY": "your-hive-memo-private-key"
}
}
}
}The server exposes a range of tools for data access, blockchain actions, cryptography, and encrypted messaging. See the tool list for all available endpoints and their parameters.
Fetch detailed information about a Hive blockchain account including balance, authority, voting power, and other metrics.
Retrieve a specific Hive blog post identified by author and permlink.
Retrieve posts filtered by a specific tag and sorting category (trending, hot, created, etc.).
Fetch posts authored by a specific user or in their feed.
Get the transaction history for an account with optional operation filtering.
Fetch current Hive blockchain properties and statistics.
Get a list of vesting delegations made by a specific account.
Vote on a Hive post using the configured account (requires posting key).
Create a new Hive blog post using the configured account (requires posting key).
Comment on an existing post or reply to a comment (requires posting key).
Send HIVE or HBD tokens to another Hive account (requires active key).
Sign a message with a Hive private key from environment variables.
Verify a digital signature against a Hive public key.
Encrypt a message for a specific Hive account using memo encryption.
Decrypt an encrypted message from a specific Hive account.
Send an encrypted message to a Hive account via a small token transfer.
Retrieve encrypted messages from account history with optional decryption.