Skip to main content
Glama
bscott

NotePlan MCP Server

by bscott

update_note

Modify existing notes in NotePlan by updating their title and content using the note ID. This tool helps users edit and maintain their notes directly from Claude conversations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the note to update
titleNoNew title for the note
contentNoNew content for the note

Implementation Reference

  • src/index.ts:133-155 (registration)
    Registers the MCP tool 'update_note' with Zod input schema (id required, title/content optional) and handler function that constructs updates object and calls noteService.updateNote, returning JSON stringified response.
    server.tool(
      'update_note',
      {
        id: z.string().describe('The ID of the note to update'),
        title: z.string().optional().describe('New title for the note'),
        content: z.string().optional().describe('New content for the note'),
      },
      async ({ id, title, content }) => {
        const updates: any = {};
        if (title !== undefined) updates.title = title;
        if (content !== undefined) updates.content = content;
        
        const updatedNote = noteService.updateNote(id, updates);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(updatedNote, null, 2),
            },
          ],
        };
      }
    );
  • Core handler function that performs the actual note update: retrieves note by ID, updates markdown file content (handling title header specially) if NotePlan available, or updates mock database otherwise, then returns the updated note object.
    function updateNote(id: string, updates: UpdateNoteParams): Note {
      const existingNote = getNoteById(id);
      if (!existingNote) {
        throw new Error(`Note with id ${id} not found`);
      }
      
      if (isNotePlanAvailable() && existingNote.filePath) {
        try {
          // Update the file content
          let newContent = existingNote.content;
          
          if (updates.content !== undefined) {
            newContent = updates.content;
          }
          
          // If title is being updated, update the first markdown header
          if (updates.title !== undefined) {
            const lines = newContent.split('\n');
            let headerUpdated = false;
            
            for (let i = 0; i < lines.length; i++) {
              if (lines[i].startsWith('# ')) {
                lines[i] = `# ${updates.title}`;
                headerUpdated = true;
                break;
              }
            }
            
            // If no header found, add one at the beginning
            if (!headerUpdated) {
              lines.unshift(`# ${updates.title}`, '');
            }
            
            newContent = lines.join('\n');
          }
          
          // Write updated content to file
          fs.writeFileSync(existingNote.filePath, newContent, 'utf8');
          
          // Clear cache to force refresh
          notesCache = [];
          lastCacheUpdate = 0;
          
          // Return updated note
          return parseMarkdownFile(existingNote.filePath, existingNote.folder)!;
        } catch (error) {
          throw new Error(`Failed to update note: ${(error as Error).message}`);
        }
      } else {
        // Fallback to mock database
        const noteIndex = notesDb.findIndex(note => note.id === id);
        if (noteIndex === -1) {
          throw new Error(`Note with id ${id} not found`);
        }
        
        const note = notesDb[noteIndex];
        const updatedNote: Note = {
          ...note,
          ...updates,
          modified: new Date().toISOString()
        };
        
        notesDb[noteIndex] = updatedNote;
        return updatedNote;
      }
    }
  • TypeScript interface defining optional parameters for note updates (title, content, folder).
    interface UpdateNoteParams {
      title?: string;
      content?: string;
      folder?: string;
    }
  • Zod schema for 'update_note' tool input validation in MCP registration (id required, title and content optional with descriptions).
      id: z.string().describe('The ID of the note to update'),
      title: z.string().optional().describe('New title for the note'),
      content: z.string().optional().describe('New content for the note'),
    },
  • Exports the noteService object including the updateNote function for use by MCP handlers.
    export const noteService = {
      getAllNotes,
      getNoteById,
      searchNotes,
      getNotesByFolder,
      createDailyNote,
      createNote,
      updateNote
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/bscott/noteplan-mcp'

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