create_comment
Create a comment on an existing Hive post or reply to another comment.
LABSCO SUMMARY
Configuring this makes an agent the account: vote_on_post, create_post and send_token act under the credentials you supply, with no separate confirmation step anywhere in the tool surface.
Reading here is ordinary chain querying; the writing side is where the design decision sits — the acting identity is fixed by configuration rather than passed per call, so whichever account you configure is the account an agent is. The keys are named separately as HIVE_POSTING_KEY, HIVE_ACTIVE_KEY and HIVE_MEMO_KEY, and sign_message takes a key_type, so which key a call reaches for is explicit rather than implied. The encrypted-message tools are the unusual part: send_encrypted_message rides a small token transfer, which makes a conversation here cost a transfer per message and leave one on the account's history.
What it is
A server over the Hive blockchain that pairs read access to accounts, posts, delegations and chain properties with write operations signed by the account whose keys you configure.
What you get
- Account reads: get_account_info returns balance, authority, voting power and other account metrics for a username, get_account_history returns transactions narrowed by operation_filter and limit, and get_vesting_delegations lists the delegations an account has made.
- Post reads by identity, tag or author: get_post_content fetches a post by author and permlink with its title, content and metadata, get_posts_by_tag sorts a tag's posts by a category such as trending, hot or created, and get_posts_by_user returns posts authored by a user or appearing in that user's feed.
- Publishing with the payout terms attached to the call: create_post takes title, body, tags and permalink alongside beneficiaries, max_accepted_payout, percent_hbd, allow_votes and allow_curation_rewards, and create_comment takes the same payout controls plus parent_author and parent_permlink.
- Curation and transfers from the configured account: vote_on_post applies a weight to an author and permlink, and send_token sends HIVE or HBD to an account with a memo.
- Memo encryption used as a message channel: encrypt_message and decrypt_message work against a Hive account, send_encrypted_message delivers one on the back of a small token transfer, and get_encrypted_messages pulls them out of account history with an optional decrypt.
- Signing separate from posting: sign_message signs with the key named by key_type, verify_signature checks a signature against a public_key and message_hash, and get_chain_properties returns current chain properties and statistics.
Requirements
A Hive account and its keys: HIVE_USERNAME, HIVE_POSTING_KEY, HIVE_ACTIVE_KEY and HIVE_MEMO_KEY.
Setup effort
One command — npx -y @gluneau/hive-mcp-server
USE CASES
01
Sizing up a Hive account before you delegate to it or trade with it
Read the account's standing, walk back through what it has actually been doing, and see what it has already committed elsewhere.
02
Publishing a post with its payout terms decided up front
Set the beneficiaries, payout ceiling and reward split as part of the same call that publishes, then read the post back as it now stands on chain.
03
Keeping up with a tag and weighing in where it is worth it
Pull what is moving under the tag, read the piece in full, and respond with a comment and a vote weighted to how much it deserves.
04
Paying someone on Hive and leaving them a note nobody else reads
Send the transfer, then put the part that should not be public into an encrypted memo and read the replies back out of history.
05
Proving a message came from the account it claims to
Sign the text with the key you name, and check a signature you were handed against the public key that is supposed to have produced it.
17 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_post
Create a new blog post on the Hive blockchain using the configured account credentials.
decrypt_message
Decrypt an encrypted message received from a specific Hive account
encrypt_message
Encrypt a message for a specific Hive account using memo encryption
get_account_history
Retrieves transaction history for a Hive account with optional operation type filtering.
get_account_info
Fetches detailed information about a Hive blockchain account including balance, authority, voting power, and other account metrics.
get_chain_properties
Fetch current Hive blockchain properties and statistics
get_encrypted_messages
Retrieve encrypted messages from account history with optional decryption
get_post_content
Retrieves a specific Hive blog post identified by author and permlink, including the post title, content, and metadata.
get_posts_by_tag
Retrieves Hive posts filtered by a specific tag and sorted by a category like trending, hot, or created.
get_posts_by_user
Retrieves posts authored by or in the feed of a specific Hive user.
get_vesting_delegations
Get a list of vesting delegations made by a specific Hive account
send_encrypted_message
Send an encrypted message to a Hive account using a small token transfer
send_token
Send HIVE or HBD tokens to another Hive account using the configured account credentials.
sign_message
Sign a message using a Hive private key from environment variables.
verify_signature
Verify a digital signature against a Hive public key
vote_on_post
Vote on a Hive post (upvote or downvote) using the configured Hive account.
BEFORE YOU INSTALL
What to know first
Tools you get
17 tools when we connected. Seven read tools need no key; vote_on_post, create_post and create_comment need a posting key, send_token needs an active key, and the four encrypted-messaging tools need HIVE_MEMO_KEY. create-post and analyze-account are prompts.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 17 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @gluneau/hive-mcp-serverMCP Clients
Claude Desktop, Windsurf, Cursor
JSON
{
"mcpServers": {
"hive": {
"command": "npx",
"args": [
"-y",
"@gluneau/hive-mcp-server"
],
"env": {
"HIVE_USERNAME": "<YOUR_HIVE_USERNAME>",
"HIVE_POSTING_KEY": "<YOUR_HIVE_POSTING_KEY>",
"HIVE_ACTIVE_KEY": "<YOUR_HIVE_ACTIVE_KEY>",
"HIVE_MEMO_KEY": "<YOUR_HIVE_MEMO_KEY>"
}
}
}
}
