obsidian-mcp-server 2.0.5 → 2.0.7

package/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.7] - 2025-06-20
+
+### Changed
+
+- **Package Update**: Fixed README & incremented version to 2.0.7 to ensure the latest changes are reflected in the npm package.
+
+## [2.0.6] - 2025-06-20
+
+### Changed
+
+- **Tool Renaming**: Renamed `obsidian_read_file`, `obsidian_delete_file`, and `obsidian_list_files` to `obsidian_read_note`, `obsidian_delete_note`, and `obsidian_list_notes` respectively. This change improves semantic clarity and aligns the tool names more closely with Obsidian's terminology, reducing ambiguity for AI agents.
+- **Dependency Updates**: Updated all dependencies to their latest versions.
+- **Documentation Improvements**: Updated `.clinerules` to reflect the new tool names and ensure all documentation is current.
+
 ## [2.0.5] - 2025-06-20
 
 ### Changed

package/README.md

@@ -2,7 +2,7 @@
 
 [![TypeScript](https://img.shields.io/badge/TypeScript-^5.8.3-blue.svg)](https://www.typescriptlang.org/)
 [![Model Context Protocol](https://img.shields.io/badge/MCP%20SDK-^1.13.0-green.svg)](https://modelcontextprotocol.io/)
-[![Version](https://img.shields.io/badge/Version-2.0.5-blue.svg)](./CHANGELOG.md)
+[![Version](https://img.shields.io/badge/Version-2.0.7-blue.svg)](./CHANGELOG.md)
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 [![Status](https://img.shields.io/badge/Status-Production-brightgreen.svg)](https://github.com/cyanheads/obsidian-mcp-server/issues)
 [![GitHub](https://img.shields.io/github/stars/cyanheads/obsidian-mcp-server?style=social)](https://github.com/cyanheads/obsidian-mcp-server)
@@ -19,14 +19,14 @@ This server equips your AI with specialized tools to interact with your Obsidian
 
 | Tool Name                                                                              | Description                                                     | Key Features                                                                                                                                           |
 | :------------------------------------------------------------------------------------- | :-------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`obsidian_read_file`](./src/mcp-server/tools/obsidianReadFileTool/)                   | Retrieves the content and metadata of a specified file.         | - Read in `markdown` or `json` format.<br/>- Case-insensitive path fallback.<br/>- Includes file stats (creation/modification time).                   |
+| [`obsidian_read_note`](./src/mcp-server/tools/obsidianReadNoteTool/)                   | Retrieves the content and metadata of a specified note.         | - Read in `markdown` or `json` format.<br/>- Case-insensitive path fallback.<br/>- Includes file stats (creation/modification time).                   |
 | [`obsidian_update_note`](./src/mcp-server/tools/obsidianUpdateNoteTool/)               | Modifies notes using whole-file operations.                     | - `append`, `prepend`, or `overwrite` content.<br/>- Can create files if they don't exist.<br/>- Targets files by path, active note, or periodic note. |
 | [`obsidian_search_replace`](./src/mcp-server/tools/obsidianSearchReplaceTool/)         | Performs search-and-replace operations within a target note.    | - Supports string or regex search.<br/>- Options for case sensitivity, whole word, and replacing all occurrences.                                      |
 | [`obsidian_global_search`](./src/mcp-server/tools/obsidianGlobalSearchTool/)           | Performs a search across the entire vault.                      | - Text or regex search.<br/>- Filter by path and modification date.<br/>- Paginated results.                                                           |
-| [`obsidian_list_files`](./src/mcp-server/tools/obsidianListFilesTool/)                 | Lists files and subdirectories within a specified vault folder. | - Filter by file extension or name regex.<br/>- Provides a formatted tree view of the directory.                                                       |
+| [`obsidian_list_notes`](./src/mcp-server/tools/obsidianListNotesTool/)                 | Lists notes and subdirectories within a specified vault folder. | - Filter by file extension or name regex.<br/>- Provides a formatted tree view of the directory.                                                       |
 | [`obsidian_manage_frontmatter`](./src/mcp-server/tools/obsidianManageFrontmatterTool/) | Atomically manages a note's YAML frontmatter.                   | - `get`, `set`, or `delete` frontmatter keys.<br/>- Avoids rewriting the entire file for metadata changes.                                             |
 | [`obsidian_manage_tags`](./src/mcp-server/tools/obsidianManageTagsTool/)               | Adds, removes, or lists tags for a note.                        | - Manages tags in both YAML frontmatter and inline content.                                                                                            |
-| [`obsidian_delete_file`](./src/mcp-server/tools/obsidianDeleteFileTool/)               | Permanently deletes a specified file from the vault.            | - Case-insensitive path fallback for safety.                                                                                                           |
+| [`obsidian_delete_note`](./src/mcp-server/tools/obsidianDeleteNoteTool/)               | Permanently deletes a specified note from the vault.            | - Case-insensitive path fallback for safety.                                                                                                           |
 
 ---
 
@@ -239,14 +239,14 @@ The Obsidian MCP Server provides a suite of tools for interacting with your vaul
 
 | Tool Name                     | Description                                               | Key Arguments                                                 |
 | :---------------------------- | :-------------------------------------------------------- | :------------------------------------------------------------ |
-| `obsidian_read_file`          | Retrieves the content and metadata of a file.             | `filePath`, `format?`, `includeStat?`                         |
+| `obsidian_read_note`          | Retrieves the content and metadata of a note.             | `filePath`, `format?`, `includeStat?`                         |
 | `obsidian_update_note`        | Modifies a file by appending, prepending, or overwriting. | `targetType`, `content`, `targetIdentifier?`, `wholeFileMode` |
 | `obsidian_search_replace`     | Performs search-and-replace operations in a note.         | `targetType`, `replacements`, `useRegex?`, `replaceAll?`      |
 | `obsidian_global_search`      | Searches the entire vault for content.                    | `query`, `searchInPath?`, `useRegex?`, `page?`, `pageSize?`   |
-| `obsidian_list_files`         | Lists files and subdirectories in a folder.               | `dirPath`, `fileExtensionFilter?`, `nameRegexFilter?`         |
+| `obsidian_list_notes`         | Lists notes and subdirectories in a folder.               | `dirPath`, `fileExtensionFilter?`, `nameRegexFilter?`         |
 | `obsidian_manage_frontmatter` | Gets, sets, or deletes keys in a note's frontmatter.      | `filePath`, `operation`, `key`, `value?`                      |
 | `obsidian_manage_tags`        | Adds, removes, or lists tags in a note.                   | `filePath`, `operation`, `tags`                               |
-| `obsidian_delete_file`        | Permanently deletes a file from the vault.                | `filePath`                                                    |
+| `obsidian_delete_note`        | Permanently deletes a note from the vault.                | `filePath`                                                    |
 
 _Note: All tools support comprehensive error handling and return structured JSON responses._
 

package/dist/mcp-server/server.js

@@ -19,10 +19,10 @@ import { config, environment } from "../config/index.js";
 // Import core utilities: ErrorHandler, logger, requestContextService.
 import { ErrorHandler, logger, requestContextService } from "../utils/index.js";
 // Import registration functions for specific resources and tools.
-import { registerObsidianDeleteFileTool } from "./tools/obsidianDeleteFileTool/index.js";
+import { registerObsidianDeleteNoteTool } from "./tools/obsidianDeleteNoteTool/index.js";
 import { registerObsidianGlobalSearchTool } from "./tools/obsidianGlobalSearchTool/index.js";
-import { registerObsidianListFilesTool } from "./tools/obsidianListFilesTool/index.js";
-import { registerObsidianReadFileTool } from "./tools/obsidianReadFileTool/index.js";
+import { registerObsidianListNotesTool } from "./tools/obsidianListNotesTool/index.js";
+import { registerObsidianReadNoteTool } from "./tools/obsidianReadNoteTool/index.js";
 import { registerObsidianSearchReplaceTool } from "./tools/obsidianSearchReplaceTool/index.js";
 import { registerObsidianUpdateNoteTool } from "./tools/obsidianUpdateNoteTool/index.js";
 import { registerObsidianManageFrontmatterTool } from "./tools/obsidianManageFrontmatterTool/index.js";
@@ -83,9 +83,9 @@ async function createMcpServerInstance(obsidianService, vaultCacheService) {
     try {
         logger.debug("Registering resources and tools using shared services...", context);
         // Register all tools, passing the vaultCacheService which may be undefined
-        await registerObsidianListFilesTool(server, obsidianService);
-        await registerObsidianReadFileTool(server, obsidianService);
-        await registerObsidianDeleteFileTool(server, obsidianService, vaultCacheService);
+        await registerObsidianListNotesTool(server, obsidianService);
+        await registerObsidianReadNoteTool(server, obsidianService);
+        await registerObsidianDeleteNoteTool(server, obsidianService, vaultCacheService);
         if (vaultCacheService) {
             await registerObsidianGlobalSearchTool(server, obsidianService, vaultCacheService);
         }

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/index.d.ts

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_delete_file' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_delete_note' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_delete_file tool module.
- * It re-exports the primary registration function (`registerObsidianDeleteFileTool`)
+ * This file serves as the public entry point for the obsidian_delete_note tool module.
+ * It re-exports the primary registration function (`registerObsidianDeleteNoteTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianDeleteFileTool } from "./registration.js";
+export { registerObsidianDeleteNoteTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/index.js

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_delete_file' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_delete_note' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_delete_file tool module.
- * It re-exports the primary registration function (`registerObsidianDeleteFileTool`)
+ * This file serves as the public entry point for the obsidian_delete_note tool module.
+ * It re-exports the primary registration function (`registerObsidianDeleteNoteTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianDeleteFileTool } from "./registration.js";
+export { registerObsidianDeleteNoteTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/logic.d.ts

@@ -2,9 +2,9 @@ import { z } from "zod";
 import { ObsidianRestApiService, VaultCacheService } from "../../../services/obsidianRestAPI/index.js";
 import { RequestContext } from "../../../utils/index.js";
 /**
- * Zod schema for validating the input parameters of the 'obsidian_delete_file' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_delete_note' tool.
  */
-export declare const ObsidianDeleteFileInputSchema: z.ZodObject<{
+export declare const ObsidianDeleteNoteInputSchema: z.ZodObject<{
     /**
      * The vault-relative path to the file to be permanently deleted.
      * Must include the file extension (e.g., "Old Notes/Obsolete File.md").
@@ -18,15 +18,15 @@ export declare const ObsidianDeleteFileInputSchema: z.ZodObject<{
     filePath: string;
 }>;
 /**
- * TypeScript type inferred from the input schema (`ObsidianDeleteFileInputSchema`).
+ * TypeScript type inferred from the input schema (`ObsidianDeleteNoteInputSchema`).
  * Represents the validated input parameters used within the core processing logic.
  */
-export type ObsidianDeleteFileInput = z.infer<typeof ObsidianDeleteFileInputSchema>;
+export type ObsidianDeleteNoteInput = z.infer<typeof ObsidianDeleteNoteInputSchema>;
 /**
- * Defines the structure of the successful response returned by the `processObsidianDeleteFile` function.
+ * Defines the structure of the successful response returned by the `processObsidianDeleteNote` function.
  * This object is typically serialized to JSON and sent back to the client.
  */
-export interface ObsidianDeleteFileResponse {
+export interface ObsidianDeleteNoteResponse {
     /** Indicates whether the deletion operation was successful. */
     success: boolean;
     /** A human-readable message confirming the deletion and specifying the path used. */
@@ -40,12 +40,12 @@ export interface ObsidianDeleteFileResponse {
  * it lists the directory, finds a unique case-insensitive match for the filename,
  * and retries the deletion with the corrected path.
  *
- * @param {ObsidianDeleteFileInput} params - The validated input parameters.
+ * @param {ObsidianDeleteNoteInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianDeleteFileResponse>} A promise resolving to the structured success response
+ * @returns {Promise<ObsidianDeleteNoteResponse>} A promise resolving to the structured success response
  *   containing a confirmation message.
  * @throws {McpError} Throws an McpError if the file cannot be found (even with fallback),
  *   if there's an ambiguous fallback match, or if any other API interaction fails.
  */
-export declare const processObsidianDeleteFile: (params: ObsidianDeleteFileInput, context: RequestContext, obsidianService: ObsidianRestApiService, vaultCacheService: VaultCacheService | undefined) => Promise<ObsidianDeleteFileResponse>;
+export declare const processObsidianDeleteNote: (params: ObsidianDeleteNoteInput, context: RequestContext, obsidianService: ObsidianRestApiService, vaultCacheService: VaultCacheService | undefined) => Promise<ObsidianDeleteNoteResponse>;

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/logic.js

@@ -6,9 +6,9 @@ import { logger, retryWithDelay, } from "../../../utils/index.js";
 // Schema Definitions for Input Validation
 // ====================================================================================
 /**
- * Zod schema for validating the input parameters of the 'obsidian_delete_file' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_delete_note' tool.
  */
-export const ObsidianDeleteFileInputSchema = z
+export const ObsidianDeleteNoteInputSchema = z
     .object({
     /**
      * The vault-relative path to the file to be permanently deleted.
@@ -33,18 +33,18 @@ export const ObsidianDeleteFileInputSchema = z
  * it lists the directory, finds a unique case-insensitive match for the filename,
  * and retries the deletion with the corrected path.
  *
- * @param {ObsidianDeleteFileInput} params - The validated input parameters.
+ * @param {ObsidianDeleteNoteInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianDeleteFileResponse>} A promise resolving to the structured success response
+ * @returns {Promise<ObsidianDeleteNoteResponse>} A promise resolving to the structured success response
  *   containing a confirmation message.
  * @throws {McpError} Throws an McpError if the file cannot be found (even with fallback),
  *   if there's an ambiguous fallback match, or if any other API interaction fails.
  */
-export const processObsidianDeleteFile = async (params, context, obsidianService, vaultCacheService) => {
+export const processObsidianDeleteNote = async (params, context, obsidianService, vaultCacheService) => {
     const { filePath: originalFilePath } = params;
     let effectiveFilePath = originalFilePath; // Track the path actually used for deletion
-    logger.debug(`Processing obsidian_delete_file request for path: ${originalFilePath}`, context);
+    logger.debug(`Processing obsidian_delete_note request for path: ${originalFilePath}`, context);
     const shouldRetryNotFound = (err) => err instanceof McpError && err.code === BaseErrorCode.NOT_FOUND;
     try {
         // --- Attempt 1: Delete using the provided path (case-sensitive) ---

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/registration.d.ts

@@ -1,7 +1,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { ObsidianRestApiService, VaultCacheService } from "../../../services/obsidianRestAPI/index.js";
 /**
- * Registers the 'obsidian_delete_file' tool with the MCP server.
+ * Registers the 'obsidian_delete_note' tool with the MCP server.
  *
  * This tool permanently deletes a specified file from the user's Obsidian vault.
  * It requires the vault-relative path, including the file extension. The tool
@@ -16,4 +16,4 @@ import { ObsidianRestApiService, VaultCacheService } from "../../../services/obs
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export declare const registerObsidianDeleteFileTool: (server: McpServer, obsidianService: ObsidianRestApiService, vaultCacheService: VaultCacheService | undefined) => Promise<void>;
+export declare const registerObsidianDeleteNoteTool: (server: McpServer, obsidianService: ObsidianRestApiService, vaultCacheService: VaultCacheService | undefined) => Promise<void>;

package/dist/mcp-server/tools/{obsidianDeleteFileTool → obsidianDeleteNoteTool}/registration.js

@@ -1,8 +1,8 @@
 import { BaseErrorCode, McpError } from "../../../types-global/errors.js";
 import { ErrorHandler, logger, requestContextService, } from "../../../utils/index.js";
-import { ObsidianDeleteFileInputSchema, processObsidianDeleteFile, } from "./logic.js";
+import { ObsidianDeleteNoteInputSchema, processObsidianDeleteNote, } from "./logic.js";
 /**
- * Registers the 'obsidian_delete_file' tool with the MCP server.
+ * Registers the 'obsidian_delete_note' tool with the MCP server.
  *
  * This tool permanently deletes a specified file from the user's Obsidian vault.
  * It requires the vault-relative path, including the file extension. The tool
@@ -17,26 +17,26 @@ import { ObsidianDeleteFileInputSchema, processObsidianDeleteFile, } from "./log
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export const registerObsidianDeleteFileTool = async (server, obsidianService, vaultCacheService) => {
-    const toolName = "obsidian_delete_file";
+export const registerObsidianDeleteNoteTool = async (server, obsidianService, vaultCacheService) => {
+    const toolName = "obsidian_delete_note";
     // Updated description to accurately reflect the response (no timestamp)
     const toolDescription = "Permanently deletes a specified file from the Obsidian vault. Tries the exact path first, then attempts a case-insensitive fallback if the file is not found. Requires the vault-relative path including the file extension. Returns a success message.";
     // Create a context specifically for the registration process.
     const registrationContext = requestContextService.createRequestContext({
-        operation: "RegisterObsidianDeleteFileTool",
+        operation: "RegisterObsidianDeleteNoteTool",
         toolName: toolName,
-        module: "ObsidianDeleteFileRegistration", // Identify the module
+        module: "ObsidianDeleteNoteRegistration", // Identify the module
     });
     logger.info(`Attempting to register tool: ${toolName}`, registrationContext);
     // Wrap the registration logic in a tryCatch block for robust error handling during server setup.
     await ErrorHandler.tryCatch(async () => {
         // Use the high-level SDK method `server.tool` for registration.
-        server.tool(toolName, toolDescription, ObsidianDeleteFileInputSchema.shape, // Provide the Zod schema shape for input definition.
+        server.tool(toolName, toolDescription, ObsidianDeleteNoteInputSchema.shape, // Provide the Zod schema shape for input definition.
         /**
-         * The handler function executed when the 'obsidian_delete_file' tool is called by the client.
+         * The handler function executed when the 'obsidian_delete_note' tool is called by the client.
          *
-         * @param {ObsidianDeleteFileInput} params - The input parameters received from the client,
-         *   validated against the ObsidianDeleteFileInputSchema shape.
+         * @param {ObsidianDeleteNoteInput} params - The input parameters received from the client,
+         *   validated against the ObsidianDeleteNoteInputSchema shape.
          * @returns {Promise<CallToolResult>} A promise resolving to the structured result for the MCP client,
          *   containing either the successful response data (serialized JSON) or an error indication.
          */
@@ -45,7 +45,7 @@ export const registerObsidianDeleteFileTool = async (server, obsidianService, va
             // Create a specific context for this handler invocation.
             const handlerContext = requestContextService.createRequestContext({
                 parentContext: registrationContext, // Link to registration context
-                operation: "HandleObsidianDeleteFileRequest",
+                operation: "HandleObsidianDeleteNoteRequest",
                 toolName: toolName,
                 params: { filePath: params.filePath }, // Log the file path being targeted
             });
@@ -54,7 +54,7 @@ export const registerObsidianDeleteFileTool = async (server, obsidianService, va
             return await ErrorHandler.tryCatch(async () => {
                 // Delegate the actual file deletion logic to the processing function.
                 // Note: Input schema and shape are identical, no separate refinement parse needed here.
-                const response = await processObsidianDeleteFile(params, handlerContext, obsidianService, vaultCacheService);
+                const response = await processObsidianDeleteNote(params, handlerContext, obsidianService, vaultCacheService);
                 logger.debug(`'${toolName}' processed successfully`, handlerContext);
                 // Format the successful response object from the logic function into the required MCP CallToolResult structure.
                 // The response object (success, message) is serialized to JSON.

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/index.d.ts

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_list_files' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_list_notes' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_list_files tool module.
- * It re-exports the primary registration function (`registerObsidianListFilesTool`)
+ * This file serves as the public entry point for the obsidian_list_notes tool module.
+ * It re-exports the primary registration function (`registerObsidianListNotesTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianListFilesTool } from "./registration.js";
+export { registerObsidianListNotesTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/index.js

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_list_files' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_list_notes' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_list_files tool module.
- * It re-exports the primary registration function (`registerObsidianListFilesTool`)
+ * This file serves as the public entry point for the obsidian_list_notes tool module.
+ * It re-exports the primary registration function (`registerObsidianListNotesTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianListFilesTool } from "./registration.js";
+export { registerObsidianListNotesTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/logic.d.ts

@@ -1,16 +1,16 @@
 /**
- * @fileoverview Core logic for the 'obsidian_list_files' tool.
+ * @fileoverview Core logic for the 'obsidian_list_notes' tool.
  * This module defines the input schema, response types, and processing logic for
  * recursively listing files and directories in an Obsidian vault with filtering.
- * @module src/mcp-server/tools/obsidianListFilesTool/logic
+ * @module src/mcp-server/tools/obsidianListNotesTool/logic
  */
 import { z } from "zod";
 import { ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.js";
 import { RequestContext } from "../../../utils/index.js";
 /**
- * Zod schema for validating the input parameters of the 'obsidian_list_files' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_list_notes' tool.
  */
-export declare const ObsidianListFilesInputSchema: z.ZodObject<{
+export declare const ObsidianListNotesInputSchema: z.ZodObject<{
     /**
      * The vault-relative path to the directory whose contents should be listed.
      * The path is treated as case-sensitive by the underlying Obsidian API.
@@ -45,13 +45,13 @@ export declare const ObsidianListFilesInputSchema: z.ZodObject<{
     recursionDepth?: number | undefined;
 }>;
 /**
- * TypeScript type inferred from the input schema (`ObsidianListFilesInputSchema`).
+ * TypeScript type inferred from the input schema (`ObsidianListNotesInputSchema`).
  */
-export type ObsidianListFilesInput = z.infer<typeof ObsidianListFilesInputSchema>;
+export type ObsidianListNotesInput = z.infer<typeof ObsidianListNotesInputSchema>;
 /**
  * Defines the structure of the successful response returned by the core logic function.
  */
-export interface ObsidianListFilesResponse {
+export interface ObsidianListNotesResponse {
     directoryPath: string;
     tree: string;
     totalEntries: number;
@@ -59,10 +59,10 @@ export interface ObsidianListFilesResponse {
 /**
  * Processes the core logic for listing files and directories recursively within the Obsidian vault.
  *
- * @param {ObsidianListFilesInput} params - The validated input parameters.
+ * @param {ObsidianListNotesInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianListFilesResponse>} A promise resolving to the structured success response.
+ * @returns {Promise<ObsidianListNotesResponse>} A promise resolving to the structured success response.
  * @throws {McpError} Throws an McpError if the initial directory is not found or another error occurs.
  */
-export declare const processObsidianListFiles: (params: ObsidianListFilesInput, context: RequestContext, obsidianService: ObsidianRestApiService) => Promise<ObsidianListFilesResponse>;
+export declare const processObsidianListNotes: (params: ObsidianListNotesInput, context: RequestContext, obsidianService: ObsidianRestApiService) => Promise<ObsidianListNotesResponse>;

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/logic.js

@@ -1,8 +1,8 @@
 /**
- * @fileoverview Core logic for the 'obsidian_list_files' tool.
+ * @fileoverview Core logic for the 'obsidian_list_notes' tool.
  * This module defines the input schema, response types, and processing logic for
  * recursively listing files and directories in an Obsidian vault with filtering.
- * @module src/mcp-server/tools/obsidianListFilesTool/logic
+ * @module src/mcp-server/tools/obsidianListNotesTool/logic
  */
 import path from "node:path";
 import { z } from "zod";
@@ -12,9 +12,9 @@ import { logger, retryWithDelay, } from "../../../utils/index.js";
 // Schema Definitions for Input Validation
 // ====================================================================================
 /**
- * Zod schema for validating the input parameters of the 'obsidian_list_files' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_list_notes' tool.
  */
-export const ObsidianListFilesInputSchema = z
+export const ObsidianListNotesInputSchema = z
     .object({
     /**
      * The vault-relative path to the directory whose contents should be listed.
@@ -84,7 +84,7 @@ function formatTree(nodes, indent = "") {
  *
  * @param {string} dirPath - The path of the directory to process.
  * @param {number} currentDepth - The current recursion depth.
- * @param {ObsidianListFilesInput} params - The original validated input parameters, including filters and max depth.
+ * @param {ObsidianListNotesInput} params - The original validated input parameters, including filters and max depth.
  * @param {RequestContext} context - The request context for logging.
  * @param {ObsidianRestApiService} obsidianService - The Obsidian API service instance.
  * @returns {Promise<FileTreeNode[]>} A promise that resolves to an array of file tree nodes.
@@ -151,16 +151,16 @@ async function buildFileTree(dirPath, currentDepth, params, context, obsidianSer
 /**
  * Processes the core logic for listing files and directories recursively within the Obsidian vault.
  *
- * @param {ObsidianListFilesInput} params - The validated input parameters.
+ * @param {ObsidianListNotesInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianListFilesResponse>} A promise resolving to the structured success response.
+ * @returns {Promise<ObsidianListNotesResponse>} A promise resolving to the structured success response.
  * @throws {McpError} Throws an McpError if the initial directory is not found or another error occurs.
  */
-export const processObsidianListFiles = async (params, context, obsidianService) => {
+export const processObsidianListNotes = async (params, context, obsidianService) => {
     const { dirPath } = params;
     const dirPathForLog = dirPath === "" || dirPath === "/" ? "/" : dirPath;
-    logger.debug(`Processing obsidian_list_files request for path: ${dirPathForLog}`, { ...context, params });
+    logger.debug(`Processing obsidian_list_notes request for path: ${dirPathForLog}`, { ...context, params });
     try {
         const effectiveDirPath = dirPath === "" ? "/" : dirPath;
         // --- Step 1: Build the file tree recursively with retry for the initial call ---

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/registration.d.ts

@@ -1,13 +1,13 @@
 /**
- * @fileoverview Registers the 'obsidian_list_files' tool with the MCP server.
+ * @fileoverview Registers the 'obsidian_list_notes' tool with the MCP server.
  * This file defines the tool's metadata and sets up the handler that links
  * the tool call to its core processing logic.
- * @module src/mcp-server/tools/obsidianListFilesTool/registration
+ * @module src/mcp-server/tools/obsidianListNotesTool/registration
  */
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.js";
 /**
- * Registers the 'obsidian_list_files' tool with the MCP server.
+ * Registers the 'obsidian_list_notes' tool with the MCP server.
  *
  * This tool lists the files and subdirectories within a specified directory
  * in the user's Obsidian vault. It supports optional filtering by file extension,
@@ -20,4 +20,4 @@ import { ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export declare const registerObsidianListFilesTool: (server: McpServer, obsidianService: ObsidianRestApiService) => Promise<void>;
+export declare const registerObsidianListNotesTool: (server: McpServer, obsidianService: ObsidianRestApiService) => Promise<void>;

package/dist/mcp-server/tools/{obsidianListFilesTool → obsidianListNotesTool}/registration.js

@@ -1,14 +1,14 @@
 /**
- * @fileoverview Registers the 'obsidian_list_files' tool with the MCP server.
+ * @fileoverview Registers the 'obsidian_list_notes' tool with the MCP server.
  * This file defines the tool's metadata and sets up the handler that links
  * the tool call to its core processing logic.
- * @module src/mcp-server/tools/obsidianListFilesTool/registration
+ * @module src/mcp-server/tools/obsidianListNotesTool/registration
  */
 import { BaseErrorCode, McpError } from "../../../types-global/errors.js";
 import { ErrorHandler, logger, requestContextService, } from "../../../utils/index.js";
-import { ObsidianListFilesInputSchema, processObsidianListFiles, } from "./logic.js";
+import { ObsidianListNotesInputSchema, processObsidianListNotes, } from "./logic.js";
 /**
- * Registers the 'obsidian_list_files' tool with the MCP server.
+ * Registers the 'obsidian_list_notes' tool with the MCP server.
  *
  * This tool lists the files and subdirectories within a specified directory
  * in the user's Obsidian vault. It supports optional filtering by file extension,
@@ -21,25 +21,25 @@ import { ObsidianListFilesInputSchema, processObsidianListFiles, } from "./logic
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export const registerObsidianListFilesTool = async (server, obsidianService) => {
-    const toolName = "obsidian_list_files";
+export const registerObsidianListNotesTool = async (server, obsidianService) => {
+    const toolName = "obsidian_list_notes";
     const toolDescription = "Lists files and subdirectories within a specified Obsidian vault folder. Supports optional filtering by extension or name regex, and recursive listing to a specified depth (-1 for infinite). Returns an object containing the listed directory path, a formatted tree string of its contents, and the total entry count. Use an empty string or '/' for dirPath to list the vault root.";
     // Create a context specifically for the registration process.
     const registrationContext = requestContextService.createRequestContext({
-        operation: "RegisterObsidianListFilesTool",
+        operation: "RegisterObsidianListNotesTool",
         toolName: toolName,
-        module: "ObsidianListFilesRegistration", // Identify the module
+        module: "ObsidianListNotesRegistration", // Identify the module
     });
     logger.info(`Attempting to register tool: ${toolName}`, registrationContext);
     // Wrap the registration logic in a tryCatch block for robust error handling during server setup.
     await ErrorHandler.tryCatch(async () => {
         // Use the high-level SDK method `server.tool` for registration.
-        server.tool(toolName, toolDescription, ObsidianListFilesInputSchema.shape, // Provide the Zod schema shape for input definition.
+        server.tool(toolName, toolDescription, ObsidianListNotesInputSchema.shape, // Provide the Zod schema shape for input definition.
         /**
-         * The handler function executed when the 'obsidian_list_files' tool is called by the client.
+         * The handler function executed when the 'obsidian_list_notes' tool is called by the client.
          *
-         * @param {ObsidianListFilesInput} params - The input parameters received from the client,
-         *   validated against the ObsidianListFilesInputSchema shape.
+         * @param {ObsidianListNotesInput} params - The input parameters received from the client,
+         *   validated against the ObsidianListNotesInputSchema shape.
          * @returns {Promise<CallToolResult>} A promise resolving to the structured result for the MCP client,
          *   containing either the successful response data (serialized JSON) or an error indication.
          */
@@ -48,7 +48,7 @@ export const registerObsidianListFilesTool = async (server, obsidianService) =>
             // Create a specific context for this handler invocation.
             const handlerContext = requestContextService.createRequestContext({
                 parentContext: registrationContext, // Link to registration context
-                operation: "HandleObsidianListFilesRequest",
+                operation: "HandleObsidianListNotesRequest",
                 toolName: toolName,
                 params: {
                     // Log all relevant parameters for debugging
@@ -62,7 +62,7 @@ export const registerObsidianListFilesTool = async (server, obsidianService) =>
             // Wrap the core logic execution in a tryCatch block.
             return await ErrorHandler.tryCatch(async () => {
                 // Delegate the actual file listing and filtering logic to the processing function.
-                const response = await processObsidianListFiles(params, handlerContext, obsidianService);
+                const response = await processObsidianListNotes(params, handlerContext, obsidianService);
                 logger.debug(`'${toolName}' processed successfully`, handlerContext);
                 // Format the successful response object from the logic function into the required MCP CallToolResult structure.
                 return {

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/index.d.ts

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_read_file' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_read_note' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_read_file tool module.
- * It re-exports the primary registration function (`registerObsidianReadFileTool`)
+ * This file serves as the public entry point for the obsidian_read_note tool module.
+ * It re-exports the primary registration function (`registerObsidianReadNoteTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianReadFileTool } from "./registration.js";
+export { registerObsidianReadNoteTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/index.js

@@ -1,12 +1,12 @@
 /**
- * @fileoverview Barrel file for the 'obsidian_read_file' MCP tool.
+ * @fileoverview Barrel file for the 'obsidian_read_note' MCP tool.
  *
- * This file serves as the public entry point for the obsidian_read_file tool module.
- * It re-exports the primary registration function (`registerObsidianReadFileTool`)
+ * This file serves as the public entry point for the obsidian_read_note tool module.
+ * It re-exports the primary registration function (`registerObsidianReadNoteTool`)
  * from the './registration.js' module. This pattern simplifies imports for consumers
  * of the tool, allowing them to import necessary components from a single location.
  *
  * Consumers (like the main server setup) should import the registration function
  * from this file to integrate the tool into the MCP server instance.
  */
-export { registerObsidianReadFileTool } from "./registration.js";
+export { registerObsidianReadNoteTool } from "./registration.js";

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/logic.d.ts

@@ -2,9 +2,9 @@ import { z } from "zod";
 import { NoteJson, ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.js";
 import { RequestContext } from "../../../utils/index.js";
 /**
- * Zod schema for validating the input parameters of the 'obsidian_read_file' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_read_note' tool.
  */
-export declare const ObsidianReadFileInputSchema: z.ZodObject<{
+export declare const ObsidianReadNoteInputSchema: z.ZodObject<{
     /**
      * The vault-relative path to the target file (e.g., "Folder/My Note.md").
      * Must include the file extension. The tool first attempts a case-sensitive match.
@@ -34,10 +34,10 @@ export declare const ObsidianReadFileInputSchema: z.ZodObject<{
     includeStat?: boolean | undefined;
 }>;
 /**
- * TypeScript type inferred from the input schema (`ObsidianReadFileInputSchema`).
+ * TypeScript type inferred from the input schema (`ObsidianReadNoteInputSchema`).
  * Represents the validated input parameters used within the core processing logic.
  */
-export type ObsidianReadFileInput = z.infer<typeof ObsidianReadFileInputSchema>;
+export type ObsidianReadNoteInput = z.infer<typeof ObsidianReadNoteInputSchema>;
 /**
  * Represents the structure of file statistics after formatting, including
  * human-readable timestamps and an estimated token count.
@@ -51,10 +51,10 @@ type FormattedStat = {
     tokenCountEstimate: number;
 };
 /**
- * Defines the structure of the successful response returned by the `processObsidianReadFile` function.
+ * Defines the structure of the successful response returned by the `processObsidianReadNote` function.
  * This object is typically serialized to JSON and sent back to the client.
  */
-export interface ObsidianReadFileResponse {
+export interface ObsidianReadNoteResponse {
     /**
      * The content of the file in the requested format.
      * If format='markdown', this is a string.
@@ -75,13 +75,13 @@ export interface ObsidianReadFileResponse {
  * internally to access file statistics. Finally, it formats the response
  * according to the requested format ('markdown' or 'json') and the 'includeStat' flag.
  *
- * @param {ObsidianReadFileInput} params - The validated input parameters.
+ * @param {ObsidianReadNoteInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianReadFileResponse>} A promise resolving to the structured success response
+ * @returns {Promise<ObsidianReadNoteResponse>} A promise resolving to the structured success response
  *   containing the file content and optionally formatted statistics.
  * @throws {McpError} Throws an McpError if the file cannot be found (even with fallback),
  *   if there's an ambiguous fallback match, or if any other API interaction fails.
  */
-export declare const processObsidianReadFile: (params: ObsidianReadFileInput, context: RequestContext, obsidianService: ObsidianRestApiService) => Promise<ObsidianReadFileResponse>;
+export declare const processObsidianReadNote: (params: ObsidianReadNoteInput, context: RequestContext, obsidianService: ObsidianRestApiService) => Promise<ObsidianReadNoteResponse>;
 export {};

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/logic.js

@@ -10,14 +10,14 @@ import { createFormattedStatWithTokenCount, logger, retryWithDelay, } from "../.
  * - 'markdown': Returns the raw Markdown content as a string.
  * - 'json': Returns a structured NoteJson object including content, frontmatter, tags, and stats.
  */
-const ReadFileFormatSchema = z
+const ReadNoteFormatSchema = z
     .enum(["markdown", "json"])
     .default("markdown")
     .describe("Specifies the format for the returned content ('markdown' or 'json'). Defaults to 'markdown'.");
 /**
- * Zod schema for validating the input parameters of the 'obsidian_read_file' tool.
+ * Zod schema for validating the input parameters of the 'obsidian_read_note' tool.
  */
-export const ObsidianReadFileInputSchema = z
+export const ObsidianReadNoteInputSchema = z
     .object({
     /**
      * The vault-relative path to the target file (e.g., "Folder/My Note.md").
@@ -34,7 +34,7 @@ export const ObsidianReadFileInputSchema = z
      * 'json' returns a structured NoteJson object containing content, parsed frontmatter, tags, and file metadata (stat).
      * Defaults to 'markdown'.
      */
-    format: ReadFileFormatSchema.optional() // Optional, defaults to 'markdown' via ReadFileFormatSchema
+    format: ReadNoteFormatSchema.optional() // Optional, defaults to 'markdown' via ReadNoteFormatSchema
         .describe("Format for the returned content ('markdown' or 'json'). Defaults to 'markdown'."),
     /**
      * If true and the requested format is 'markdown', includes formatted file statistics
@@ -59,18 +59,18 @@ export const ObsidianReadFileInputSchema = z
  * internally to access file statistics. Finally, it formats the response
  * according to the requested format ('markdown' or 'json') and the 'includeStat' flag.
  *
- * @param {ObsidianReadFileInput} params - The validated input parameters.
+ * @param {ObsidianReadNoteInput} params - The validated input parameters.
  * @param {RequestContext} context - The request context for logging and correlation.
  * @param {ObsidianRestApiService} obsidianService - An instance of the Obsidian REST API service.
- * @returns {Promise<ObsidianReadFileResponse>} A promise resolving to the structured success response
+ * @returns {Promise<ObsidianReadNoteResponse>} A promise resolving to the structured success response
  *   containing the file content and optionally formatted statistics.
  * @throws {McpError} Throws an McpError if the file cannot be found (even with fallback),
  *   if there's an ambiguous fallback match, or if any other API interaction fails.
  */
-export const processObsidianReadFile = async (params, context, obsidianService) => {
+export const processObsidianReadNote = async (params, context, obsidianService) => {
     const { filePath: originalFilePath, format: requestedFormat, includeStat, } = params;
     let effectiveFilePath = originalFilePath; // Track the actual path used (might change during fallback)
-    logger.debug(`Processing obsidian_read_file request for path: ${originalFilePath}`, { ...context, format: requestedFormat, includeStat });
+    logger.debug(`Processing obsidian_read_note request for path: ${originalFilePath}`, { ...context, format: requestedFormat, includeStat });
     const shouldRetryNotFound = (err) => err instanceof McpError && err.code === BaseErrorCode.NOT_FOUND;
     try {
         let noteJson;

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/registration.d.ts

@@ -1,7 +1,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.js";
 /**
- * Registers the 'obsidian_read_file' tool with the MCP server.
+ * Registers the 'obsidian_read_note' tool with the MCP server.
  *
  * This tool retrieves the content and optionally metadata of a specified file
  * within the user's Obsidian vault. It supports specifying the output format
@@ -17,4 +17,4 @@ import { ObsidianRestApiService } from "../../../services/obsidianRestAPI/index.
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export declare const registerObsidianReadFileTool: (server: McpServer, obsidianService: ObsidianRestApiService) => Promise<void>;
+export declare const registerObsidianReadNoteTool: (server: McpServer, obsidianService: ObsidianRestApiService) => Promise<void>;

package/dist/mcp-server/tools/{obsidianReadFileTool → obsidianReadNoteTool}/registration.js

@@ -1,8 +1,8 @@
 import { BaseErrorCode, McpError } from "../../../types-global/errors.js";
 import { ErrorHandler, logger, requestContextService, } from "../../../utils/index.js";
-import { ObsidianReadFileInputSchema, processObsidianReadFile, } from "./logic.js";
+import { ObsidianReadNoteInputSchema, processObsidianReadNote, } from "./logic.js";
 /**
- * Registers the 'obsidian_read_file' tool with the MCP server.
+ * Registers the 'obsidian_read_note' tool with the MCP server.
  *
  * This tool retrieves the content and optionally metadata of a specified file
  * within the user's Obsidian vault. It supports specifying the output format
@@ -18,26 +18,26 @@ import { ObsidianReadFileInputSchema, processObsidianReadFile, } from "./logic.j
  * @returns {Promise<void>} A promise that resolves when the tool registration is complete or rejects on error.
  * @throws {McpError} Throws an McpError if registration fails critically.
  */
-export const registerObsidianReadFileTool = async (server, obsidianService) => {
-    const toolName = "obsidian_read_file";
+export const registerObsidianReadNoteTool = async (server, obsidianService) => {
+    const toolName = "obsidian_read_note";
     const toolDescription = "Retrieves the content and metadata of a specified file within the Obsidian vault. Tries the exact path first, then attempts a case-insensitive fallback. Returns an object containing the content (markdown string or full NoteJson object based on 'format'), and optionally formatted file stats ('stats' object with creationTime, modifiedTime, tokenCountEstimate). Use 'includeStat: true' with 'format: markdown' to include stats; stats are always included with 'format: json'.";
     // Create a context specifically for the registration process.
     const registrationContext = requestContextService.createRequestContext({
-        operation: "RegisterObsidianReadFileTool",
+        operation: "RegisterObsidianReadNoteTool",
         toolName: toolName,
-        module: "ObsidianReadFileRegistration", // Identify the module
+        module: "ObsidianReadNoteRegistration", // Identify the module
     });
     logger.info(`Attempting to register tool: ${toolName}`, registrationContext);
     // Wrap the registration logic in a tryCatch block for robust error handling during server setup.
     await ErrorHandler.tryCatch(async () => {
         // Use the high-level SDK method `server.tool` for registration.
         // It handles schema generation from the shape, basic validation, and routing.
-        server.tool(toolName, toolDescription, ObsidianReadFileInputSchema.shape, // Provide the Zod schema shape for input definition.
+        server.tool(toolName, toolDescription, ObsidianReadNoteInputSchema.shape, // Provide the Zod schema shape for input definition.
         /**
-         * The handler function executed when the 'obsidian_read_file' tool is called by the client.
+         * The handler function executed when the 'obsidian_read_note' tool is called by the client.
          *
-         * @param {ObsidianReadFileInput} params - The input parameters received from the client,
-         *   validated against the ObsidianReadFileInputSchema shape. Note: The handler receives the raw input;
+         * @param {ObsidianReadNoteInput} params - The input parameters received from the client,
+         *   validated against the ObsidianReadNoteInputSchema shape. Note: The handler receives the raw input;
          *   stricter validation against the full schema should happen inside if needed, though in this case,
          *   the shape and the full schema are identical.
          * @returns {Promise<CallToolResult>} A promise resolving to the structured result for the MCP client,
@@ -48,7 +48,7 @@ export const registerObsidianReadFileTool = async (server, obsidianService) => {
             // Create a specific context for this handler invocation.
             const handlerContext = requestContextService.createRequestContext({
                 parentContext: registrationContext, // Link to registration context
-                operation: "HandleObsidianReadFileRequest",
+                operation: "HandleObsidianReadNoteRequest",
                 toolName: toolName,
                 params: {
                     // Log key parameters for debugging
@@ -63,7 +63,7 @@ export const registerObsidianReadFileTool = async (server, obsidianService) => {
                 // Delegate the actual file reading logic to the dedicated processing function.
                 // Pass the (already shape-validated) parameters, context, and the Obsidian service.
                 // The process function handles the refined validation internally if needed, but here shape = refined.
-                const response = await processObsidianReadFile(params, // Pass params directly as shape matches refined schema
+                const response = await processObsidianReadNote(params, // Pass params directly as shape matches refined schema
                 handlerContext, obsidianService);
                 logger.debug(`'${toolName}' processed successfully`, handlerContext);
                 // Format the successful response object from the logic function into the required MCP CallToolResult structure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-mcp-server",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing notes, tags, and frontmatter, acting as a bridge to the Obsidian Local REST API plugin.",
   "main": "dist/index.js",
   "files": [
@@ -26,10 +26,10 @@
     "start": "node dist/index.js",
     "start:stdio": "MCP_LOG_LEVEL=debug MCP_TRANSPORT_TYPE=stdio node dist/index.js",
     "start:http": "MCP_LOG_LEVEL=debug MCP_TRANSPORT_TYPE=http node dist/index.js",
-    "rebuild": "ts-node --esm scripts/clean.ts && npm run build",
-    "fetch:spec": "ts-node --esm scripts/fetch-openapi-spec.ts",
+    "rebuild": "npx ts-node --esm scripts/clean.ts && npm run build",
+    "fetch:spec": "npx ts-node --esm scripts/fetch-openapi-spec.ts",
     "docs:generate": "typedoc --tsconfig ./tsconfig.typedoc.json",
-    "tree": "ts-node --esm scripts/tree.ts",
+    "tree": "npx ts-node --esm scripts/tree.ts",
     "format": "prettier --write \"**/*.{ts,js,json,md,html,css}\"",
     "inspect": "mcp-inspector --config mcp.json",
     "inspect:stdio": "mcp-inspector --config mcp.json --server obsidian-mcp-server-stdio",