Kwork vs OSCAR
A side-by-side look at the Kwork and OSCAR 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 OSCAR 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 OSCAR when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
status, list_projects, read_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | KWORK_WRITESKWORK_EXPECTED_USER_IDKWORK_SITE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 192 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 11 |
| Full listing | View Kwork | View OSCAR |
Tools & capabilities
Kwork tools 4
account_statusФактический account ID, binding, готовность writes и `unresolved_write_idsget_connectsАктивные и общие коннектыdiscover_projectsfavorites`, `all` или `category_ids`, фильтры и opaque cursorlist_notificationsПолные группы уведомлений
OSCAR tools 11
statusOSCAR's version, its ports (HTTP, the fixed OSC listening port, the socket bridge), whether editing is locked, the MIDI driver's condition, and how many projects and published interfaces there are. Start here.list_projectsEvery project OSCAR holds, with its id and its title, as File > Open project or template lists them. A project is what a person edits; it reaches phones only once it is published (list_published).read_projectEvery widget in one project, published or not, with its full settings as the editor holds them: addresses, ports, channels, MIDI mappings, DMX targets. Also says where the project is published, if it is. A setting nobody touched reads as its default. What phones see is the published copy, which may be older: read_published reads that one.list_publishedEvery published interface: its name, the project it was published from, the path it is served at, who can open it (access: "network", or "off" for one no device can open, whose schedules and bridges still run), and how many widgets it holds. Published interfaces are running -- phones and tablets may be on them, and the rig hears them.read_publishedEvery widget on one published interface, with its full settings as phones have them: addresses, ports, channels, MIDI mappings, DMX targets. For answering why something does or does not respond.installation_mapOne picture of the whole installation: this computer's network addresses and ports, its MIDI ports and USB interfaces (a USB DMX interface among them), and everything the published interfaces talk to and listen for -- each OSC destination with the addresses sent to it, each MIDI port with its channels and controllers, each DMX output with its universe and channels -- with the control and interface behind every one. notices lists what does not add up: a MIDI port or USB interface that is not there, OSC followed while OSCAR cannot listen, two controls on the same DMX channels. It is worked out from settings and sends nothing onto the network: it says where OSCAR sends, not whether anything is there to hear it.midi_portsThe MIDI inputs and outputs this machine has right now, and the driver's condition.recent_activityThe network log's recent rows: what OSCAR's server actually received and sent, oldest first, repeats within a moment gathered into one row with a count n. Each row has what (OSC address, MIDI control, DMX universe and channels) and value (what the latest carried). Incoming rows: device (the sender's address, or the MIDI port), surfaces (published interfaces that follow it), canvas (the editor's canvas followed it); with neither, nothing follows it. Outgoing rows: to (where it went), origin (whose move: canvas, local, internet, schedule, bridge), surface (the published interface) and widget. dropped, on either, says why it was refused. The first place to look when something moves that should not, or does not move when it should.describe_widgetsEvery widget OSCAR has -- tag, attributes, defaults, and each setting with its type, options and meaning -- plus how an interface is written as HTML. Read this before building one.validate_draftRun an interface written as HTML through the widgets' own validators: unknown settings, values their panels would refuse, missing or repeated ids. Returns the complaints to correct. Nothing is saved.create_draftValidate an interface and, if it is clean, save it as a draft: it appears in OSCAR under File > Open project or template, with a Draft badge. It is a file for a person to review: nothing is published, nothing is sent, and no project is changed. An existing draft of the same name is only replaced when overwrite is true.
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"
}
}
}
}
OSCAR
{
"mcpServers": {
"oscar": {
"command": "npx",
"args": [
"-y",
"createwithoscar"
]
}
}
}
Frequently asked questions
Kwork is categorized under Developer Tools and uses a local stdio subprocess. OSCAR belongs to Developer Tools and uses a local stdio subprocess. Pick Kwork for developer tools work and OSCAR 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. OSCAR is listed as free. Auth: no auth required. 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 oscar 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. OSCAR has 68/100 (Great) with 0 views, 0 installs and 192 GitHub stars.