Rook

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.

What are the runtime requirements?

Requires Rook to be installed from userook.app. The server binary is bundled inside the Rook app and must be run from that location.

Where does the data from append_to_inbox go?

Data is sent to the Rook app via the app-group entitlement, where it is saved as notes within Rook.

Are there any known limits?

The README does not mention limits beyond the requirement for the Rook app to be installed and the standalone build restriction.

What transport and authentication does Rook use?

Rook uses stdio JSON-RPC 2.0 transport. No authentication is described; it relies on local file system access.