GibWork MCP Server

What is GibWork MCP Server?

A Model Context Protocol (MCP) server implementation for interacting with the GibWork platform. It provides tools for managing tasks on GibWork through an MCP interface.

How to use GibWork MCP Server?

Install dependencies with pnpm, create a .env file with your Solana private key, then configure Claude Desktop to point to the compiled server. Use its tools for task management.

Key features of GibWork MCP Server

• Implements the Model Context Protocol for standardized tool interactions
• Create, retrieve, and search tasks on the GibWork platform
• Provides three tools: get-tasks-by-id, get-tasks, and create-task
• Supports pagination, filtering, and searching for tasks
• Uses a Solana private key for secure task creation

Use cases of GibWork MCP Server

• Fetch detailed information about a specific GibWork task by ID
• Browse or search tasks with pagination and tagged filtering
• Create new tasks on the GibWork platform from within an MCP client
• Integrate GibWork task management into AI‑powered workflows

FAQ from GibWork MCP Server

What does GibWork MCP Server do?

It allows AI agents (via MCP) to manage tasks on the GibWork platform, including fetching, searching, and creating tasks.

What prerequisites are required?

Node.js (latest LTS recommended) and pnpm version 10.5.2 or higher. For task creation, a Solana private key is needed.

How do I configure GibWork MCP Server with Claude Desktop?

Create a .env file with your Solana private key, then add the server to Claude Desktop’s MCP configuration (on Windows or macOS) with the path to the compiled dist/index.js.

How do I create a task?

Use the create-task tool, providing title, content, requirements, tags, payer, and token. The Solana private key from the .env file is used for authentication.

Is my Solana private key secure?

The key is stored in a .env file which is excluded from version control. Keep the key confidential and never commit it to the repository.