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 Related Servers Score Discussions

TypeScript

Local

[!Caution] Активно не поддерживается. Используйте на свой страх и риск!

📝 MCP-сервер Apple Notes

MCP-сервер Apple Notes — это сервер протокола Model Context Protocol, который обеспечивает беспрепятственное взаимодействие с Apple Notes с помощью естественного языка. Создавайте, ищите и извлекайте заметки без усилий с помощью Claude или других ИИ-ассистентов! 🎉

🎯 Функции

Создание заметок: Быстрое создание новых заметок с заголовками, содержимым и тегами 📝
Поиск заметок: Поиск заметок с помощью мощных возможностей поиска 🔍
Извлечение содержимого: Получение полного содержимого любой заметки по её заголовку 📖
Интеграция с iCloud: Работает напрямую с вашей учетной записью iCloud Notes ☁️

Related MCP server: Apple Notes MCP Server

🚀 Начало работы

Предварительные требования

macOS с настроенным приложением Apple Notes
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. Dates show when Glama detected each change.

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

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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
memolOAuth
app.memol
Search, read, create and edit your Memol notes from Claude. Team note-taking with AI search.
Note Taking Search
2
aNotepadOAuth
com.anotepad
AI access to your aNotepad online notes: read, search, write, and organize via 22 tools.
Note Taking Cloud Storage 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 9 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
433
27
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
433
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)
433
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Siddhant-K-code/mcp-apple-notes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server