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] Wird nicht aktiv gewartet. Benutzung auf eigene Gefahr!

📝 Apple Notes MCP-Server

Apple Notes MCP-Server ist ein Model Context Protocol-Server, der eine nahtlose Interaktion mit Apple Notes durch natürliche Sprache ermöglicht. Erstellen, suchen und rufen Sie Notizen mühelos mit Claude oder anderen KI-Assistenten ab! 🎉

🎯 Funktionen

Notizen erstellen: Erstellen Sie schnell neue Notizen mit Titeln, Inhalten und Tags 📝
Notizen suchen: Finden Sie Notizen mit leistungsstarken Suchfunktionen 🔍
Inhalte abrufen: Rufen Sie den vollständigen Inhalt jeder Notiz über ihren Titel ab 📖
iCloud-Integration: Funktioniert direkt mit Ihrem iCloud-Notizen-Konto ☁️

Related MCP server: Apple Notes MCP Server

🚀 Erste Schritte

Voraussetzungen

macOS mit konfigurierter Apple Notes-App
Node.js (Version 20.0.0 oder höher)
Yarn-Paketmanager

Installation

Klonen Sie das Repository:

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

Installieren Sie die Abhängigkeiten:
```
yarn install
```
Bauen Sie das Projekt:
```
yarn build
```
Starten Sie den Server:
```
yarn start
```
Konfigurieren Sie Claude Desktop. Aktualisieren Sie Ihre claude_desktop_config.json mit:
```
{
  "mcpServers": {
    "apple-notes": {
      "command": "yarn",
      "args": ["start"],
      "cwd": "/path/to/mcp-apple-notes"
    }
  }
}
```
Hinweis: Ersetzen Sie /path/to/mcp-apple-notes durch den tatsächlichen Pfad zu Ihrem geklonten Repository. Möglicherweise müssen Sie das Skript autorisieren, um beim ersten Ausführen von Befehlen auf Apple Notes zuzugreifen.

MCP-Server-Initialisierung

Wenn der Server erfolgreich startet, sehen Sie:

Starting Apple Notes MCP server.

Der Server ist nun bereit, Ihre Notizvorgänge zu verarbeiten! 🎉

🛠️ Verwendung

Verfügbare Tools

Notiz erstellen

Beschreibung: Erstellt eine neue Notiz in Apple Notes

Parameter:

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

Beispielantwort:
```
Note created: My New Note
```

Notizen suchen
- Beschreibung: Suchen Sie nach Notizen anhand des Titels
- Parameter:
  { query: string; // The search query }
- Beispielantwort:
  Meeting Notes Shopping List Ideas for Project
Notizinhalt abrufen
- Beschreibung: Rufen Sie den vollständigen Inhalt einer bestimmten Notiz ab
- Parameter:
  { title: string; // The exact title of the note }
- Beispielantwort:
  [Full content of the note]

📚 Anwendungsbeispiele

1. Schnelle Notizen machen

Erstellen Sie Notizen während Meetings oder Brainstorming-Sitzungen:

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

2. Informationsabruf

Suchen Sie nach bestimmten Notizen, wenn Sie sie benötigen:

{
"query": "meeting"
}

3. Inhaltsüberprüfung

Rufen Sie den vollständigen Inhalt einer bestimmten Notiz ab:

{
"title": "Team Meeting Notes"
}

⚡ Tipps für beste Ergebnisse

Stellen Sie sicher, dass Ihre Apple Notes-App ordnungsgemäß mit iCloud konfiguriert ist
Verwenden Sie aussagekräftige Titel für eine bessere Durchsuchbarkeit
Fügen Sie beim Erstellen von Notizen relevante Tags für eine bessere Organisation hinzu

🔧 Entwicklung

Das Projekt verwendet TypeScript und folgt modernen ES-Modul-Mustern. Wichtige Dateien:

src/index.ts: Hauptserver-Implementierung
src/services/appleNotesManager.ts: Kernfunktionalität der Notizverwaltung
src/utils/applescript.ts: AppleScript-Integrations-Dienstprogramme

Entwicklungs-Container

Eine Entwicklungs-Container-Konfiguration wird für VS Code-Benutzer bereitgestellt und bietet:

TypeScript Node.js-Umgebung
Prettier für die Code-Formatierung
Automatische Installation von Abhängigkeiten

📄 Lizenz

Dieses Projekt ist unter der MIT-Lizenz lizenziert - siehe die LICENSE-Datei für Details.

Mit ❤️ für Apple Notes-Benutzer gemacht

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-Server

🎯 Funktionen

🚀 Erste Schritte

Voraussetzungen

Installation

MCP-Server-Initialisierung

🛠️ Verwendung

Verfügbare Tools

📚 Anwendungsbeispiele

1. Schnelle Notizen machen

2. Informationsabruf

3. Inhaltsüberprüfung

⚡ Tipps für beste Ergebnisse

🔧 Entwicklung

Entwicklungs-Container

📄 Lizenz

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches