mcp-server-bear

Created By
Ssiswenta year ago
MCP server for Bear note-taking app
Overview

what is Mcp Server Bear?

Mcp Server Bear is a server that integrates with the Bear API, allowing users to create notes in Bear through conversation with any MCP client.

how to use Mcp Server Bear?

To use Mcp Server Bear, configure it with your preferred MCP client (like Cursor AI, Claude, or OpenAI) and interact with it to create or manage notes in Bear.

key features of Mcp Server Bear?

  • Create Bear notes through conversation with MCP clients.
  • Open and search existing notes in Bear.
  • Support for Markdown formatted note content.
  • Ability to add tags to notes.

use cases of Mcp Server Bear?

  1. Recording meeting notes through voice commands.
  2. Saving code snippets directly into Bear notes.
  3. Searching for specific notes related to projects.
  4. Opening the latest notes in Bear with simple commands.

FAQ from Mcp Server Bear?

  • What systems are required to run Mcp Server Bear?

It requires macOS and the Bear application installed.

  • How do I install Mcp Server Bear?

You can install it using npx, globally via npm, or from source.

  • Can I use Mcp Server Bear with any MCP client?

Yes, it is compatible with various MCP clients like Cursor AI and Claude.

Server Config

{
  "mcpServers": {
    "mcp-server-bear": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-bear"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Ssiswent
Star
0
Language
JavaScript
License
MIT license
Category
note-taking
Tags

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)

2 days ago