Obsidian Turbocharged MCP Server

What the code does

We read the source, 5 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

          `that directory ("rm -rf ${lockDir}") and retry.`,

const METADATA_IPV4 = new Set(["169.254.169.254", "100.100.100.200"]);

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      execFile(

    const abs = path.join(v.root, input.path);

            `SELECT id, rejudged_at AS at FROM contradictions WHERE id IN (${group.map(() => "?").join(",")})`,

# hadolint ignore=DL3066
USER root

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add obsidian-tc -e 'OBSIDIAN_TC_CONFIG=<OBSIDIAN_TC_CONFIG>' -- npx -y obsidian-tc

{
  "mcpServers": {
    "obsidian-tc": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ],
      "env": {
        "OBSIDIAN_TC_CONFIG": "<OBSIDIAN_TC_CONFIG>"
      }
    }
  }
}

[mcp_servers.obsidian-tc]
command = "npx"
args = ["-y", "obsidian-tc"]
env = { OBSIDIAN_TC_CONFIG = "<OBSIDIAN_TC_CONFIG>" }

{
  "mcpServers": {
    "obsidian-tc": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ],
      "env": {
        "OBSIDIAN_TC_CONFIG": "<OBSIDIAN_TC_CONFIG>"
      }
    }
  }
}

{
  "servers": {
    "obsidian-tc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ],
      "env": {
        "OBSIDIAN_TC_CONFIG": "<OBSIDIAN_TC_CONFIG>"
      }
    }
  }
}

Put your own value in place of <OBSIDIAN_TC_CONFIG> (Absolute path to the obsidian-tc JSON config (vaults, ACL, transports). May also be passed as the first CLI argument). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: OBSIDIAN_TC_DEFAULT_VAULT (Optional id of the vault to bind tool calls to when a request omits one).