TaskNote Bridge - Swift MCP Server with Things 3 & Apple Notes ✅

Created By
ragdollKBa year ago
TaskNote Bridge - MCP Server for Things 3 and Apple Notes integration
Overview

What is TaskNote Bridge?

TaskNote Bridge is a native macOS application that serves as a Model Context Protocol (MCP) server, enabling integration between Things 3 and Apple Notes.

How to use TaskNote Bridge?

To use TaskNote Bridge, download the latest release, install it on your macOS, and launch the application. Configure your MCP-compatible tools like VS Code or Claude Desktop to connect to the server.

Key features of TaskNote Bridge?

  • Complete MCP server implementation for Things 3 and Apple Notes.
  • Real-time monitoring dashboard for server activity.
  • TCP transport protocol for universal client compatibility.
  • Live log streaming and connection management.
  • SwiftUI interface for easy server control.

Use cases of TaskNote Bridge?

  1. Create and manage tasks in Things 3 using natural language commands.
  2. Organize and retrieve notes in Apple Notes seamlessly.
  3. Monitor server activity and manage connections in real-time.

FAQ from TaskNote Bridge?

  • Can I use TaskNote Bridge with any MCP-compatible tool?
    Yes! TaskNote Bridge is designed to work with any MCP-compatible application or AI assistant.

  • Is TaskNote Bridge free to use?
    Yes! TaskNote Bridge is free to download and use.

  • What are the system requirements?
    TaskNote Bridge requires macOS 12.0 or later, along with Things 3 and Apple Notes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ragdollKB
Star
1
Language
Swift
License
View license

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)

6 hours ago