Made changes to support multiple vaults in Obsidian MCP Server plugin

[mbelinky]

I've made changes to your code to accept multiple vaults.

[netlify]

✅ Deploy Preview for superb-starlight-b5acb5 canceled.

Name	Link
🔨 Latest commit	d1859f1
🔍 Latest deploy log	https://app.netlify.com/projects/superb-starlight-b5acb5/deploys/6849451dd7154b0008ad85fb

[jacksteamdev]

Thanks for making this PR! Multiple vault support will be vaulable for lots of people. These changes are a step in the right direction.

I have two concerns with this PR as-is:

1. I wasn't able to get this PR working on my computer. I'm not sure what's wrong, but I created vaults.json and configured MCP_VAULTS_CONFIG_PATH in claude_desktop_config.json.

2. I think the installation UX for multiple vaults will probably frustrate typical non-technical users.

One of the main goals for an Obsidian plugin is to require little-to-no manual setup. Users should be able to click a button in the options page, and everything is done automatically, or at least through the UI.

This PR introduces a vaults.json file, which makes sense from a developer perspective, but we need to make it accessible to non-technical users, which means creating vaults.json automatically and guiding them through the process of adding vaults.

I know people want multiple vault support, and I really appreciate the time and effort this feature required, but I can't merge this PR without improvements to the user experience.

[istefox]

Hi @mbelinky — heads-up that this PR will likely sit unmerged on the unmaintained upstream (per #79, declared 2026-04-24).

Multi-vault is structurally supported in the community fork istefox/obsidian-mcp-connector 0.4.0 (released 2026-05-04) by way of architecture rather than configuration: each Obsidian vault loads its own plugin instance with its own data.json, its own Bearer token, and its own port from the allow-list 27200-27205 (auto-fallback if a port is occupied). Open Vault A and Vault B in two separate Obsidian windows and they bind to two different ports automatically; configure each MCP client entry against the corresponding port + token. No env-var dance, no shared state.

If your original problem was running multiple vaults concurrently, 0.4.0 should cover it directly. Install: BRAT pointing at istefox/obsidian-mcp-connector.