MCP Server Setup

This guide shows you how to install and configure the Noteriv MCP server with different AI assistants.

Quick Start with Claude Code

The fastest way to get started is with Claude Code. Run this single command:

claude mcp add --scope user noteriv -- npx -y noteriv-mcp

This registers the Noteriv MCP server as a user-scoped tool in Claude Code. The npx -y flag downloads and runs the latest version of noteriv-mcp from npm automatically. The server will start whenever Claude Code needs it and stop when the session ends.

After adding the server, you can immediately ask Claude to interact with your notes:

> Read my note at Projects/roadmap.md
> Search my vault for "API design"
> Create a daily note with today's tasks

Claude Desktop

To use the Noteriv MCP server with Claude Desktop, add it to your MCP configuration file.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

Add the following to the mcpServers section:

{
  "mcpServers": {
    "noteriv": {
      "command": "npx",
      "args": ["-y", "noteriv-mcp"]
    }
  }
}

Restart Claude Desktop after saving the configuration.

Cursor

To use with Cursor, add the Noteriv MCP server to your Cursor MCP configuration. Open Cursor Settings, navigate to the MCP section, and add a new server:

{
  "mcpServers": {
    "noteriv": {
      "command": "npx",
      "args": ["-y", "noteriv-mcp"]
    }
  }
}

Alternatively, create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "noteriv": {
      "command": "npx",
      "args": ["-y", "noteriv-mcp"]
    }
  }
}

Windsurf

For Windsurf, add the server to your MCP configuration at ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "noteriv": {
      "command": "npx",
      "args": ["-y", "noteriv-mcp"]
    }
  }
}

Running from Source

If you have cloned the Noteriv repository and want to run the MCP server from source:

cd Noteriv/mcp
npm install
node index.js

To use the source version with Claude Code:

claude mcp add --scope user noteriv -- node /path/to/Noteriv/mcp/index.js

Specifying a Vault Path

By default, the MCP server auto-discovers your vaults from the Noteriv desktop app's configuration file. If you want to point it at a specific vault directory instead, pass the path as a command-line argument:

# Run directly with a specific vault
node index.js /path/to/my-vault

# Or via npx
npx -y noteriv-mcp /path/to/my-vault

To configure this in Claude Code:

claude mcp add --scope user noteriv -- npx -y noteriv-mcp /path/to/my-vault

Or in a JSON config file:

{
  "mcpServers": {
    "noteriv": {
      "command": "npx",
      "args": ["-y", "noteriv-mcp", "/path/to/my-vault"]
    }
  }
}

Vault Auto-Discovery

When no vault path is provided as a command-line argument, the server reads the Noteriv configuration file to find your vaults. The config file is located at:

The configuration file contains a list of vaults with their names, paths, and IDs, along with the ID of the currently active vault. The server uses the active vault by default.

If the configuration file does not exist or contains no vaults, the server starts without a vault. You can then use the set_vault_path or switch_vault tools to configure a vault at runtime.

Switching Vaults at Runtime

Even after the server starts, you can switch between vaults using the switch_vault tool:

> Switch to my "Work" vault

The AI assistant will call switch_vault with the vault name, and all subsequent operations will target the new vault. You can also use list_vaults to see all available vaults and get_active_vault to check which one is currently selected.

Verifying the Connection

After setting up the MCP server, verify that it is working by asking your AI assistant to list your vaults:

> List my Noteriv vaults

You should see a list of your vault names and paths. If you see an error, check that:

1. Node.js 18+ is installed and available in your PATH.
2. The Noteriv desktop app has been opened at least once (to create the config file).
3. Your vault path exists and contains markdown files.

Troubleshooting

"No active vault" error

The server could not find a vault. Either the Noteriv config file does not exist, or it does not contain any vaults. Solutions:

• Open the Noteriv desktop app and create or open a vault.
• Pass a vault path explicitly: npx -y noteriv-mcp /path/to/vault.
• Use the set_vault_path tool at runtime.

Server does not start

Make sure npx is available in your PATH. Run npx --version in your terminal to verify. If npx is not found, install Node.js from nodejs.org.

Tools are not showing up

Some AI assistants cache the tool list. Restart the AI assistant or reload the MCP configuration. In Claude Code, run claude mcp list to verify that the noteriv server is registered.