feat(mcp): add OpenCode ingest readiness checks
Expose a check_ingest_opencode_readiness MCP tool for remote operators and run the same static preflight before launching OpenCode ingest jobs. The preflight validates the OpenCode binary, required run flags, project AGENTS/skill context files, and can run a no-write smoke test that proves wiki-ingest loads successfully. Document the remote ingest workflow and clarify that wiki-file-assets is tool-first, so empty resources/prompts lists are not a failure signal. Validation: python3 -m unittest discover -v; python3 -m py_compile obsidian_wiki/mcp_ingest.py obsidian_wiki/mcp_server.py tests/test_mcp_ingest.py tests/test_mcp_server_remote.py; git diff --check; real OpenCode smoke test passed with opencode 1.17.13.
This commit is contained in:
@@ -52,6 +52,9 @@ OBSIDIAN_MCP_PATH=/mcp
|
||||
# Optional write-capable MCP ingest tools. Default is disabled.
|
||||
# When enabled, remote MCP clients sharing this token can upload files and
|
||||
# trigger a local `opencode run --auto` wiki-ingest job for those uploads.
|
||||
# After enabling, call the MCP tool `check_ingest_opencode_readiness` before
|
||||
# the first upload; set run_smoke_test=true to verify OpenCode can load the
|
||||
# project wiki-ingest skill without editing files.
|
||||
# Keep this runtime root outside OBSIDIAN_VAULT_PATH; uploads are staging inputs,
|
||||
# and wiki-ingest decides how sources are archived into the vault.
|
||||
OBSIDIAN_MCP_ENABLE_INGEST=0
|
||||
|
||||
Reference in New Issue
Block a user