NoteVault

Open Source — GitScrum MCP Server is open source under the MIT license. Available on npm and GitHub. Model Context Protocol server for GitScrum — Claude, GitHub Copilot, Cursor, and any MCP-compatible client full operational access to your project management stack.

NoteVault is your personal and team workspace for notes — meeting summaries, sprint retrospectives, research logs, architecture drafts, and anything that doesn't belong in project-level documentation yet. Two tools work together to manage NoteVault: the note tool for creating and sharing notes, and the note_folder tool for organizing notes into folders.

Unlike Wiki pages, which are project-scoped documentation, NoteVault notes belong to you. They live in your workspace, can be organized into personal folders, and shared with specific team members when ready. Revision tracking lets you review previous versions of any note.

Note Tool — Actions Overview

The note tool provides 6 actions for the full note lifecycle:

Note Folder Tool — Actions Overview

The note_folder tool provides 4 actions for folder management:

Listing Notes

The list action returns all notes in your workspace. Each note in the response includes its uuid, title, folder assignment, creation date, and sharing status.

Required Parameters

You:  "Show all my notes"
AI:   Calls note action=list → returns your complete note inventory

You:  "List my notes in the Acme workspace"
AI:   Calls note action=list with company_slug → returns workspace notes

You:  "What notes do I have?"
AI:   Calls note action=list → summarizes your notes by folder and date

Creating Notes

The create action builds a new note with a title and Markdown content. Notes are created in your personal workspace — they're private until explicitly shared.

Required Parameters

Example Prompts

You:  "Create a note 'Sprint 14 Retrospective' with notes from today's meeting"
AI:   Calls note action=create with title and Markdown content

You:  "Create a note about the database migration research I've been doing"
AI:   Calls note action=create with research notes formatted in Markdown

You:  "Take a note: 'Meeting with Client — agreed on Q2 roadmap,
       priority is mobile app launch by March'"
AI:   Calls note action=create with meeting notes

You:  "Create a note summarizing the architecture options we discussed"
AI:   Calls note action=create with structured comparison in Markdown

Updating Notes

The update action modifies a note's title or content. Only the fields you specify are changed.

Required Parameters

Optional Parameters

You:  "Update my retrospective note with the action items we agreed on"
AI:   Finds note → calls note action=update with revised content

You:  "Add a follow-up section to my client meeting notes"
AI:   Gets current content → appends follow-up → calls note action=update

You:  "Rename my research note to 'Database Migration — Final Recommendation'"
AI:   Calls note action=update with title

Sharing Notes

The share action makes a note visible to specific team members by username. Shared notes appear in the recipient's note list, enabling collaborative review.

Required Parameters

Parameters

You:  "Share my retrospective note with @sarah and @john"
AI:   Calls note action=share with usernames=["sarah", "john"]

You:  "Share the architecture research note with the backend team"
AI:   Resolves team members → calls note action=share with their usernames

You:  "Share my meeting notes with the project manager"
AI:   Identifies the PM → calls note action=share with their username

Revision History

The revisions action returns the version history of a note — every time the content was updated, a revision is recorded. This lets you track how a note evolved over time and reference previous versions.

Required Parameters

You:  "Show the revision history of my architecture note"
AI:   Calls note action=revisions → returns list of revisions with timestamps

You:  "How many times has the onboarding note been updated?"
AI:   Calls note action=revisions → counts revisions

You:  "What did the meeting notes look like before the last edit?"
AI:   Calls note action=revisions → returns previous version content

Managing Folders

Note folders organize your notes into logical groups. The note_folder tool handles creation, renaming, and moving notes between folders.

Listing Folders

Returns all folders in your workspace, each with its uuid and name.

You:  "Show my note folders"
AI:   Calls note_folder action=list → returns folder list with UUIDs

You:  "How are my notes organized?"
AI:   Calls note_folder action=list + note action=list → shows folder structure

Creating Folders

Creates a new folder for organizing notes.

You:  "Create a folder called 'Meeting Notes'"
AI:   Calls note_folder action=create with name="Meeting Notes"

You:  "Create folders for 'Sprint Retros', 'Research', and 'Client Meetings'"
AI:   Calls note_folder action=create three times with each name

Renaming Folders

Updates the name of an existing folder.

You:  "Rename 'Meeting Notes' folder to 'Team Meetings'"
AI:   Finds folder → calls note_folder action=update with name="Team Meetings"

Moving Notes

Moves a note into a folder, or removes it from a folder (unfiling it). Omit folder_uuid to remove a note from its current folder.

You:  "Move my retrospective note to the Sprint Retros folder"
AI:   Finds note + folder → calls note_folder action=move with both UUIDs

You:  "Unfile the architecture note — remove it from its folder"
AI:   Calls note_folder action=move with note_uuid only (no folder_uuid)

You:  "Move all meeting notes to the Team Meetings folder"
AI:   Lists notes → identifies meeting notes → calls move for each

Folder Organization Workflow

Build a structured personal workspace for efficient note management:

1. Set up folder structure

Create folders that match your workflow patterns.

You:  "Create note folders: 'Sprint Retros', 'Client Meetings',
       'Research', 'Architecture Decisions'"
AI:   Creates four folders in sequence

2. Create and organize notes

Create notes and file them immediately, or organize existing notes.

You:  "Create a note 'Sprint 14 Retro' with today's retrospective feedback
       and put it in the Sprint Retros folder"
AI:   Creates note → moves it to the Sprint Retros folder

You:  "Move all my unfiled notes from this week into the appropriate folders"
AI:   Lists notes → categorizes by content → moves each to the matching folder

3. Share when ready

Share polished notes with team members for review or reference.

You:  "Share the Sprint 14 Retro note with the entire backend team"
AI:   Resolves team members → shares the note with all usernames

4. Track evolution

Use revision history to see how notes evolved over iterations.

You:  "Show how my architecture decision note changed over time"
AI:   Calls note action=revisions → displays the revision timeline

NoteVault vs Wiki vs Discussions

Choose the right collaboration tool:

Typical flow: Start with a NoteVault note for rough drafts and meeting captures. When the content matures, move it to a Wiki page for the team. If a topic needs discussion, create a Discussion thread.

Context Auto-Resolution

The note and note_folder tools support automatic context resolution. If your AI assistant knows the workspace from a previous call, you can say "create a note" without specifying the workspace every time.

Next Steps

• Wiki: Create project-level documentation from your polished notes.
• Discussions: Start project-level discussion threads.
• Search: Find content across all GitScrum entities.
• Quick Start: Set up the MCP server if you haven't already.