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] No se mantiene activamente. ¡Úselo bajo su propia responsabilidad!

📝 Servidor MCP de Notas de Apple

Servidor MCP de Notas de Apple es un servidor del Protocolo de Contexto de Modelo (MCP) que permite una interacción fluida con Notas de Apple mediante lenguaje natural. ¡Cree, busque y recupere notas sin esfuerzo usando Claude u otros asistentes de IA! 🎉

🎯 Características

Crear notas: Cree rápidamente nuevas notas con títulos, contenido y etiquetas 📝
Buscar notas: Encuentre notas usando potentes capacidades de búsqueda 🔍
Recuperar contenido: Obtenga el contenido completo de cualquier nota por su título 📖
Integración con iCloud: Funciona directamente con su cuenta de Notas de iCloud ☁️

Related MCP server: Apple Notes MCP Server

🚀 Primeros pasos

Requisitos previos

macOS con la aplicación Notas de Apple configurada
Node.js (versión 20.0.0 o superior)
Gestor de paquetes Yarn

Instalación

Clone el repositorio:

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

Instale las dependencias:
```
yarn install
```
Compile el proyecto:
```
yarn build
```
Inicie el servidor:
```
yarn start
```
Configure Claude Desktop. Actualice su claude_desktop_config.json con:
```
{
  "mcpServers": {
    "apple-notes": {
      "command": "yarn",
      "args": ["start"],
      "cwd": "/path/to/mcp-apple-notes"
    }
  }
}
```
Nota: Reemplace /path/to/mcp-apple-notes con la ruta real a su repositorio clonado. Es posible que deba autorizar al script para acceder a Notas de Apple al ejecutar comandos por primera vez.

Inicialización del servidor MCP

Cuando el servidor se inicie correctamente, verá:

Starting Apple Notes MCP server.

¡El servidor ya está listo para gestionar sus operaciones de notas! 🎉

🛠️ Uso

Herramientas disponibles

Crear nota

Descripción: Crea una nueva nota en Notas de Apple

Parámetros:

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

Respuesta de ejemplo:
```
Note created: My New Note
```

Buscar notas

Descripción: Busca notas por título

Parámetros:

{
  query: string; // The search query
}

Respuesta de ejemplo:

Meeting Notes
Shopping List
Ideas for Project

Obtener contenido de la nota
- Descripción: Recupera el contenido completo de una nota específica
- Parámetros:
  { title: string; // The exact title of the note }
- Respuesta de ejemplo:
  [Full content of the note]

📚 Casos de uso de ejemplo

1. Toma de notas rápida

Cree notas durante reuniones o sesiones de lluvia de ideas:

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

2. Recuperación de información

Busque notas específicas cuando las necesite:

{
"query": "meeting"
}

3. Revisión de contenido

Obtenga el contenido completo de una nota específica:

{
"title": "Team Meeting Notes"
}

⚡ Consejos para obtener los mejores resultados

Asegúrese de que su aplicación Notas de Apple esté configurada correctamente con iCloud
Use títulos descriptivos para una mejor capacidad de búsqueda
Incluya etiquetas relevantes al crear notas para una mejor organización

🔧 Desarrollo

El proyecto utiliza TypeScript y sigue patrones modernos de módulos ES. Archivos clave:

src/index.ts: Implementación principal del servidor
src/services/appleNotesManager.ts: Funcionalidad principal de gestión de notas
src/utils/applescript.ts: Utilidades de integración con AppleScript

Contenedor de desarrollo

Se proporciona una configuración de contenedor de desarrollo para usuarios de VS Code, que ofrece:

Entorno Node.js con TypeScript
Prettier para el formato de código
Instalación automática de dependencias

📄 Licencia

Este proyecto está bajo la Licencia MIT; consulte el archivo LICENSE para obtener más detalles.

Hecho con ❤️ para los usuarios de Notas de Apple

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

📝 Servidor MCP de Notas de Apple

🎯 Características

🚀 Primeros pasos

Requisitos previos

Instalación

Inicialización del servidor MCP

🛠️ Uso

Herramientas disponibles

📚 Casos de uso de ejemplo

1. Toma de notas rápida

2. Recuperación de información

3. Revisión de contenido

⚡ Consejos para obtener los mejores resultados

🔧 Desarrollo

Contenedor de desarrollo

📄 Licencia

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches