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.
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.
- 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.
A Hive account and its keys: HIVE_USERNAME, HIVE_POSTING_KEY, HIVE_ACTIVE_KEY and HIVE_MEMO_KEY.
One command — npx -y @gluneau/hive-mcp-server