MCP server · pre-built binaries

Wire your
agent in.

The Faultline MCP server lets Claude Code, Cursor, Windsurf, or any MCP-aware editor list issues, fetch diagnostic context, and mark bugs resolved — all against your faultline.live project.

1. Download

Source release is in the pipeline; until then, grab a pre-built binary built straight from the deploy. Version: latest.

macOS / Linux one-liner:

terminal
curl -fsSL https://faultline.live/mcp/install.sh | bash

2. Get an API token

The MCP server authenticates with a per-account fl_ token. Mint one at Account → API tokens after you sign in. Tokens are scoped to your account's project visibility — same as the dashboard.

3. Configure your editor

MCP-aware editors look for a server config file. Same shape across Cursor, Claude Code, and Windsurf — copy this and adjust the command path to wherever you saved the binary.

.mcp.json (Claude Code) / mcp.json (Cursor)
{ "mcpServers": { "faultline": { "command": "/usr/local/bin/faultline-mcp", "env": { "FAULTLINE_API_TOKEN": "fl_…", "FAULTLINE_BASE_URL": "https://faultline.live" } } } }

Optional: drop a .faultline.json file in any repo with a project_id field, and the MCP server will auto-scope to that project. Otherwise it tries the FAULTLINE_PROJECT_ID env var, then a git-remote lookup against your faultline projects.

4. Use it

Once your editor restarts with the config above, your agent has these tools:

Ask your agent something like "what's broken on faultline?" and it'll start pulling issues. From there you can have it diagnose, write a fix, run your tests, and call mark_resolved when the fix is verified.

Already wired in?

Add Gas Town for autonomous agents that pick up beads, fix, merge, and verify without you driving.