Beemcp MCP Server

A Model Context Protocol (MCP) server for Bee.computer lifelogging data (unofficial)

Local serverstdioPython

What is the Beemcp MCP server?

Most developer tooling work still happens through a UI a human drives. Beemcp MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server for Bee.computer lifelogging data (unofficial).

The short version

This server acts as a bridge, allowing Large Language Models (LLMs) like Claude or custom AI agents to access and interact with your personal data stored in Bee, including conversations, facts, to-dos, and location history.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • Conversations — The Conversations tool exposed by this server
  • Facts — The Facts tool exposed by this server
  • Locations — Some of these convenience functions are redundant but are added to make usage with current large language models more practical

Getting it running

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: BEE_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  1. Python: Version 3.10 or higher. 2. Bee.computer API Key: You need an API key from your Bee account settings.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Beemcp's toolset — Conversations, Facts, Locations — is a fair guide to whether it matches your workflow.

This entry was verified against Beemcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ConversationsThe Conversations tool exposed by this server.
FactsThe Facts tool exposed by this server.
LocationsSome of these convenience functions are redundant but are added to make usage with current large language models more practical

How to install the Beemcp MCP server

{
  "mcpServers": {
    "beemcp": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "BEE_API_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  1. Python: Version 3.10 or higher. 2. Bee.computer API Key: You need an API key from your Bee account settings.
VariableDescriptionRequired
BEE_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Beemcp to Conversations.
  • Use Beemcp to Facts.
  • Use Beemcp to Locations.

Frequently asked questions

It connects Beemcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Conversations, Facts, Locations) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Beemcp directly.