Skip to main content
MCP is a Kimi Code CLI feature. The Kimi chatbot at kimi.com has no connector surface, so this page is the way to use Hive with Kimi.

Add the server

kimi mcp auth opens a browser. Approve the connection there and Kimi stores the credential outside your config file, so no secret goes on disk.

Headless use

Where no browser is available, pass a key in the header instead:
See authentication for where to get a key.

Check it works

hive should appear as connected. Then start a session. Kimi Code CLI keeps its servers in ~/.kimi-code/mcp.json under mcpServers, or in .kimi-code/mcp.json in the working directory for a project-scoped server.
  1. Ask your client: “What Hive tools do you have?” Expect nine: find_token, get_token_price, check_token_safety, research_token, analyze_wallet, market_positioning, market_overview, defi_yields and prediction_markets. An empty list means the connection or sign-in failed. Go back to the sign-in step on this page.
  2. Ask: “Is PEPE on Ethereum safe to buy, and what is it worth?”
  3. Confirm the answer names GoPlus and CoinGecko with a fetch time. An answer with no source came from the model’s memory, not from Hive.