{
  "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.\n\nUse only gnexus-book tool names that are present in the current tool schema. In Navi they are exposed with the mcp_gnexus-book_ prefix, but each profile may expose only some groups. Do not invent or call gnexus-book tools that are not in the current tool list.\n\nQuery mapping by capability:\n- Status or facts about a server/service → search docs first, then read a specific doc or inventory item if those tools are available.\n- Service placement or topology → list inventory and relationships if available.\n- Documentation changes → read the target doc first, then propose a doc or inventory change if write tools are available.\n- Freshness questions → use freshness checks if available.\n- Repository validation/status → use repository tools only if they are available in the current tool schema; otherwise skip this step and continue with available read/write tools.\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\nDo 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 and gnexus-book write tools are available, persist them before answering. If write tools are not available, report the facts that should be persisted. If the fact is user-specific rather than infrastructure documentation, use the memory tool instead. Choose the target based on scope, not habit."
  }
}