mcp server
frink
Fine-tuned automation for everyone: visual workflows where AI coding agents act on your tickets, errors and schedules, and ask before they change anything. Works with Claude Code, Codex, OpenCode, Git
Set up
Runs on your computer. Pick your agent and operating system.
This project does not publish an install method we can turn into a config. Follow the README instead.
README
synced Oct 17, 2026Features
Run four agents side by side
Split the window into up to four panes and give each agent a different job. They work at the same time, and each pane keeps its own model and its own diff to review. Put each one on its own git worktree and they never touch the same files.
One sentence becomes an automation
Type the routine the way you would say it: "Every weekday at 9am, run the tests. If any fail, have an agent fix them, then wait for my approval before it opens a PR." Frink builds it as a Flow and lists every step, so you can read it and change it before it runs.
It starts when something happens
A new ticket in Linear, Jira, Shortcut or ClickUp, an error in Sentry, an event in PostHog, any webhook, or a time of day. The Flow checks a condition to pick its path, and waits at an approval step until you say yes.
Everything that needs you, in one queue
Every run from every project shows up in the Work Queue as running, ready for review or queued. A badge appears when a Flow stops for approval or an agent has a question. Read what it did, then approve it or reply to send it back.
Check the work and fix it yourself
Every file the agent changes shows as a diff. Open it in the built-in editor, change a line and save, run a command in the terminal, or roll the chat back to an earlier checkpoint.
Also in the box:
- Permissions — every change and command passes a per-project gate first;
~/.ssh,~/.awsand.envare blocked wherever Frink checks (the page lists what it doesn't cover yet). - Plugins & MCP — connect Linear, Shortcut, ClickUp, GitHub, Notion, Slack, Sentry, PostHog and more, as chat tools and Flow steps.
- Your own AI sign-in — uses your existing Claude Code or Codex login, the OpenCode or GitHub Copilot you installed, or your Cursor sign-in. Frink never stores the token.
- Local-first — chats, Flows, tasks and permissions live in SQLite on your machine. No account needed. Official builds send anonymous usage counts and crash reports: everything Frink sends.
Supported Agents
Bring your own subscription or API key — Frink runs the agent, you keep the account.
Install
- Download from frink.dev
- Or grab a build directly: macOS Apple Silicon · macOS Intel
- Or build from source — see CONTRIBUTING.md.
Linux (x64 and arm64)
Download the AppImage or the .deb from frink.dev/download, or directly: x64 AppImage · .deb, arm64 AppImage · .deb. Both update themselves.
- AppImage (any distro):
chmod +x Frink-X.Y.Z.AppImage && ./Frink-X.Y.Z.AppImage, withX.Y.Zthe version you downloaded. It does not need libfuse2: it mounts itself withfusermount3from thefuse3package. If it will not start, installfuse3or start it with--appimage-extract-and-run. Keep it in a folder you can write to, such as~/Applications, so updates can replace it. - .deb (Debian/Ubuntu):
sudo apt install ./frink_X.Y.Z_amd64.deb(_arm64.debon arm64). Updates ask for your password in a system prompt.
Frink saves API keys and MCP credentials only when it can encrypt them with a desktop keyring (GNOME Keyring or KWallet). Without one it does not save them, so install one and relaunch Frink before adding accounts.
Community & Support
- Bugs & ideas: open an issue.
- Changelog: frink.dev/changelog.
- Show support: star the repo to follow along.
Developing
Want to contribute or run locally? See our CONTRIBUTING.md guide.
License
Frink is licensed under the MIT License. Copyright 2026 Benji Norval.
Third-party licenses are listed in THIRD_PARTY_LICENSES.md.