Skip to main content
Glama
Siddhant-K-code

Apple Notes MCP Server

create-note

Create new notes in Apple Notes with title, content, and optional tags using natural language commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYes
tagsNo

Implementation Reference

  • MCP tool handler for 'create-note': calls AppleNotesManager.createNote and returns formatted success or error response.
    async ({ title, content, tags = [] }: CreateNoteParams) => {
      try {
        const note = notesManager.createNote(title, content, tags);
        if (!note) {
          return {
            content: [{
              type: "text",
              text: "Failed to create note. Please check your Apple Notes configuration."
            }],
            isError: true
          };
        }
    
        return {
          content: [{
            type: "text",
            text: `✅ Note created successfully: "${note.title}"`
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error creating note: ${error instanceof Error ? error.message : 'Unknown error'}`
          }],
          isError: true
        };
      }
    }
  • Input schema for 'create-note' tool using Zod validators.
    const createNoteSchema = {
      title: z.string().min(1, "Title is required"),
      content: z.string().min(1, "Content is required"),
      tags: z.array(z.string()).optional()
    };
  • src/index.ts:34-65 (registration)
    Registration of the 'create-note' tool on the MCP server.
      "create-note",
      createNoteSchema,
      async ({ title, content, tags = [] }: CreateNoteParams) => {
        try {
          const note = notesManager.createNote(title, content, tags);
          if (!note) {
            return {
              content: [{
                type: "text",
                text: "Failed to create note. Please check your Apple Notes configuration."
              }],
              isError: true
            };
          }
    
          return {
            content: [{
              type: "text",
              text: `✅ Note created successfully: "${note.title}"`
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error creating note: ${error instanceof Error ? error.message : 'Unknown error'}`
            }],
            isError: true
          };
        }
      }
    );
  • Core helper method in AppleNotesManager that executes AppleScript to create the note in Apple Notes app.
    createNote(title: string, content: string, tags: string[] = []): Note | null {
      const formattedContent = formatContent(content);
      const script = `
        tell application "Notes"
          tell account "${this.ICLOUD_ACCOUNT}"
            make new note with properties {name:"${title}", body:"${formattedContent}"}
          end tell
        end tell
      `;
    
      const result = runAppleScript(script);
      if (!result.success) {
        console.error('Failed to create note:', result.error);
        return null;
      }
    
      return {
        id: Date.now().toString(),
        title,
        content,
        tags,
        created: new Date(),
        modified: new Date()
      };
    }
  • Helper function to format note content for AppleScript compatibility.
    const formatContent = (content: string): string => {
      if (!content) return '';
    
      // Define replacement patterns for text formatting
      const replacements: [string, RegExp][] = [
        ['\n', /\n/g],
        ['\t', /\t/g],
        ['"', /"/g], // Escape quotes for AppleScript
      ];
    
      return replacements.reduce(
        (text, [char, pattern]) => text.replace(pattern, char === '"' ? '\\"' : '<br>'),
        content
      );
    };
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.

Install Server

Other Tools

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/Siddhant-K-code/mcp-apple-notes'

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