Kwork vs WalkerOS Flow
A side-by-side look at the Kwork and WalkerOS Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kwork for developer tools work as a local process; choose WalkerOS Flow for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kwork when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KWORK_WRITES, KWORK_EXPECTED_USER_ID, KWORK_SITE. - You want tools like
account_status, get_connects, discover_projects.
Choose WalkerOS Flow when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | KWORK_WRITESKWORK_EXPECTED_USER_IDKWORK_SITE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 347 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Kwork | View WalkerOS Flow |
Tools & capabilities
Kwork tools 4
account_statusФактический account ID, binding, готовность writes и `unresolved_write_idsget_connectsАктивные и общие коннектыdiscover_projectsfavorites`, `all` или `category_ids`, фильтры и opaque cursorlist_notificationsПолные группы уведомлений
WalkerOS Flow tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kwork
{
"mcpServers": {
"kwork": {
"command": "uvx",
"args": [
"kwork-mcp@1.5.2"
],
"env": {
"KWORK_WRITES": "YOUR_KWORK_WRITES_HERE",
"KWORK_EXPECTED_USER_ID": "YOUR_KWORK_EXPECTED_USER_ID_HERE",
"KWORK_SITE": "YOUR_KWORK_SITE_HERE"
}
}
}
}
WalkerOS Flow
{
"mcpServers": {
"walkeros-flow": {
"command": "npx",
"args": [
"-y",
"walkeros"
]
}
}
}
Frequently asked questions
Kwork is categorized under Developer Tools and uses a local stdio subprocess. WalkerOS Flow belongs to Developer Tools and uses a local stdio subprocess. Pick Kwork for developer tools work and WalkerOS Flow for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kwork has no declared pricing — check the project's own site. WalkerOS Flow has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kwork and walkeros-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kwork has a quality signal of 52/100 (Good) with 0 views, 0 installs and 3 GitHub stars. WalkerOS Flow has 49/100 (Fair) with 1 views, 0 installs and 347 GitHub stars.