meta-setup

meta-setup is a command for Claude Code from tboome33/obsidian-mcp-router. It costs 44 tokens per session (1,631 once invoked), scanned B, original, Apache-2.0.

An installation command for setting up obsidian-mcp-router, a tool that connects Claude to one or more Obsidian vaults. Obsidian is a note-taking app that stores linked notes in vaults.

In plain words
What is it for?
Use it to install the router, configure multi-vault Obsidian access, and replace existing Obsidian MCP entries.
Why use it?
It replaces several separate Obsidian connections with one user-level router, reducing the setup needed when working with multiple vaults.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the obsidian-router plugin — 48 skills, 53 commands, 2 agents, 3 hooks, 1 MCP server shipped together

Good fit Use it to install the router, configure multi-vault Obsidian access, and replace existing Obsidian MCP entries.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/tboome33/obsidian-mcp-router/meta-setup
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/tboome33/obsidian-mcp-router

Made for: Claude Code.

Or install obsidian-router, the plugin that ships this one along with the rest of its 48 skills, 53 commands, 2 agents, 3 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for meta-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-setup/github.svg)](https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-setup)
Your own site
<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-setup"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meta-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-setup"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,631 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01631
Opus 5 $0.00022 $0.00816
Sonnet 5 $0.00009 $0.00326
Haiku 4.5 $0.00004 $0.00163

Measured 6d ago against content hash 1db1afa9b3e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

meta-setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

To get `/obsidian-router:*` slash commands (vault discovery, reads, writes, etc.), enable the plugin shipped in the same repo. Add to `~/.claude/settings.json`:
commands/meta-setup.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

meta-setup

Walks the user through installing obsidian-mcp-router and replacing their existing obsidian-rest / obsidian-tools user-scope MCP entries with a single obsidian-router entry that routes to all configured vaults.

When to use

  • The user says: "install the router", "replace the obsidian MCP with the router", "set up multi-vault Obsidian", "add a remote vault to Claude".
  • The user has more than one Obsidian vault (or plans to) and doesn't want to maintain one MCP entry per vault.

Pre-requisites to verify

  1. node --version ≥ 18.
  2. ~/.claude/obsidian-mcp-router/config.json exists with at least one entry in portRegistry. If not, run node <router-repo>/scripts/setup-vault.mjs <vault-path> first.
  3. Obsidian is installed and at least one vault has the Local REST API + MCP Router Bridge plugins activated.

Install steps

# 1. Clone (pick a destination that fits your workflow — examples below).
#    Linux/macOS:
git clone https://github.com/tboome33/obsidian-mcp-router.git ~/dev/obsidian-mcp-router
cd ~/dev/obsidian-mcp-router
#    Windows (PowerShell):
#    git clone https://github.com/tboome33/obsidian-mcp-router.git "$env:USERPROFILE\dev\obsidian-mcp-router"
#    cd "$env:USERPROFILE\dev\obsidian-mcp-router"

# 2. Install dependencies + create global symlink
npm install
npm link

# 3. Verify the binary is callable
obsidian-mcp-router --version

Ask the user upfront which directory they prefer if it's not obvious. Don't pick a destination on their behalf — clone paths are a personal taste thing.

Register in Claude (user scope)

Edit ~/.claude.json. Find the mcpServers section, remove the existing obsidian-rest and obsidian-tools entries (the router replaces both for REST-level operations), and add:

"obsidian-router": {
  "type": "stdio",
  "command": "obsidian-mcp-router"
}

To get /obsidian-router:* slash commands (vault discovery, reads, writes, etc.), enable the plugin shipped in the same repo. Add to ~/.claude/settings.json:

Read the full file on GitHub · 134 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago Changed · +42 lines 1db1afa9b3e2
  2. 9d ago First seen · 92 lines · 44 tokens per session scan B 576560657145

Subscribe to this mod's changes

meta-setup is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 1,631 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.