{
  "gnexus-book": {
    "transport": "sse",
    "url": "http://192.168.1.170:8001/sse",
    "groups": {
      "read": [
        "search_docs",
        "read_doc",
        "list_docs",
        "list_inventory",
        "get_inventory_item",
        "get_relationships",
        "check_freshness"
      ],
      "write": [
        "propose_doc_change",
        "propose_inventory_item_change",
        "apply_pending_change",
        "commit_changes",
        "update_doc"
      ],
      "admin": [
        "validate_repository",
        "git_status",
        "git_diff",
        "list_pending_changes"
      ]
    },
    "instructions": "MANDATORY for profiles that expose gnexus-book tools: Before answering any question about infrastructure, servers, services, networks, documentation, or system inventory, call gnexus-book tools first. In Navi, gnexus-book tools are exposed with the mcp_gnexus-book_ prefix; use the exact tool names from the current tool schema.\n\nQuery mapping:\n- 'server X not working / status' → mcp_gnexus-book_search_docs, mcp_gnexus-book_get_inventory_item\n- 'what services run where' → mcp_gnexus-book_list_inventory, mcp_gnexus-book_get_relationships\n- 'update docs / fix documentation' → mcp_gnexus-book_read_doc, mcp_gnexus-book_propose_doc_change, mcp_gnexus-book_commit_changes\n- 'is X up to date / freshness' → mcp_gnexus-book_check_freshness\n- 'validate repository / repo state' → mcp_gnexus-book_validate_repository, mcp_gnexus-book_git_status\n\nDo not rely on memory for infrastructure facts. Memory is only for personal user facts and preferences. Always pull infrastructure state from gnexus-book when these tools are available to the active profile.\n\nAlways validate the repository before making changes. Do not store raw secrets in documentation.\n\nBefore the final response, decide whether tool execution revealed stable reusable infrastructure facts, service configurations, or relationships. If yes, persist them with gnexus-book write tools (mcp_gnexus-book_propose_doc_change, mcp_gnexus-book_propose_inventory_item_change) before answering. If the fact is user-specific rather than infrastructure documentation, use the memory tool instead. Choose the target based on scope, not habit."
  }
}