Workix MCP

What Workix MCP MCP server does

Workix MCP MCP server gives an AI agent access to the Workix catalog and account actions through MCP. The catalog includes projects, roles, orders, participants, and mentors. Public searches do not require an account key; operations connected to an account require WORKIX_AGENT_KEY.

The repository contains the MCP implementation under mcp/, alongside the Workix storefront and documentation. The MCP component is separate from the web interface, but both use the central Workix API. A local installation can therefore search the shared catalog without maintaining a separate local catalog.

How it works

The agent communicates with a local TypeScript MCP process. That process calls the Workix hub defined by WORKIX_API, which defaults conceptually to the central service at https://workix.co when configured as shown in the documentation. Search operations cover Workix listings and profiles. Authenticated operations can create or update listings and manage a participant profile.

Workix MCP MCP server also provides a local interface to supported external job sources. Depending on the source, it can search or read opportunities, combine results into a digest, open a specific listing, draft a proposal, submit through an available API, or produce a browser checklist. Submission always requires explicit human confirmation.

External credentials stay in the local MCP environment. Upwork, Kwork, and other platform passwords or tokens should not be sent to the Workix hub. Source behavior varies: some integrations use official APIs, while others rely on RSS or browser-assisted steps.

Setup and configuration

The documented source installation requires Node.js 22.5 or newer because the local store uses Node's built-in node:sqlite. From the repository, install and build the MCP package:

git clone https://github.com/facetoplace/Workix.git
cd Workix/mcp
npm install
npm run build

Configure an MCP client to launch mcp/dist/index.js with node. Set WORKIX_API to the hub URL, normally https://workix.co. Add WORKIX_AGENT_KEY after registering at Workix if the agent must create or modify account-owned data. The key is optional for public searches.

The repository also documents an npm and npx package, @workix/mcp, but recommends installing from source for the newest tools and adapters. Client configuration uses a standard local command and environment-variable block.

Tools and capabilities

Workix MCP MCP server supports these workflows:

• Search projects, roles, orders, participants, and mentors by relevant information such as skills and interests.
• Create or update Workix listings and maintain a participant profile with an agent key.
• Record profile preferences for networking, collaboration, startups, open source, and equity, using the documented preference values.
• Filter participants who opted into networking, collaboration, or mentor formats.
• Hide a participant profile from public feeds and search, or bump it when eligible.
• Collect and search opportunities from supported external platforms through local adapters.
• Prepare proposals and either submit through an available API or create a browser-based checklist.

The workix_list_performers capability supports participant filtering, and workix_bump_profile can resurface a profile subject to the hub's three-day cooldown. External platform support is not uniform: Freelancehunt and Freelancer.com use official API workflows, while Upwork, FL.ru, and HH.ru have different authentication, submission, or browser requirements documented by the project.

Limitations and notes

A Workix account key is needed for account-related actions, and the public catalog remains separate from private platform credentials. Proposal submission is not fully automatic: human confirmation is always required, and some sources only support browser assistance or a checklist.

Platform readiness and permissions can change. API access, OAuth requirements, user-agent rules, proxies, browser sessions, and platform terms affect what an adapter can do. Use each source according to its current rules; the project does not authorize unauthorized scraping.

The storefront can be hosted on another domain, but that is a separate repository function and does not create a separate catalog. A hosted mirror still reads from the central Workix API.