Kwork — Claude Code MCP server: what it does, how to install
Kwork is a Claude Code MCP server that links a freelance marketplace profile to your assistant. Handles project discovery, dialogue monitoring, and proposal drafts.
MIT ★ 6 updated 2026-11-15
claude mcp add --env KWORK_EXPECTED_USER_ID=<KWORK_EXPECTED_USER_ID> --env KWORK_EXPECTED_USERNAME=<KWORK_EXPECTED_USERNAME> --env KWORK_WRITES=<KWORK_WRITES> --env KWORK_SITE=<KWORK_SITE> --env KWORK_TIMEOUT=<KWORK_TIMEOUT> --transport stdio kwork -- uvx kwork-mcpWhat Kwork does
The server bridges your AI assistant with the marketplace through local stdio communication. The toolset lets the agent inspect available tasks, track remaining bids, inspect customer threads, and generate proposal drafts with specific costs and delivery windows.
Outbound updates rely on the KWORK_WRITES environment variable. By default, it operates in confirm mode, forcing the assistant to display the exact wording and pricing for explicit confirmation. Setting it to off strips modifying capabilities entirely, while auto allows hands-off submission.
Execution requires macOS or Linux, Python between 3.12 and 3.14, and uv. Windows is unsupported. Credentials are entered once via an interactive CLI login prompt and never exposed inside client config files. The package defaults to kwork.ru, with kwork.com support enabled through KWORK_SITE=com.
What it helps with
- find relevant freelance gigs by budget thresholds and keywords
- draft bids with specified delivery timelines and price tags
- check ongoing message threads for unread client updates
- inspect active orders and remaining connection credits
Example prompts for the agent
- Find web scraping jobs with a minimum price of 10000
- Check my unread marketplace conversations and propose replies
- Draft an offer for project 3257238: 15000 price and 5 days delivery
How to install Kwork
Platform CLI
claude mcp add --env KWORK_EXPECTED_USER_ID=<KWORK_EXPECTED_USER_ID> --env KWORK_EXPECTED_USERNAME=<KWORK_EXPECTED_USERNAME> --env KWORK_WRITES=<KWORK_WRITES> --env KWORK_SITE=<KWORK_SITE> --env KWORK_TIMEOUT=<KWORK_TIMEOUT> --transport stdio kwork -- uvx kwork-mcpReplace <…> with your own values. 20 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from kwork-mcp <command>
Platform CLI
codex mcp add kwork --env KWORK_EXPECTED_USER_ID=<KWORK_EXPECTED_USER_ID> --env KWORK_EXPECTED_USERNAME=<KWORK_EXPECTED_USERNAME> --env KWORK_WRITES=<KWORK_WRITES> --env KWORK_SITE=<KWORK_SITE> --env KWORK_TIMEOUT=<KWORK_TIMEOUT> -- uvx kwork-mcpReplace <…> with your own values. 20 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from kwork-mcp <command>
Config file
{
"mcpServers": {
"kwork": {
"command": "uvx",
"args": [
"kwork-mcp"
],
"env": {
"KWORK_EXPECTED_USER_ID": "<KWORK_EXPECTED_USER_ID>",
"KWORK_EXPECTED_USERNAME": "<KWORK_EXPECTED_USERNAME>",
"KWORK_WRITES": "<KWORK_WRITES>",
"KWORK_SITE": "<KWORK_SITE>",
"KWORK_TIMEOUT": "<KWORK_TIMEOUT>"
}
}
}
}Replace <…> with your own values. 20 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from kwork-mcp <command>
Config file
{
"servers": {
"kwork": {
"type": "stdio",
"command": "uvx",
"args": [
"kwork-mcp"
],
"env": {
"KWORK_EXPECTED_USER_ID": "<KWORK_EXPECTED_USER_ID>",
"KWORK_EXPECTED_USERNAME": "<KWORK_EXPECTED_USERNAME>",
"KWORK_WRITES": "<KWORK_WRITES>",
"KWORK_SITE": "<KWORK_SITE>",
"KWORK_TIMEOUT": "<KWORK_TIMEOUT>"
}
}
}
}Replace <…> with your own values. 20 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from kwork-mcp <command>
Platform CLI
gemini mcp add -e KWORK_EXPECTED_USER_ID=<KWORK_EXPECTED_USER_ID> -e KWORK_EXPECTED_USERNAME=<KWORK_EXPECTED_USERNAME> -e KWORK_WRITES=<KWORK_WRITES> -e KWORK_SITE=<KWORK_SITE> -e KWORK_TIMEOUT=<KWORK_TIMEOUT> kwork uvx kwork-mcpReplace <…> with your own values. 20 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from kwork-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Kwork
How to install Kwork on Claude Code?
Run claude mcp add kwork-mcp -- uvx kwork-mcp. Complete the initial sign-in beforehand by running uvx [email protected] login in your terminal.
What is required to run Kwork?
A Linux or macOS environment, uv, and Python 3.12–3.14 are mandatory. You also need an existing marketplace user profile.
Does it work with kwork.com?
Yes, pass KWORK_SITE=com in the environment settings. The international platform lacks the public project feed tool, though messages and orders remain accessible.