Bear MCP Server

Created By
jkawamotoa year ago
A MCP server for interacting with Bear note-taking software.
Overview

What is Bear MCP Server?

Bear MCP Server is a server application designed to interact with Bear note-taking software, allowing users to perform various actions through a model context protocol.

How to use Bear MCP Server?

To use Bear MCP Server, configure it with your Bear API token and set it up in either Claude Desktop or Goose CLI by editing the respective configuration files. You can also install it automatically via Smithery.

Key features of Bear MCP Server?

  • Supports multiple actions like opening notes, creating new notes, and searching notes.
  • Integration with Bear's X-callback-url scheme for seamless interaction.
  • Easy installation and configuration for different platforms.

Use cases of Bear MCP Server?

  1. Automating note-taking tasks in Bear.
  2. Integrating Bear with other applications using the MCP protocol.
  3. Enhancing productivity by managing notes through command-line interfaces.

FAQ from Bear MCP Server?

  • Is Bear MCP Server free to use?

Yes! Bear MCP Server is free to use and open-source.

  • What platforms does Bear MCP Server support?

It supports Claude Desktop and Goose CLI, among others.

  • How do I get my Bear API token?

You can obtain your Bear API token from the Bear app settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jkawamoto
Star
10
Language
Python
License
MIT license
Category
note-taking

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago