Skip to main content
Glama
Siddhant-K-code

Apple Notes MCP Server

get-note-content

Retrieve content from Apple Notes by specifying a note title, enabling quick access to stored information through the Apple Notes MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes

Implementation Reference

  • Core handler logic for retrieving note content via AppleScript execution on Apple Notes app.
    getNoteContent(title: string): string {
      const sanitizedTitle = title.replace(/"/g, '\\"');
      const script = `
        tell application "Notes"
          tell account "${this.ICLOUD_ACCOUNT}"
            get body of note "${sanitizedTitle}"
          end tell
        end tell
      `;
    
      const result = runAppleScript(script);
      if (!result.success) {
        console.error('Failed to get note content:', result.error);
        return '';
      }
    
      return result.output;
    }
  • src/index.ts:95-117 (registration)
    Registers the 'get-note-content' tool with the MCP server, providing schema and thin wrapper handler that delegates to AppleNotesManager.
    server.tool(
      "get-note-content",
      getNoteSchema,
      async ({ title }: GetNoteParams) => {
        try {
          const content = notesManager.getNoteContent(title);
          return {
            content: [{
              type: "text",
              text: content || "Note not found"
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error retrieving note content: ${error instanceof Error ? error.message : 'Unknown error'}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod schema for validating input parameters (title) of the get-note-content tool.
    const getNoteSchema = {
      title: z.string().min(1, "Note title is required")
    };
  • TypeScript interface defining the input parameters for the get-note-content tool handler.
    export interface GetNoteParams {
      title: string;
    }
  • Utility function that executes AppleScript commands using osascript, used by the note content retrieval logic.
    export function runAppleScript(script: string): AppleScriptResult {
      try {
        // Trim and sanitize the script
        const sanitizedScript = script.trim().replace(/[\r\n]+/g, ' ');
    
        // Execute the AppleScript command
        const output = execSync(`osascript -e '${sanitizedScript}'`, {
          encoding: 'utf8',
          timeout: 10000 // 10 second timeout
        });
    
        return {
          success: true,
          output: output.trim()
        };
      } catch (error) {
        console.error('AppleScript execution failed:', error);
    
        return {
          success: false,
          output: '',
          error: error instanceof Error
            ? error.message
            : 'Unknown error occurred while executing AppleScript'
        };
      }
    }
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