About GibWork MCP Server
GibWork MCP Server lets MCP clients manage tasks on the GibWork platform. It supports task creation, retrieval, and search, with a Solana private key required for creating tasks.
Key features
- 01Create tasks on GibWork
- 02Fetch tasks by ID
- 03List and search tasks
- 04Filter, sort, and paginate results
Use cases
- 01Create a GibWork task through an MCP client
- 02Look up a task by its ID
- 03Search and filter available tasks
MCP support
Exposes GibWork task creation, retrieval, and search as tools for MCP clients. Task creation requires a Solana private key.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGibWork MCP Server
A Model Context Protocol (MCP) server implementation for interacting with the GibWork platform. This server provides tools for managing tasks on the GibWork platform through an MCP.
Features
- Task Management: Create, retrieve, and search tasks on the GibWork platform
- MCP Protocol: Implements the Model Context Protocol for standardized tool interactions
Prerequisites
- Node.js (latest LTS version recommended)
- pnpm package manager (version 10.5.2 or higher)
- Solana private key (for task creation)
Installation
- Clone the repository:
git clone <repository-url>
cd gibwork-mcp
- Install dependencies:
pnpm install
- Create a
.envfile in the root directory and add your Solana private key:
SOLANA_PRIVATE_KEY=your_private_key_here
- Configure Claude Desktop:
- Open Claude Desktop settings
- Navigate to Developer settings
- Edit the configuration file at:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
- Add the following configuration:
Note: Adjust the paths according to your system configuration.{ "mcpServers": { "gibwork": { "command": "C:\\Program Files\\nodejs\\node", "args": ["C:\\path\\to\\gibwork-mcp\\dist\\index.js"] } } }
For more detailed information about MCP configuration, visit Model Context Protocol Quickstart Guide.
Project Structure
gibwork-mcp/
├── src/
│ ├── index.ts # Main server implementation
│ └── utils.ts # Utility functions for API interactions
├── dist/ # Compiled JavaScript output
├── package.json # Project dependencies and scripts
└── tsconfig.json # TypeScript configuration
Available Tools
The server implements the following MCP tools:
-
get-tasks-by-id
- Fetches a specific task by its ID
- Parameters:
id(string)
-
get-tasks
- Retrieves tasks with pagination and filtering
- Parameters:
page(number, default: 1)limit(number, default: 15)pageAll(boolean, default: false)search(string, default: '')orderBy(string, default: '')tags(string[], default: [])
-
create-task
- Creates a new task on the GibWork platform
- Parameters:
title(string)content(string)requirements(string)tags(string[])payer(string)token(object)
Development
- Build the project:
pnpm build
- Run the development server:
pnpm dev
Configuration
The server is configured to run with the following settings:
- API Base URL:
https://api2.gib.work - Module System: ES Modules
- Target: ES2022
- Strict Type Checking: Enabled
Security
- The
.envfile containing sensitive information is excluded from version control - Solana private key should be kept secure and never committed to the repository
License
ISC License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.