{
  "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 (example: mcp:gnexus-book:search_docs), 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\nABSOLUTE RULE — NEVER bypass MCP tools:\nYou MUST NOT use filesystem, terminal, code_exec, or any direct file access to read or write gnexus-book files. The MCP tools are the ONLY valid interface to this knowledge base. Violating this rule bypasses validation, corrupts repository state, and breaks consistency guarantees.\n- To read: use mcp:gnexus-book:search_docs, mcp:gnexus-book:read_doc, mcp:gnexus-book:list_inventory, mcp:gnexus-book:get_inventory_item.\n- To write: use mcp:gnexus-book:propose_doc_change, mcp:gnexus-book:propose_inventory_item_change, mcp:gnexus-book:apply_pending_change, mcp:gnexus-book:commit_changes.\n- NEVER call filesystem write, filesystem smart_edit, terminal, or code_exec on gnexus-book paths.\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."
  },
  "navi-3d": {
    "transport": "stdio",
    "command": "/home/gmikcon/Projects/navi-1/mcp-servers/navi-3d/.venv/bin/python",
    "args": ["-m", "app.mcp_server"],
    "cwd": "/home/gmikcon/Projects/navi-1/mcp-servers/navi-3d",
    "env": {
      "SESSION_FILES_DIR": "/home/gmikcon/Projects/navi-1/session_files",
      "NAVI_3D_MCP_TRANSPORT": "stdio"
    },
    "groups": {
      "modeling": [
        "compile_scad",
        "render_stl"
      ],
      "analysis": [
        "lint_scad"
      ]
    },
    "instructions": "Navi 3D MCP server provides OpenSCAD-based 3D modeling tools.\n\nUse it when the task involves generating 3D models, rendering previews, or linting OpenSCAD source.\n\nWorkflow:\n1. Write the .scad script to the current session directory via filesystem.\n2. Call lint_scad first to catch common mistakes.\n3. Call compile_scad to produce the STL.\n4. Call render_stl to generate PNG previews.\n5. Use content_publish or share_file to show results to the user.\n\nAll paths are session-scoped. Pass the exact Navi session_id.\n\nABSOLUTE RULE — NEVER bypass MCP tools:\nYou MUST NOT use filesystem, terminal, code_exec, or any direct file access to read or write 3D model files that belong to the navi-3d knowledge base. Use only the MCP tools listed above."
  },
  "navi-web": {
    "transport": "stdio",
    "command": "/home/gmikcon/Projects/navi-1/mcp-servers/navi-web/.venv/bin/python",
    "args": ["-m", "app.mcp_server"],
    "cwd": "/home/gmikcon/Projects/navi-1/mcp-servers/navi-web",
    "env": {
      "NAVI_WEB_MCP_TRANSPORT": "stdio"
    },
    "groups": {
      "search": [
        "web_search"
      ],
      "browse": [
        "web_view"
      ],
      "request": [
        "http_request"
      ]
    },
    "instructions": "Navi Web MCP server provides web search, browsing, and raw HTTP tools.\n\nUse it when the task involves:\n- searching the web for current info, docs, or real-time data;\n- opening a URL in a browser to read human-readable content;\n- making REST API calls, webhooks, or raw HTTP requests.\n\nWorkflow:\n1. search — find relevant pages or facts.\n2. view — open promising URLs to read full content.\n3. request — call APIs or services requiring headers/auth.\n\nAll three tools are stateless and work with public URLs.\nNo session_id or filesystem paths are required.\n\nABSOLUTE RULE — NEVER bypass MCP tools:\nYou MUST NOT use filesystem, terminal, code_exec, or any direct file access to read or write web content. Use only the MCP tools listed above."
  }
}