Mcp Bear
Let your coding agent read and write Bear notes on macOS through a token-authenticated MCP server.
Overview
io.github.jkawamoto/mcp-bear is a MCP server for the Build phase that connects coding agents to Bear note-taking with a required API token.
What is this MCP server?
- MCP server v0.5.2 for Bear note-taking via mcpb release bundle
- Requires BEAR_API_TOKEN secret environment variable for authenticated access
- stdio transport through published mcpb identifier on GitHub releases
- Enables agents to search, create, or manage Bear notes without leaving the IDE
- Server version 0.5.2
- 1 required secret env var: BEAR_API_TOKEN
- mcpb release with documented fileSha256 on package entry
Community signal: 70 GitHub stars.
What problem does it solve?
Your specs and research sit in Bear while your agent works in the terminal, forcing manual copy-paste between note tags and code sessions.
Who is it for?
macOS solo builders who standardize on Bear and want Claude Code or Cursor to reference and update those notes in flow.
Skip if: Windows/Linux-only workflows, teams on Notion or Obsidian without Bear, or builders unwilling to manage Bear API tokens.
What do I get? / Deliverables
With BEAR_API_TOKEN configured and mcp-bear registered, agents can operate on Bear notes as MCP tools during development.
- Authenticated Bear MCP bridge in your agent stack
- Tool calls that list, search, or mutate Bear notes from the IDE
- Reduced context switching between Bear tags and implementation work
Recommended MCP Servers
Journey fit
Bear MCP connects a personal knowledge app into the dev environment, which solo builders set up during Build as agent-tooling and integrations. The server’s sole purpose is bridging Bear’s API—integration work, not shipping tests or launch SEO.
How it compares
Bear-specific notes MCP—not a generic filesystem skill or cloud document browser automation.
Common Questions / FAQ
Who is io.github.jkawamoto/mcp-bear for?
Solo developers on macOS who use Bear as their primary notes app and MCP-based coding agents daily.
When should I use io.github.jkawamoto/mcp-bear?
During Build when you want agent-tooling that reads project notes, todos, or specs stored in Bear without context switching.
How do I add io.github.jkawamoto/mcp-bear to my agent?
Download the v0.5.2 mcpb from jkawamoto/mcp-bear releases, set BEAR_API_TOKEN in your MCP server env, point your client at the mcpb stdio server, and restart the host.