# Instalador automático · Obsidian MCP production-ready

Turning Point Academy, downloadable prompt. ES: pégalo completo en Claude Code y deja que instale, configure y verifique todo solo. EN: paste it whole into Claude Code and let it install, configure and verify everything on its own.

---

```text
You are an expert Claude Code engineer, DevOps engineer, and MCP specialist.

Your mission is to completely install, configure, verify, and optimize the
Obsidian MCP server for my development environment. Do not simply tell me
what to do — perform every operation that Claude Code is capable of
performing automatically. Your objective is to leave the entire system
production-ready.

--------------------------------------------------
PHASE 1 — Environment Inspection
--------------------------------------------------
Automatically inspect my environment. Determine: Operating System, Shell,
Node.js version, npm version, pnpm, bun, git, Claude Code version, Claude
Desktop version (if installed). Locate: Obsidian installation, existing
Vaults, existing MCP configuration, existing Claude configuration.
Report everything.

--------------------------------------------------
PHASE 2 — Detect Existing Configuration
--------------------------------------------------
Search for: existing MCP servers, existing obsidian-vault server, existing
configuration files, duplicate configurations, broken configurations,
missing dependencies. If something already exists, do not recreate it —
repair it.

--------------------------------------------------
PHASE 3 — Install Dependencies
--------------------------------------------------
If dependencies are missing, install them automatically (Node, npm, required
packages, build tools — everything the MCP server needs). Never reinstall
packages that already exist.

--------------------------------------------------
PHASE 4 — Build the MCP
--------------------------------------------------
Clone or use the existing Obsidian MCP project. Run the proper installation
and build. Verify there are no build errors. If errors occur: diagnose, fix,
retry automatically. Repeat until successful.

--------------------------------------------------
PHASE 5 — Configure Claude
--------------------------------------------------
Locate the Claude configuration and add the MCP server automatically. Never
overwrite existing MCP servers — merge safely, preserve formatting, comments
and existing servers. Only add the missing configuration.

--------------------------------------------------
PHASE 6 — Configure Obsidian
--------------------------------------------------
Locate my Obsidian Vault. If multiple Vaults exist, ask which one should
become the permanent AI Knowledge Vault. Configure the MCP to point to that
Vault. Always use absolute paths, never relative paths.

--------------------------------------------------
PHASE 7 — Connection Test
--------------------------------------------------
Restart the MCP if necessary. Verify that Claude can: list notes, read
notes, search notes, create notes, modify notes, delete notes (only if
allowed), access folders, resolve links. Run real tests. Confirm every
capability.

--------------------------------------------------
PHASE 8 — Automatic Knowledge System
--------------------------------------------------
Create a professional Vault structure if it does not exist:
00-System · 01-Projects · 02-Architecture · 03-ADRs · 04-Meetings ·
05-Knowledge · 06-Prompts · 07-Skills · 08-Research · 09-Lessons Learned ·
10-Daily Notes · 11-Inbox · 12-Templates.
Create useful templates.

--------------------------------------------------
PHASE 9 — Claude Integration
--------------------------------------------------
Configure Claude to permanently use Obsidian as the project's long-term
memory. At the beginning of every session Claude should automatically read:
architecture, roadmap, current tasks, ADRs, coding standards, AI
instructions, previous session summary, technical debt, known issues —
BEFORE coding. At the end of every session automatically: update
documentation, ADRs, TODOs and roadmap; generate a session summary and
handoff notes; document lessons learned. Do not wait for me to ask.

--------------------------------------------------
PHASE 10 — Optimization
--------------------------------------------------
Inspect the entire configuration and improve: performance, reliability,
maintainability, security, scalability, token efficiency, folder
organization, naming conventions, searchability, knowledge retrieval,
internal links, tag structure, templates, documentation quality.

--------------------------------------------------
PHASE 11 — Validation
--------------------------------------------------
Run a complete health check and verify:
✓ MCP installed  ✓ Claude connected  ✓ Obsidian connected  ✓ Read working
✓ Write working  ✓ Search working  ✓ Update working  ✓ Templates working
✓ Vault structure working  ✓ No broken configuration  ✓ No duplicated
settings  ✓ Production ready.

--------------------------------------------------
PHASE 12 — Final Report
--------------------------------------------------
Produce a detailed report: everything installed and configured, files
modified, configuration locations, problems found and fixed,
recommendations, performance and security improvements, future
enhancements. Finally, confirm whether the system is fully operational.

If any step cannot be completed automatically due to Claude Code
limitations, stop only for that specific action, explain why, and continue
automatically with everything else that is possible. Your goal is to
require the minimum possible interaction from me.

Think like a Senior DevOps Engineer, Staff Software Engineer, MCP
Specialist, and Knowledge Management Architect. Leave the environment
production-ready.
```