Log inSubmit server
Kwork logo

Kwork

Connects Kwork accounts to MCP clients for project discovery, marketplace work, conversations, orders, and controlled writes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kwork

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kwork": {
      "command": "uvx",
      "args": [
        "kwork-mcp@1.5.2"
      ],
      "env": {
        "KWORK_WRITES": "YOUR_VALUE_HERE",
        "KWORK_EXPECTED_USER_ID": "YOUR_VALUE_HERE",
        "KWORK_SITE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Kwork MCP server connects a Kwork account to an MCP client so an agent can inspect projects, offers, orders, dialogs, notifications, and account data. It supports marketplace discovery with category, price, and response filters, plus a two-step workflow for submitting offers and other writes. Use it when you want an agent to research freelance work or prepare Kwork actions while retaining confirmation control. It runs through `uvx` on macOS or Linux and supports Kwork.ru and, with configuration, Kwork.com.

Use cases

  • Discover Kwork projects by category, budget, and response count
  • Review unread dialogs and draft client replies
  • Inspect seller orders and identify pending actions
  • Prepare project offers for confirmation before sending
  • Monitor connects, notifications, and submitted offers

Key features

  • Searches projects across favorites, the marketplace, or selected categories
  • Reads offers, orders, dialogs, messages, kworks, and notifications
  • Supports price and response-count filters with cursor pagination
  • Controls writes with confirm, auto, or off modes
  • Reconciles uncertain write results to prevent duplicate actions
  • Supports Kwork.ru and configured Kwork.com accounts

Tools4

What Kwork lets your agent do. Expand a tool for its parameters.

Self-reported~62 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · kwork-mcp@1.5.2 (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.

How Kwork works

What Kwork MCP server does

Kwork MCP server gives an MCP-compatible agent access to a connected Kwork account. Its read tools cover account status, connect balances, project discovery, exchange information, offers, seller orders, dialogs, messages, kworks, user profiles, categories, and notifications.

Project discovery can use favorites, the full marketplace, or selected category IDs. Filters include price and the number of responses, and results can be paged with an opaque cursor. Agents can also inspect individual projects, offers, orders, conversations, and kworks after finding them.

Write actions include responding to a project, removing an offer, sending or changing messages, marking a dialog as read, submitting an order for review, and starting or pausing a kwork. These operations are exposed through a prepare-then-commit process rather than a single unrestricted call.

How it works

The Kwork MCP server authenticates through a one-time terminal login. The login command asks for Kwork credentials and optionally the last four phone digits and a proxy. After account binding, the token is stored in a protected local state directory; the username and password are not saved.

Each write is recorded and is not automatically retried. If a connection failure leaves the result uncertain, the server checks the operation before allowing additional writes for that account. Unresolved records can be reconciled with the write-status tools or resolved manually after checking Kwork.

KWORK_WRITES controls write access. confirm is the default and requires the agent to present the exact text, price, and recipient before sending. auto permits execution without a separate confirmation, while off hides write tools and provides read-only access. Client-side approval settings may add another confirmation step.

Setup and configuration

The supported setup uses macOS or Linux, Python 3.12–3.14, and uv; Windows is not supported. Run uvx kwork-mcp@1.5.2 login, then add the generated uvx kwork-mcp@1.5.2 command to an MCP client. Configuration examples are provided for Claude Code, Codex, Cursor, and Claude Desktop.

If several Kwork accounts have been logged in, set KWORK_EXPECTED_USER_ID to select one. The status command reports the selected account and site without contacting Kwork, and logout can remove an account binding. Do not place the Kwork login, password, token, or proxy in the client configuration.

Kwork.ru is the default site. Set KWORK_SITE=com to use Kwork.com with the shared account and token. The .com site does not provide the project marketplace, project search, categories, or project responses; dialogs, orders, and kworks remain available, with orders kept separate by site.

Limitations and notes

The Kwork MCP server depends on an active Kwork login. Authentication may expire, and Kwork can require browser-based CAPTCHA completion before login succeeds. A server configured with KWORK_WRITES=off cannot perform write operations.

In auto mode, the server labels project and message text as external data, but it cannot verify that an agent ignores instructions embedded in that text. For safer operation, use confirm and retain client-side approval for write tools.

When an operation has an unknown outcome, new writes are blocked until reconciliation. Check the relevant Kwork site, then use the pending-write commands or ask the agent to run reconcile_write for the associated write ID.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kwork

Kwork is an MCP server that connects a Kwork freelance-marketplace account to MCP clients. Its main tools discover projects, inspect offers and orders, read dialogs and notifications, report account status and connects, and prepare or commit controlled writes such as offers and messages.

Install it by running `uvx kwork-mcp@1.5.2 login`, then add `uvx kwork-mcp@1.5.2` to your MCP client configuration. The supported setup requires macOS or Linux, Python 3.12–3.14, and `uv`; Windows is not supported.

Yes, Kwork works with Cursor through its MCP configuration. Use the provided Cursor install link or add a server with `uvx` and the `kwork-mcp@1.5.2` argument, then restart the client.

Set `KWORK_WRITES=confirm` to require confirmation before each write, or set `KWORK_WRITES=off` to hide write tools entirely. The default is `confirm`; `auto` allows writes without a separate confirmation.

Set `KWORK_SITE=com` in the MCP client configuration. The same account and token can be used, but Kwork.com does not support project-marketplace search or project responses, and its orders are separate from Kwork.ru.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKwork AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kwork?style=directory)](https://allmcps.com/mcp/kwork)
HTML Embed
<a href="https://allmcps.com/mcp/kwork"><img src="https://allmcps.com/api/badge/kwork?style=directory" alt="Kwork on AllMCPs" /></a>