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