开发笔记管理扩展

My Dev Notes

A VS Code sidebar extension for managing workspace-scoped TODOs and scratch pad notes, with MCP server integration for AI agents.

Features

• TODOs — Add, edit, check off, snooze, pin as current task, and drag-reorder tasks. Organize with named groups.
• Project + Global scopes — Keep project-specific work separate from global notes that are visible in every workspace.
• Notes — Markdown scratch pad notes. Write in markdown, see rendered output. Double-click to edit.
• Search + tags — Filter TODOs and notes from the sidebar. Add #tags in TODO text and click tag chips to filter.
• Groups — Create named groups to organize TODOs. Drag to reorder groups.
• Archive — Completed TODOs are archived for 7 days, then auto-cleaned.
• Collapsible sections — Collapse TODOs, Notes, and individual groups.
• MCP Server — AI agents (e.g. Claude Code) can read and manage your TODOs and notes across project/global scopes.

Installation

VS Code Extension

1. Clone the repo and install dependencies:

   复制

   git clone https://github.com/reefbarman/mydevnotes.git
   cd mydevnotes
   npm install
   

2. Build the extension:

   复制

   npm run compile
   npm run bundle:mcp
   npm run bundle:webview
   

3. Install locally in VS Code — either:

   • Open the repo in VS Code, press F5 to launch the Extension Development Host, or

   • Package and install the .vsix:

     复制

     npx @vscode/vsce package
     code --install-extension mydevnotes-*.vsix
     

4. The "My Dev Notes" icon will appear in the activity bar sidebar.

MCP Server (for AI agents)

The extension can auto-register its MCP server with Claude Code. On first activation you'll be prompted to enable this. If you choose "Enable", it writes the following to ~/.claude.json:

{
  "mcpServers": {
    "mydevnotes": {
      "command": "node",
      "args": ["/path/to/extension/out/mcp-server.js"]
    }
  }
}

To register manually, add the above to your ~/.claude.json (updating the path to point to the installed extension's out/mcp-server.js).

For project-scoped data, the MCP server uses an explicit --workspace argument or MYDEVNOTES_WORKSPACE environment variable when provided, then a workspace root advertised by the MCP client, and finally process.cwd() for clients that do not support roots. With multiple roots, the root containing process.cwd() is used; otherwise configure an explicit workspace. The resolved workspace is cached for the MCP connection, so reconnect after changing roots.

Place --workspace after the server script in a manual configuration:

{
  "mcpServers": {
    "mydevnotes": {
      "command": "node",
      "args": [
        "/path/to/extension/out/mcp-server.js",
        "--workspace=/path/to/project"
      ]
    }
  }
}

You can control auto-registration via the mydevnotes.mcpAutoRegister setting (see Configuration below).

MCP Tools

TODO Tools

Note Tools

Most MCP tools accept an optional scope parameter: "project" (default, keyed by the resolved workspace path) or "global" (shared everywhere). set_current_task and get_current_task are project-only.

Embedded images are returned as MCP image content by list_todos, list_completed_todos, get_current_task, and list_notes. Their inline data URLs are replaced with compact attachment:img-N Markdown references in the text response.

Configuration

Data Storage

State is stored in ~/.mydevnotes/data.json, keyed by workspace path. Global items use the reserved key ::global::. This keeps your project directories clean — no per-project config files or .gitignore entries needed.

Current schema version is 3. Older extension/MCP versions can read the file shape but will not understand snoozed TODO behavior or current-task clearing rules.