B
benord-labs/frink
Desktop-first app for parallel agents and triggered multi-step workflows
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-10-21 · last seen 2026-11-14 · seen 28× · listed by 25 sources
- Score
- score 2,503 · 25 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-21;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
Frink
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Desktop-first app for parallel agents and triggered multi-step workflows.
Workflows can include steps you write yourself in code, alongside agent, command and approval steps.
Save a routine as a Flow and it starts by itself: on a schedule, from any webhook, or from an event in Linear, Shortcut, ClickUp, Sentry, PostHog or Vercel.
Finished work and agent questions wait for you in the Work Queue, on your computer or on your iPhone (beta).
It all runs on your computer while Frink is open, with the AI coding tool you already use. No Frink account.
Download Frink
## Features
### 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.
Docs →
### 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.
Docs →
### It starts when something happens
A new ticket in Linear, Shortcut or ClickUp, an error in Sentry, an event in PostHog or Vercel, 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.
Docs →
### 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.
Docs →
### 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 and its code back to an earlier point.
Docs →
Also in the box:
Custom steps — need a step Frink doesn't have? Ask the agent to write one in JavaScript, or write it yourself, and reuse it in any Flow. For another language, use a command step.
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 only checks that you are signed in and leaves the login with the tool. If you paste an Anthropic API key instead, it is stored encrypted on your computer.
Local-first — chats, Flows and tasks live in SQLite on your machine. No account needed. Official builds send anonymous usage counts and crash reports: everything Frink sends.
## Supported Agents
Claude Code
Codex
OpenCode
GitHub Copilot
Cursor
Bring your own subscription or API key — Frink runs the agent, you keep the account.
Workflows can include steps you write yourself in code, alongside agent, command and approval steps.
Save a routine as a Flow and it starts by itself: on a schedule, from any webhook, or from an event in Linear, Shortcut, ClickUp, Sentry, PostHog or Vercel.
Finished work and agent questions wait for you in the Work Queue, on your computer or on your iPhone (beta).
It all runs on your computer while Frink is open, with the AI coding tool you already use. No Frink account.
Download Frink
## Features
### 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.
Docs →
### 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.
Docs →
### It starts when something happens
A new ticket in Linear, Shortcut or ClickUp, an error in Sentry, an event in PostHog or Vercel, 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.
Docs →
### 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.
Docs →
### 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 and its code back to an earlier point.
Docs →
Also in the box:
Custom steps — need a step Frink doesn't have? Ask the agent to write one in JavaScript, or write it yourself, and reuse it in any Flow. For another language, use a command step.
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 only checks that you are signed in and leaves the login with the tool. If you paste an Anthropic API key instead, it is stored encrypted on your computer.
Local-first — chats, Flows and tasks live in SQLite on your machine. No account needed. Official builds send anonymous usage counts and crash reports: everything Frink sends.
## Supported Agents
Claude Code
Codex
OpenCode
GitHub Copilot
Cursor
Bring your own subscription or API key — Frink runs the agent, you keep the account.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/benord-labs-frink/)
- Source
- awesome · https://github.com/benord-labs/frink
- Browse by field
- MCP servers
- Listed by
- 25 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.