Workix — Claude Code MCP server: jobs and gigs for agents
Wires an agent to the Workix catalog and a set of job boards: searching projects, roles, gigs and people, with results stored in a local database.
claude mcp add --env WORKIX_API=<WORKIX_API> --env WORKIX_AGENT_KEY=<WORKIX_AGENT_KEY> --transport stdio mcp -- npx -y @workix/mcpWhat Workix does
Workix is a local MCP server. It hands the agent tools over the Workix hub: search and create projects, roles, orders, participant profiles and mentors. A second group of tools reaches out to job boards for digests, search, proposal drafts and browser apply steps. Submitting the application stays with the human.
Collecting and searching are two steps. workix_collect pulls from all sources in parallel into a local store, then workix_db_search ranks the results offline: word-boundary matching, résumé and "for hire" entries dropped, cross-posts merged, a cap per advertiser, plus a check against your outreach log. Board modules are not needed at install time; the server fetches them on the first call and keeps a local copy.
Writing to the hub needs WORKIX_AGENT_KEY, and WORKIX_API sets the API address. Boards that read a logged-in browser profile sit behind opt-in flags and never submit anything. Without the key, search and reading still work while creating or editing cards does not — get the key sorted before the first run.
What it helps with
- find gigs and vacancies for given skills across several boards at once
- keep collected listings in a local store and query them offline
- publish a project or role card to the Workix hub
- draft a proposal and prepare the browser steps to apply
- check the outreach log so you do not contact the same place twice
Example prompts for the agent
- Collect python listings from every board and show the ones I have not applied to yet
- Search Workix for projects looking for react and frontend help
- Draft a proposal for this listing and give me the browser steps
How to install Workix
Platform CLI
claude mcp add --env WORKIX_API=<WORKIX_API> --env WORKIX_AGENT_KEY=<WORKIX_AGENT_KEY> --transport stdio mcp -- npx -y @workix/mcpReplace <…> with your own values
Platform CLI
codex mcp add mcp --env WORKIX_API=<WORKIX_API> --env WORKIX_AGENT_KEY=<WORKIX_AGENT_KEY> -- npx -y @workix/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@workix/mcp"
],
"env": {
"WORKIX_API": "<WORKIX_API>",
"WORKIX_AGENT_KEY": "<WORKIX_AGENT_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@workix/mcp"
],
"env": {
"WORKIX_API": "<WORKIX_API>",
"WORKIX_AGENT_KEY": "<WORKIX_AGENT_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e WORKIX_API=<WORKIX_API> -e WORKIX_AGENT_KEY=<WORKIX_AGENT_KEY> mcp npx -y @workix/mcpReplace <…> with your own values
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 Workix
How do I install Workix in Claude Code?
Run claude mcp add mcp -e WORKIX_AGENT_KEY=<WORKIX_AGENT_KEY> -- npx -y @workix/mcp with your own key in place.
What does Workix do?
It gives the agent tools to search the Workix catalog and external job boards, and to publish or edit cards when an agent key is set.
What do I need before it works?
Set WORKIX_AGENT_KEY for hub writes and WORKIX_API for the API address. Browser-profile boards turn on through separate flags such as AVITO_ENABLE=1 and X_ENABLE=1.
