io.github.cyanheads/obsidian-mcp-server

The materials show it requires OBSIDIAN_API_KEY plus multiple connection and behavior configuration variables. The API key is sensitive and could be abused to access the associated Obsidian service if leaked; however, the requested credential appears aligned with the stated functionality, with no obvious overreach.

The system check shows no declared fixed remote host, but the presence of OBSIDIAN_BASE_URL and OBSIDIAN_OMNISEARCH_URL indicates it can send requests to user-configured Obsidian/search endpoints. This egress is consistent with the tool’s purpose, and the provided materials do not show data being sent to unrelated or unknown third-party endpoints.

The system marks it as executes-code, and OBSIDIAN_ENABLE_COMMANDS suggests it may trigger local commands or related execution capabilities. For an MCP tool this is a standard capability that warrants caution, but the available materials do not show concrete red flags such as unrelated privilege use or a suspicious execution chain.

The description explicitly supports reading, writing, searching, and surgically editing notes, tags, and frontmatter, and includes scope controls such as OBSIDIAN_READ_PATHS, OBSIDIAN_WRITE_PATHS, and OBSIDIAN_READ_ONLY. The data-access surface is broad but consistent with the stated purpose, and exposure can be reduced through read-only mode and path restrictions; no clear evidence of over-privileged access is shown.

It comes from an official registry, the repository is open source and auditable, it has about 590 stars, and it has been updated within the last year—these are strong positive supply-chain indicators. The missing license declaration slightly reduces transparency, but based on the available facts it does not justify a high-risk rating.