Skip to main content
Glama
Rish-it
by Rish-it

NotesY - Apple Notes Integration for Claude

A Claude MCP integration that allows seamless interaction with Apple Notes through natural language.

Features

  • Create notes with content and titles

  • Update existing notes with new content

  • Delete notes by title

  • Search for notes containing specific text

  • Automatically detect trip planning requests and create notes

Related MCP server: Notes MCP

Installation

  1. Clone and build the project:

git clone https://github.com/yourusername/NotesY.git
cd NotesY
npm install
npm run build
  1. Add to Claude's configuration (usually at ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "NotesY": {
      "command": "node",
      "args": ["/absolute/path/to/NotesY/dist/index.js"]
    }
  }
}

Usage

With Claude Desktop

Simply talk to Claude Desktop and ask it to:

Create a note titled 'shopping list' with items: milk, eggs, bread

Add meeting notes to my 'work' note

Delete my 'old tasks' note

Search for notes with 'project'

You can also just give Claude long text and it will create a note with appropriate title:

Create a comprehensive trip plan for Krabi, Thailand, including recommended duration, best time to visit, must-see attractions, accommodation options, transportation tips, food recommendations, and budget considerations.

Using the CLI

For testing without Claude, you can use the built-in CLI:

npm run cli

This lets you enter natural language commands directly and see the results.

Local Development

git clone https://github.com/yourusername/NotesY.git
cd NotesY
npm install
npm run build
npm run dev

To run the Express server for API testing:

START_EXPRESS_SERVER=true npm run dev

How it Works

NotesY uses AppleScript to interact with the macOS Notes app, providing natural language understanding through an MCP integration with Claude Desktop.

Available Tools

1 tool
process_note_requestD
ParametersJSON Schema
NameRequiredDescriptionDefault
textYes

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.

  1. 1 tool update
    • First observedprocess_note_request

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is inherently distinct by default in this minimal set.

Naming Consistency5/5

The single tool name 'process_note_request' follows a clear verb_noun pattern, and since there are no other tools, consistency is trivially perfect with no deviations to assess.

Tool Count2/5

A single tool is too few for a server named 'NotesY', which suggests a domain involving notes management. This minimal count likely leaves significant gaps in functionality, such as creating, retrieving, updating, or deleting notes, making it inappropriate for the implied scope.

Completeness1/5

The server appears to target note management, but with only one generic tool ('process_note_request') and no description, the surface is severely incomplete. It lacks basic CRUD operations and any clear lifecycle coverage, making it inadequate for the domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables AI assistants like Claude to access and manipulate Apple Notes on macOS, allowing for retrieving, creating, and managing notes through natural language interactions.
    82
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Enables seamless interaction with Voicenotes through natural language, allowing users to search, create, edit, tag, and organize their notes via an MCP client like Claude.
    14
    4
    -

Latest Blog Posts

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/Rish-it/Notes-MCP'

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