What problem does it solve? AI clients like Claude Code, Codex, VS Code/Copilot, and Kiro need a running MCP server to query a Fux knowledge index, but configuring the launch command, working directory, and output defaults correctly is error-prone and often results in a server that connects but shows no tools. ## Core Features & Use Cases - Three MCP tools: fux_search returns ranked documents with a confidence band, fux_passage reads line spans from indexed files, and fux_related lists a document's inbound and outbound links including supersedes and tags. - Client registration guidance: Provides tested command configurations for Claude Code (.mcp.json), Codex (config.toml), VS Code (.vscode/mcp.json), and Kiro, including the PATH ladder problem where a client's environment differs from your shell. - Troubleshooting table: Maps symptoms like "command not found", missing [mcp] top config, and connected-but-no-tools to concrete fixes. - Use Case: You want your coding agent to search your team's committed runbook index. Register uv run fux mcp as a project-scope MCP server, verify it with a JSON-RPC initialize test, and the agent gains fux_search, fux_passage, and fux_related tools. ## Quick Start Register fux as a project-scope MCP server in Claude Code by running "claude mcp add --scope project fux -- uv run fux mcp" from the repository root.