BeeMCP - A Bee MCP Server

What is BeeMCP?

An unofficial Model Context Protocol (MCP) server that bridges Large Language Models (LLMs) like Claude with your Bee wearable lifelogging data. It allows AI assistants to access and interact with personal Bee data including conversations, facts, to-dos, and location history.

How to use BeeMCP?

Install via uvx beemcp or pip install beemcp. Configure your Bee API key as the BEE_API_TOKEN environment variable (or in a .env file). Then add the server to your MCP client (e.g., Claude Desktop or Zed) by specifying the command and API key in the client’s settings.

Key features of BeeMCP

• List, get, create, update, and delete user facts.
• List, get, create, update, and delete to‑dos (reminders).
• List conversations and retrieve full conversation details.
• Query location history by time range (today, week, month, or custom).
• Provides MCP resources for direct data access (e.g., bee://conversations, bee://locations).

Use cases of BeeMCP

• Ask your AI assistant “What did I discuss last week?” and get a summary of conversations.
• Have the assistant remind you of preferences or facts (e.g., “Brad is gluten‑free”).
• Check or add to‑dos and reminders directly through voice or chat.
• Find out where you were at a specific time using location history.
• Automate note‑taking or fact recording from a conversation.

FAQ from BeeMCP

What is BeeMCP and how does it differ from alternatives?

BeeMCP is an unofficial MCP server that gives LLMs read/write access to your Bee lifelogging data. Unlike generic memory tools, it is purpose‑built for the Bee ecosystem and can retrieve conversations, facts, to‑dos, and location history directly from your Bee account.

What are the runtime requirements?

You need Python 3.10 or higher and a valid Bee API key (obtainable from the Bee developer site). No additional databases or external services are required; the server communicates with Bee’s API.

Where does my personal data live?

All data remains in your Bee.computer account. BeeMCP only accesses it through Bee’s API using your API key. The server never stores data locally beyond transient in‑memory processing during a session.

What are the known limitations?

BeeMCP is an unofficial project not affiliated with Bee. Use it at your own risk. The server requires an active internet connection to reach Bee’s API, and the API key must be kept secret to prevent unauthorized data access.

How do I configure the API key?

Set the BEE_API_TOKEN environment variable (e.g., in your shell or MCP client configuration) or create a .env file in the run directory with BEE_API_TOKEN="your_key_here". The server will exit if the key is not found.