fux-mcp

Serve a Fux search index over MCP with fux_search, fux_passage, and fux_related tools.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/arpitarya/fux --skill fux-mcp-arpitarya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fux-mcp
Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-mcp
Command: npx skills add https://github.com/arpitarya/fux --skill fux-mcp-arpitarya

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about fux-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add fux as an MCP server in Claude Code?▼

Run "claude mcp add --scope project fux -- uv run fux mcp" from the repository root, which writes .mcp.json. Verify with "claude mcp list" or /mcp, and approve the project server in an interactive session before its tools appear.

What tools does the fux MCP server expose?▼

The server exposes three tools: fux_search for ranked documents with a confidence band, fux_passage for reading line spans from indexed files, and fux_related for a document's inbound and outbound links. Answer synthesis, graph queries, and path routes remain CLI-only.

Why does my MCP client connect but show no fux tools?▼

The server is usually not approved or trusted in the client, is marked disabled, or Codex's start-up timeout expired while uv synced. Approve the server in the client and raise startup_timeout_sec if needed.

Why does fux mcp fail with command not found in my client?▼

The client spawns the server with its own PATH, not your shell's, so a fux that works in your terminal may be missing. Test the exact command the client will launch and use an absolute path to the fux or uv binary.

When should I use the fux CLI instead of the MCP server?▼

Use the CLI when you have a shell and need fux answer for cited answers with freshness verdicts, or fux graph and fux path for query neighbourhoods and routes. MCP only exposes search, passage reading, and related-document lookup.