Rook

Name: Rook
Author: maryamtb

@maryamtb

About Rook

Save anything from your AI chats to Rook, the notes app for code. With one tool available: append_to_inbox, each AI client gets their own inbox. Requires Rook to be installed from userook.app.

#notes #productivity #macos #claude #cursor #openclaw #agents #devtools

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "rook": {
      "command": "/Applications/Rook.app/Contents/Helpers/rook-mcp.app/Contents/MacOS/rook-mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Rook?

Rook is an MCP server that saves text from AI chats into Rook, the notes app for code. It integrates with the Rook app via a signed binary using stdio JSON-RPC 2.0. Targeted at developers who want to capture AI-generated notes into Rook.

How to use Rook?

Install Rook from userook.app, then add to your MCP client config with the command path /Applications/Rook.app/Contents/Helpers/rook-mcp.app/Contents/MacOS/rook-mcp. The server provides one tool: append_to_inbox, which accepts title and content parameters.

Key features of Rook

Single MCP tool: append_to_inbox with title and content.
Integrates with Rook, the notes app for code.
Uses stdio JSON-RPC 2.0 protocol.
Signed binary with app-group entitlement for data handoff.
Standalone builds return entitlement_unavailable.

Use cases of Rook

Save AI-generated code snippets directly to Rook.
Capture meeting summaries from chat into a permanent note.
Store debugging steps from AI assistants in Rook for later reference.
Quickly archive chat content with custom titles and descriptions.

FAQ from Rook

How is Rook different from other MCP servers?

Rook is purpose-built for the Rook notes app and uses its native binary with app-group entitlement for seamless data transfer. Standalone builds cannot function due to entitlement checks.