de en es ja ko ru zh

Apple Notes MCP Server

Name: Apple Notes MCP Server
Author: Siddhant-K-code

by Siddhant-K-code

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

[!Caution] 現在メンテナンスされていません。自己責任で使用してください！

📝 Apple Notes MCPサーバー

Apple Notes MCPサーバーは、Apple Notesとのシームレスな対話を自然言語で可能にするModel Context Protocolサーバーです。Claudeやその他のAIアシスタントを使用して、メモの作成、検索、取得を簡単に行えます！ 🎉

🎯 機能

メモの作成: タイトル、コンテンツ、タグを指定して新しいメモを素早く作成 📝
メモの検索: 強力な検索機能を使用してメモを検索 🔍
コンテンツの取得: タイトルを指定してメモの全内容を取得 📖
iCloud連携: iCloudのメモアカウントと直接連携 ☁️

Related MCP server: Apple Notes MCP Server

🚀 はじめに

前提条件

Apple Notesアプリが設定されたmacOS
Node.js (バージョン20.0.0以上)
Yarnパッケージマネージャー

インストール

リポジトリをクローンします:

git clone https://github.com/Siddhant-K-code/mcp-apple-notes.git
cd mcp-apple-notes

依存関係をインストールします:
```
yarn install
```
プロジェクトをビルドします:
```
yarn build
```
サーバーを起動します:
```
yarn start
```
Claude Desktopを設定します。claude_desktop_config.jsonを以下のように更新してください:
```
{
  "mcpServers": {
    "apple-notes": {
      "command": "yarn",
      "args": ["start"],
      "cwd": "/path/to/mcp-apple-notes"
    }
  }
}
```
注意: /path/to/mcp-apple-notes は、クローンしたリポジトリの実際のパスに置き換えてください。初回実行時に、スクリプトがApple Notesにアクセスするための許可を求められる場合があります。

MCPサーバーの初期化

サーバーが正常に起動すると、以下のように表示されます:

Starting Apple Notes MCP server.

これで、サーバーはメモ操作を処理する準備が整いました！ 🎉

🛠️ 使用方法

利用可能なツール

Create Note (メモの作成)

説明: Apple Notesに新しいメモを作成します

パラメータ:

{
  title: string;      // The title of the note
  content: string;    // The content of the note
  tags?: string[];    // Optional tags for the note
}

レスポンス例:
```
Note created: My New Note
```

Search Notes (メモの検索)
- 説明: タイトルでメモを検索します
- パラメータ:
  { query: string; // The search query }
- レスポンス例:
  Meeting Notes Shopping List Ideas for Project
Get Note Content (メモの内容取得)
- 説明: 特定のメモの全内容を取得します
- パラメータ:
  { title: string; // The exact title of the note }
- レスポンス例:
  [Full content of the note]

📚 使用例

1. クイックメモ

会議中やブレインストーミング中にメモを作成します:

{
"title": "Team Meeting Notes",
"content": "Discussion points:\n1. Project timeline\n2. Resource allocation",
"tags": ["meetings", "work"]
}

2. 情報の取得

必要なときに特定のメモを検索します:

{
"query": "meeting"
}

3. コンテンツの確認

特定のメモの全内容を取得します:

{
"title": "Team Meeting Notes"
}

⚡ 最良の結果を得るためのヒント

Apple NotesアプリがiCloudで適切に設定されていることを確認してください
検索性を高めるために、わかりやすいタイトルを使用してください
整理しやすくするために、メモ作成時に適切なタグを含めてください

🔧 開発

このプロジェクトはTypeScriptを使用し、最新のESモジュールパターンに従っています。主要なファイル:

src/index.ts: サーバーのメイン実装
src/services/appleNotesManager.ts: メモ管理のコア機能
src/utils/applescript.ts: AppleScript連携ユーティリティ

開発コンテナ

VS Codeユーザー向けに開発コンテナ設定が提供されており、以下が利用可能です:

TypeScript Node.js環境
コードフォーマット用のPrettier
自動依存関係インストール

📄 ライセンス

このプロジェクトはMITライセンスの下でライセンスされています。詳細はLICENSEファイルを参照してください。

Apple Notesユーザーのために❤️を込めて作成

Available Tools

3 tools

create-noteD

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes
`content`	Yes
`tags`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-note-contentD

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search-notesD

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 18, 2025
- First observedcreate-note
- First observedget-note-content
- First observedsearch-notes

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored 2026-04-18 11:35 across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: create-note for creating new notes, get-note-content for retrieving content of specific notes, and search-notes for finding notes based on criteria. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb-noun pattern using kebab-case (e.g., create-note, get-note-content, search-notes). This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

Tool Count2/5

With only 3 tools, the server feels thin for a notes management domain. Key operations like updating, deleting, or listing notes are missing, which limits the agent's ability to perform full CRUD workflows. The count is too low for the apparent scope of managing Apple Notes.

Completeness2/5

The tool set is severely incomplete for notes management. It lacks update and delete operations, as well as basic listing tools to view all notes. This creates significant gaps that will cause agent failures when trying to modify or manage notes beyond creation and retrieval.

Maintenance

ActivityMaintained

ResponsivenessUnresponsive

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

notesbridgeOAuth
io.github.IsaiahDupree
Search, read, and write your Apple Notes from ChatGPT/Claude via a local Mac agent + MCP relay.
Note Taking App Automation
1
xNotepad AI
com.xnotepadai
Create, search, and update notes in an xNotepad AI notebook, with semantic search and AI Q&A.
Note Taking AI & Machine Learning Knowledge & Memory
1
Stipp AOAuth
app.stipp
Notes and actions in one app. Let Claude or ChatGPT read and update them.
91
memolOAuth
app.memol
Search, read, create and edit your Memol notes from Claude. Team note-taking with AI search.
Note Taking Search
2

Related MCP Servers

Apple Notes MCP Server
Note Taking OS Automation App Automation
arslankhanali
F
license
A
quality
D
maintenance
Enables interaction with Apple Notes on macOS through AppleScript, allowing users to list, search, read, create, update, and delete notes across accounts and folders.
Updated 10 months ago (2025-12-03 01:22 UTC)
7
1
-
Apple Notes MCP Server
Note Taking Knowledge & Memory
RodriguesJohn
A
license
A
quality
D
maintenance
Enables AI assistants to read, create, search, update, and delete Apple Notes through natural language conversation, using JXA to communicate directly with the Notes app.
Updated 6 months ago (2026-03-20 17:57 UTC)
8
3,611 npm
28
MIT
Apple Notes MCP
Note Taking Workplace & Productivity
taylorarndt
A
license
A
quality
D
maintenance
Enables AI clients to search, read, create, update, move, and delete Apple Notes on macOS via AppleScript automation.
Updated 2 months ago (2026-07-18 15:42 UTC)
10
3,611 npm
2
MIT
Apple Notes MCP Server
Note Taking App Automation
bfeeny
A
license
Not graded
quality
D
maintenance
Enables Claude to read, write, search, and manage Apple Notes on macOS via AppleScript automation.
Updated 6 months ago (2026-03-14 07:03 UTC)
3,611 npm
MIT

📝 Apple Notes MCPサーバー

🎯 機能

🚀 はじめに

前提条件

インストール

MCPサーバーの初期化

🛠️ 使用方法

利用可能なツール

📚 使用例

1. クイックメモ

2. 情報の取得

3. コンテンツの確認

⚡ 最良の結果を得るためのヒント

🔧 開発

開発コンテナ

📄 ライセンス

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches