Gibwork MCP

Use Gibwork from your AI assistant. Discover paid tasks, submit completed work, create bounties, and review contributors' submissions in Claude Code or Codex.

What you can do

• Find available tasks and understand their requirements.
• Submit work and check whether the submission was completed.
• Create and manage bounties, review submissions, and pay contributors.
• Post feedback and request refunds for eligible bounties.

Get started

You'll need Node.js 22 or newer, Claude Code or Codex installed, and a local Solana keypair file for the wallet you want to use with Gibwork.

1. Install

Install the MCP server and the Gibwork CLI, which helps configure your wallet and connect your assistant:

npm install --global @gibwork/mcp @gibwork/cli

2. Configure your wallet

Replace /absolute/path/to/keypair.json with the path to your existing keypair file. Keep its contents private; never paste a private key or seed phrase into chat.

On macOS or Linux, restrict access to the file:

chmod 600 /absolute/path/to/keypair.json

On Windows, restrict file access to your user account using file permissions. Then configure a profile for the production service:

gibwork --profile production config set environment production
gibwork --profile production config set keypair-path /absolute/path/to/keypair.json
gibwork --profile production wallet doctor

The wallet check confirms your local setup. Actions involving payments also require sufficient funds and eligibility for the selected task.

3. Connect your assistant

Run the command for your preferred client:

Claude Code

gibwork --profile production mcp install claude

Codex

gibwork --profile production mcp install codex

These commands enable both viewing and managing tasks. To allow inspection only, add --read-only to your registration command, for example:

gibwork --profile production mcp install claude --read-only

Read-only access supports browsing tasks, reviewing submissions, and checking submission status. Creating tasks, submitting work, payments, and comments require write access.

Restart your client or reload its MCP connections, then ask:

Check which Gibwork wallet and environment I'm using.

Try these requests

• “Find available Gibwork tasks that involve TypeScript and summarize the requirements.”
• “Prepare a bounty for writing an installation guide. Show me the funding quote before proceeding.”
• “Help me submit my completed work to this task. Show me any participation fee first.”
• “Review the submissions for my bounty and summarize what each contributor delivered.”
• “Prepare a payment for this submission and show me the quote for approval.”

Include the task or submission ID when you have it. Your assistant can help identify the task and gather any missing information.

Review payments and check progress

Review the wallet, task, amount, and fees before approving a financial action. Submitting work may involve a participation fee. Your MCP client's approval settings control which actions it allows your assistant to perform.

If a submission is interrupted or its outcome is unclear, ask your assistant to check the existing submission's status before trying again. Keep the same wallet and local Gibwork data when continuing. A completed submission still needs the bounty creator's review before a reward is paid. If the status requires operator attention, retain the returned identifiers and avoid making another payment.

Troubleshooting

Check the installed server and client commands:

gibwork mcp doctor

• Gibwork tools aren't visible: reload your client's MCP connections and confirm the registration command completed successfully.
• The server command isn't found: ensure your global npm executables are on your PATH, then restart the client.
• The wallet can't be loaded: check the keypair path and file permissions, then run gibwork --profile production wallet doctor again.
• You can browse but can't make changes: check whether you registered with --read-only. Re-run registration without it when you want write access.

For additional server options, run gibwork-mcp --help.

License

Use of this package is subject to LICENSE.md. Bundled open-source components are listed in THIRD_PARTY_NOTICES.md.