bear-mcp
MCP server that gives LLMs fast, read-only access to your Bear notes by reading the SQLite database directly.
How it works
Bear stores notes in a Core Data SQLite file on disk. This server opens it read-only (?mode=ro) and queries it directly. No network calls, no CloudKit sync latency, no API keys. Queries against the tag index instead of scanning note content.
Why this exists
The existing Bear MCP options either go through Bear's x-callback-url scheme (slow, requires Bear to be running, macOS UI automation) or the akseyh implementation that builds SQL with string concatenation. I wanted something that's fast, read-only by design, and doesn't have SQL injection issues.
Limitations:
- macOS only — Bear is a macOS/iOS app, the SQLite file lives on macOS
- Read-only — this server cannot create, edit, or delete notes
- Needs Full Disk Access — the process reading Bear's database needs FDA granted in System Settings > Privacy & Security
Install
pip install git+https://github.com/mark-liu/bear-mcp.git
Or run without installing:
uvx --from git+https://github.com/mark-liu/bear-mcp.git bear-mcp
PyPI coming soon — pip install bear-mcp once published.
Configure in Claude Code
claude mcp add bear -s user -- uvx --from git+https://github.com/mark-liu/bear-mcp.git bear-mcp
Tools
| Tool | Description |
|---|---|
search_bear_notes |
Search notes by text and/or tag (uses tag index, not text scan) |
get_bear_note |
Get a specific note by UUID |
list_bear_tags |
List all tags (reads ZSFNOTETAG table directly) |
find_notes_by_title |
Find notes by title, exact or partial match |
get_recent_notes |
Get notes modified in the last N days |
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for bear-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bear_mcp-0.2.0.tar.gz | 4.8 kB | With provenance | Details for bear_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bear_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for bear_mcp-0.2.0-py3-none-any.whl |
Total release size: 10.3 kB
Release files / bear_mcp-0.2.0.tar.gz
| Download URL | bear_mcp-0.2.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ee1d01b5acc8a2eaa6b807ac63b841f775ce543be59902d73698096187d76b1
|
|
BLAKE2b-256 checksum How to use checksums |
1bce7857ec47ebcafae0537800701b2c223407ca44a4397dcde8550250eee86b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logRelease files / bear_mcp-0.2.0-py3-none-any.whl
| Download URL | bear_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b700f16e5b920418cfafc73ed63fc771f0c749993ffb1295f9e066f8b9c6b127
|
|
BLAKE2b-256 checksum How to use checksums |
ebf18bf13ad2caf1e39243f3fb5491207790a38ba3dfc5dc2861984e8d3714de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logSecurity for bear-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bear_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
