Synapse

Read a file from the Obsidian vault. Returns the full content including frontmatter.

Write or overwrite a file in the Obsidian vault. Creates parent directories automatically. Use this to create new wiki pages, update existing ones, or save any markdown content.

List markdown files in the vault or a subdirectory. Returns relative paths.

Search the vault for files containing a text query. Returns matching files with line numbers and context. Case-insensitive.

Get vault statistics: file counts, folder structure, and whether the knowledge base has been initialized.

Read the YAML frontmatter metadata from a vault file. Returns parsed key-value pairs (title, tags, date, status, etc.).

Save content to the vault's sources folder from a URL or pasted text. Ideal for mobile users who find articles and want to save them without a web clipper.

If a URL is provided, fetches the page and converts it to markdown. If content is provided directly, saves it as-is. Always adds frontmatter with metadata.

One-shot status overview. Returns everything needed to understand the vault state: configuration, file counts, recent activity, CLAUDE.md schema, and suggested next actions. This is THE tool to call when a user first connects or asks "what can you do?"

Process a source file into the knowledge base. Reads the source, generates organized pages (summaries, concepts, entities), adds [[wikilinks]], and updates the index and log.

You MUST read the source file content first, then generate all pages. Follow the CLAUDE.md schema in the vault root for conventions and folder paths.

Steps:

1. Read the source file

2. Create a summary page in the configured notes folder

3. For each key concept: create/update a concept page

4. For each key entity: create/update an entity page

5. Add [[wikilinks]] connecting related pages

6. Update the index

7. Append to the log

Scan for all unprocessed sources and compile them into organized pages. Lists which sources exist in the sources folder but don't have corresponding summaries yet. Use synapse_ingest on each one to process them.

Research a question against the knowledge base. Reads the index, identifies relevant pages, and returns their content so you can synthesize an answer. You MUST save the synthesized answer to the outputs folder using vault_write after responding.

Health-check the knowledge base. Scans for contradictions, orphan pages, broken wikilinks, missing frontmatter, stale content, and missing pages. Returns a report and instructions for fixing issues.

Onboarding entry point for Synapse. Scans the vault to detect existing structure, conventions, and CLAUDE.md, then returns configuration options for the user to choose from:

• Option A: Use existing vault conventions (adapts to what's already there)

• Option B: Set up a structured knowledge base (organized folders for a specific topic)

• Option C: Start fresh with custom settings

After the user chooses, call synapse_configure with their selection.

Save Synapse configuration based on the user's choice from synapse_setup. Three modes:

• "existing": Auto-detect conventions from the vault and save config. No folders created.

• "structured": Set up an organized knowledge base (creates sources/, notes/, CLAUDE.md). Requires a topic.

• "custom": Save whatever folder paths and conventions the user specified.

Initialize a structured knowledge base in the vault. Creates the folder structure, generates CLAUDE.md with the schema, and creates the initial index and log files. Safe to run on an existing vault — won't overwrite existing files.

For new vaults only. If you have an existing vault, use synapse_setup instead — it detects your conventions and adapts.