モデルコンテキストプロトコル(MCP)用のAppleネイティブツールのPython実装で、macOSアプリケーションとのシームレスな統合を実現します。

同じ統合に2つのフロントエンドがあります:Claude用のMCPサーバー デスクトップとその他のMCPクライアント、および[pyapple]、同じ運転のためのコマンドライン シェルから10個のツール。 彼らは1つの許可ポリシーを共有しているので、許可されているもの どちらも許可されているもの。

10つのツールを渡る88の操作 これらは、以下に記載されています ツールとそれらを拒否するツールは、下にあります 知っておく価値を制限する — 知っておく前に、 それら。

それを読んでいる人ではなく、CLIを運転するためのエージェントなら、 このリポジトリの[.claude/skills/pyapple/SKILL.mdは、オペレータガイドです。 最初に、出口の状態を読む方法、およびルートへの拒否の呼び出し 対談レポート

##特徴

-メッセージ:会話を見つけ、スレッド全体を読み、メッセージのテキストを検索します。 スレッドが送信されたものをリスト化し、テキストやファイルを送信します。 読書は通る [[chat.db] は直接、chat によってスコープ付けられているので、グループスレッドは次のように戻ってくる 参加者の共有ではなくグループ

PyApple MCP Tools

A Python implementation of Apple-native tools for the Model Context Protocol (MCP), providing seamless integration with macOS applications.

There are two front ends over the same integrations: an MCP server for Claude Desktop and other MCP clients, and pyapple, a command line for driving the same ten tools from a shell. They share one permission policy, so what you allow in one you have allowed in both.

88 operations across ten tools. They are listed in full under The tools, and what they refuse to do is under Limits worth knowing — read that before you rely on any of them.

If you are an agent about to drive the CLI rather than a person reading about it, .claude/skills/pyapple/SKILL.md in this repository is the operator guide: which call to make first, how to read the exit status, and which refusals to route around versus report.

Features

• Messages: find conversations, read a thread whole, search message text, list what a thread was sent, and send — text or a file. Reads go through chat.db directly and are scoped by chat, so a group thread comes back as the group rather than as one participant’s share
• Notes: search, list, read, create, append, rename and rewrite — with a gate that refuses any note whose content a round trip would destroy — plus filing a note into another folder, and folders themselves: list them, create one, rename one, delete one. create refuses a folder name that does not exist rather than making a folder out of a typo, and the listing is how you find out what does; folder-delete refuses a folder holding notes unless you pass their exact count, because what it deletes does not go to Recently Deleted
• Contacts: search by name, go the other way from a number or address to a person, and add, correct or delete a card. Reads and writes both go through the Contacts framework; nothing launches Contacts.app
• Mail: unread, header search, body search, read one message whole by id, a whole thread in order, what is attached and whether the bytes are here, coverage — what each account can actually answer about — send, reply, forward, the drafted form of each of those three, mark read, file, delete, and list mailboxes and accounts. Reads come from the local Envelope Index rather than through the app
• Reminders: list, search, create, update, complete, uncomplete and delete, plus creating and deleting the lists themselves, through EventKit