# Kwork [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/simonether/kwork-mcp  
**GitHub Stars:** 3  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kwork

## Description
Kwork freelance marketplace: browse projects, submit offers, manage orders, message clients

## Tools
Capabilities this server exposes over MCP:

- **account_status** — Фактический account ID, binding, готовность writes и `unresolved_write_ids
- **get_connects** — Активные и общие коннекты
- **discover_projects** — favorites`, `all` или `category_ids`, фильтры и opaque cursor
- **list_notifications** — Полные группы уведомлений

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "kwork": {
    "command": "uvx",
    "args": ["kwork-mcp@1.5.2"],
    "env": {
      "KWORK_WRITES": "",
      "KWORK_EXPECTED_USER_ID": "",
      "KWORK_SITE": ""
    }
  }
}
```

**Requires environment variables:** `KWORK_WRITES`, `KWORK_EXPECTED_USER_ID`, `KWORK_SITE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/kwork/readme_