Fjord
Local-first project management — Linux first, also on Windows & macOS. Built for the keyboard, friendly to the mouse, and open to AI agents.
Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
mcpb https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpbClaude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add jhtjernsmo-fjord -- mcpb https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpbIn einem Terminal ausführen.
{ "mcpServers": { "jhtjernsmo-fjord": { "command": "mcpb", "args": [ "https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpb" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Local-first project management — Linux first, also on Windows & macOS. Built for the keyboard, friendly to the mouse, and open to AI agents.
Local-first project management, Linux first, also on Windows and macOS: kanban, notes with [[links]] and files in SQLite. Keyboard-first, mouse-friendly, with a CLI and MCP server for AI agents.

Fjord keeps your projects, kanban boards, files and notes in a single SQLite database on your own machine. No account, no cloud, no telemetry. It's a lightweight native desktop app (Tauri), a scriptable CLI, and an MCP server — so you and your AI assistant can work in the same projects, and you can always see who did what.
H/L. Rename, recolor, reorder and add columns, and mark one or more as done columns (e.g. Resolved and Done). Right-click a project to change its icon and colour.Space T cycles themes.w, right-click, or the task panel). It stays in its column with a “pending 3d” badge, can be filtered on, is listed on the Overview with the longest waiting first, and shows up as a blocker in the standup. Tasks from Azure Boards follow their work item both ways: a work item set to Pending in Azure becomes pending in Fjord, and marking it pending in Fjord moves the work item there (and back when you clear it).A to add.[[Project]], [[#12]] (a task) or [[Another note]] — type [[ for autocomplete — and see backlinks (“mentioned in”) on tasks, projects and notes. Tables, task lists and Mermaid diagrams render in notes and task descriptions; web links open in your browser.Space f).Ctrl+K command palette, and every binding configurable. The mouse works for everything too.B, e.g. feat/12-add-login) or link an existing one, see pull requests with CI status, open PRs from a task, and let merged PRs move tasks to done.fjord mcp exposes 28 tools to MCP clients such as Claude Code and Cursor, and an Agent Skill teaches agents how to use them. Agents can create, edit, move and archive but never hard-delete, and every change is tagged with its author.Fjord is Linux first: that's where it's developed and used daily. Windows and macOS builds come from the same code and are tested in CI on every pull request.
Grab the installer for your system from Releases:
On macOS (and for the CLI on Linux) you can also use Homebrew:
brew install --cask jhtjernsmo/fjord/fjord # the app
brew install jhtjernsmo/fjord/fjord-cli # the `fjord` command-line tool
The CLI is attached separately as fjord-cli-<platform>. From 0.2.9 the macOS app is signed with
an Apple Developer ID and notarized, so it opens normally. Windows builds aren't code-signed yet and
may show a SmartScreen warning (More info → Run anyway).
Requirements: Rust (stable), Node.js 20+. On Linux also WebKitGTK 4.1; Windows uses the built-in WebView2, and macOS needs the Xcode command line tools.
# Arch
sudo pacman -S --needed webkit2gtk-4.1 base-devel
# Debian / Ubuntu
sudo apt install libwebkit2gtk-4.1-dev build-essential libssl-dev librsvg2-dev
# Fedora
sudo dnf install webkit2gtk4.1-devel openssl-devel librsvg2-devel
git clone https://github.com/jhtjernsmo/fjord.git
cd fjord
npm --prefix ui install
npx --prefix ui tauri build # installers for your OS in target/release/bundle
./target/release/fjord-app # run it
cargo install --path crates/fjord-cli # optional: puts `fjord` on your PATH
For development with hot reload: npx --prefix ui tauri dev.
From 0.2.1 on, Fjord checks GitHub Releases on startup and offers Update & restart (Windows, macOS and the Linux AppImage; .deb/.rpm update via your package manager). Updates are signed and verified before installing; the check can be turned off in Settings. Settings → Updates shows the installed version and has a Check now button. Versions before 0.2.1 have no updater, so install the latest release once by hand.

Press ? in the app to see every shortcut. Press the leader key (Space) and wait a moment to see
what comes next.
On the Overview: j / k move through due tasks, mentions and projects, Enter opens, a adds a
mention as a task and x dismisses it. Space G creates a GitHub repository for the current project.
Ctrl+B collapses the sidebar to icons, like in VS Code.
In an open task: [ / ] move it to the previous/next column, e edits, A adds a subtask, B
starts a branch, L links an existing one, P opens a pull request, m moves it to another project,
o pops it out into its own window and N makes it a subtask of another task (or a regular task again).
On macOS, Ctrl shortcuts use ⌘ instead. Remap anything in keymap.json (see Data for where it lives):
{
"leader": "space",
"bindings": {
"task.archive": "D",
"search.open": "<leader>/"
}
}
Action ids are listed in ui/src/keymap.ts.
fjord project add "Bokost" --icon '$'
fjord task add bokost "Fix push notifications" -p 3 --due 2026-10-10
fjord column add bokost Review
fjord task move 1 review
fjord task done 1
fjord task nest 3 1 # make #3 a subtask of #1 (unnest to undo)
fjord project show bokost # board in the terminal
fjord search push
fjord log bokost # activity
fjord --json project ls # JSON for scripts
Run fjord --help for everything. Changes are recorded with an actor: --actor, $FJORD_ACTOR or $USER.
Link a project to a repository in the Git tab (or fjord git link <project> <path>). No
repository yet? Tick Also create a repository on GitHub when you make a project, or use the Git
tab: Fjord creates it (private or public, under you or an organization, with an optional README,
.gitignore and license), clones it and links it in one step. A local repository without a remote
can be published the same way. If you aren't signed in to GitHub, you can sign in right there.
Once a project is linked, Fjord:
fix/12-fix-push-notifications. Pick the type (feat, fix, chore, docs, refactor, test, perf, ci, hotfix) in the task, or let Fjord guess: fix for bug-like tasks and Azure Bugs, feat otherwise. The task moves to the second column,feat: Add login, and the description comes from the task),Space e,If GitHub or Azure DevOps refuses access, the Git tab shows their own explanation, for example an organization that restricts OAuth apps or requires SSO approval.
Git runs through your installed git, so your config, hooks and credentials apply. GitHub access
(needed for private repositories and opening PRs) comes from, in order: GITHUB_TOKEN/GH_TOKEN, a
Sign in with GitHub in Settings (browser sign-in, OAuth device flow) or a personal access token pasted there, or gh auth login. A connected token is
checked with GitHub and kept in the OS credential store (Windows Credential Manager, macOS Keychain,
Secret Service on Linux), never in Fjord's database or files. Public repositories can be read without one.
Azure DevOps (beta). Repositories on dev.azure.com (and the older visualstudio.com URLs) are
detected the same way and get the same features: pull requests with pipeline status, a branch per
task, opening PRs from a task, and moving tasks to done when their PR completes. Auth comes from
AZURE_DEVOPS_EXT_PAT, a personal access token per organization in Settings → Azure DevOps
(scopes: Code Read & Write, Build Read; stored in the OS credential store), or the Azure CLI: add the organization in Settings without a token and Fjord uses az login.
Azure Boards import (beta). Work items assigned to you can be imported into chosen Fjord projects
(on start and every 10 minutes, no duplicates). Each item lands in the column named like its Azure
state (Active falls back to your in-progress column, New to the first), child items become subtasks,
items finished in the last 30 days (configurable) are included, and a notification tells you what
was added or changed. The task panel shows the work item's discussion. An AI agent can analyze new ones through the MCP
server (import_azure, list_new_imports, mark_analyzed). Setup, a ready-made triage prompt and
how to schedule it: docs/azure-boards-triage.md.
Pending. A work item in the state named in Settings → Integrations → Pending state
(Pending by default) is pending in Fjord. Marking an imported task pending in Fjord moves its work
item to that state, and clearing it moves the work item back to the state it had before. The state
has to exist for the work item type in your Azure process, and writing it needs permission to edit
work items (your az login, or a token with Work Items Read & Write). If Azure refuses, the task is
still marked in Fjord and Fjord tells you why. Leave the setting empty to keep pending local.
Mentions. When someone @mentions you in a work item that isn't assigned to you, the Overview shows it under Mentioned: the item, who mentioned you and what they wrote. Open it in Azure, add it to a project as a task, or dismiss it. New mentions also get a notification. This uses Azure DevOps' own "recent mentions" (the last 30 days, Azure DevOps Services only).
fjord git link bokost ~/code/bokost
fjord git branch 12 # check out (or create) the task's branch
fjord git main bokost # back to the main branch
fjord git status bokost # branches and recent commits
fjord git prs bokost # pull requests + CI; moves merged tasks to done
fjord git pr 12 --draft # push the branch and open a pull request
fjord git which # the project and task for the current folder
fjord azure import # import Azure Boards work items (same settings as the app)
fjord azure links bokost # the work items behind a project's imported tasks
fjord notes list --folder Work # notes in a folder and its subfolders
fjord notes move 7 --folder Work/Meetings # sort a note into a folder
fjord notes rename-folder Work Jobb # rename a folder and everything under it
fjord notes lock 7 on # open read-only in the app
Fjord for VS Code puts the board of the project linked to the open folder in the Explorer, and the task for the branch you're on in the status bar.
fjord CLI, without leaving VS Code#12 while you're on task 12's branchIt needs the fjord CLI 0.2.18 or later and talks to the same local database as the app. Install the .vsix from the extension's releases (code --install-extension fjord-*.vsix).

fjord mcp runs a Model Context Protocol server on stdio. Changes it
makes are recorded as claude (override with --actor) and shown with an AI tag in the app.
Claude Desktop: download fjord-mcp.mcpb from the latest release
and open it; Claude Desktop installs Fjord as an extension, with the command-line tool included (macOS on Apple
Silicon, Windows and Linux). Fjord is also listed in the MCP Registry as
io.github.jhtjernsmo/fjord.
Other clients need the fjord command-line tool on your PATH (see Install). With Claude Code:
claude mcp add fjord -- fjord mcp
Cursor (~/.cursor/mcp.json) and other clients:
{ "mcpServers": { "fjord": { "command": "fjord", "args": ["mcp"] } } }
Tools: list_projects, get_board, create_project, create_task, get_task, update_task, move_task,
complete_task, set_task_pending, archive_task, add_note, attach_file, search, recent_activity, link_repo,
git_status, start_branch, link_branch, list_pull_requests, open_pull_request, list_notes, get_note, update_note, backlinks, analyze_story, import_azure, list_new_imports, mark_analyzed. There is deliberately no
delete tool.
The MCP tools say what each one does; the Fjord skill teaches an agent how
to use them together: look at the board before changing it, keep what you wrote in a description,
plan work into tasks, take a task from branch to pull request, analyse a story, triage Azure imports.
Install it for Claude Code and Cursor (both read ~/.claude/skills):
fjord skill install
fjord skill install --dir .claude/skills puts it in a repository instead, and fjord skill prints it.
With a CLI older than 0.2.27, copy the skills/fjord folder into ~/.claude/skills/ by hand.
Settings in the app shows the exact paths. Set FJORD_DATA_DIR / FJORD_CONFIG_DIR to use other
locations (for example a separate test database). Back up by copying the data folder.
crates/fjord-core Rust library: schema & migrations, projects, columns, tasks, files, notes, search, activity
crates/fjord-vcs Git (via the git CLI), GitHub and Azure DevOps REST integration
crates/fjord-cli `fjord` CLI and MCP server
src-tauri Tauri desktop shell — thin commands over fjord-core
ui React + TypeScript interface (dnd-kit, Lucide, Motion)
All three front ends (GUI, CLI, MCP) go through fjord-core, so validation and the activity log
behave the same everywhere.
cargo test --workspace # Rust: core unit tests, CLI and MCP end-to-end tests
npm --prefix ui test # UI: keymap engine, i18n, helpers (Vitest)
cargo clippy --workspace --all-targets -- -D warnings
cargo fmt --all
npm --prefix ui run typecheck
See CONTRIBUTING.md. Translations are welcome: copy the no block in
ui/src/i18n.ts.
What changed in each version is in CHANGELOG.md. Please report security problems privately, as described in SECURITY.md.
Licensed under either of Apache License 2.0 or MIT, at your option.
Local-first project management, Linux first, also on Windows and macOS: kanban, notes with [[links]] and files in SQLite. Keyboard-first, mouse-friendly, with a CLI and MCP server for AI agents.
{ "mcpServers": { "jhtjernsmo-fjord": { "command": "mcpb", "args": [ "https://github.com/jhtjernsmo/fjord/releases/download/v0.2.32/fjord-mcp.mcpb" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Fjord läuft lokal über stdio.
Zuletzt geprüft: 2026-10-27. Local-first project management, Linux first, also on Windows and macOS: kanban, notes with [[links]] and files in SQLite. Keyboard-first, mouse-friendly, with a CLI and MCP server for AI agents.