Shippy MCP Server
resmiKirim pekerjaan. Dapatkan royalti.
Dokumentasi
Instalasi Server MCP
Shippy menyediakan server Model Context Protocol (MCP) jarak jauh yang memungkinkan asisten coding AI berinteraksi dengan bounty Anda langsung di IDE Anda.
Server MCP Dokumentasi
Perlu diketahui bahwa kami juga menyediakan endpoint MCP terpisah untuk membaca dokumentasi Shippy melalui MCP:
Endpoint: https://shippy.sh/mcp/docs
Endpoint ini tidak memerlukan autentikasi dan menyediakan dua alat:
| Alat | Deskripsi |
|---|---|
| list_docs | Tampilkan semua halaman dokumentasi yang tersedia |
| read_doc | Baca halaman dokumentasi tertentu berdasarkan ID |
Ini berguna jika Anda ingin asisten AI Anda dapat merujuk ke dokumen Shippy tanpa meninggalkan IDE Anda.
Fitur
Dengan server Shippy MCP, asisten AI Anda dapat:
Untuk Kontributor:
- Menjelajahi dan mencari bounty di berbagai proyek
- Membaca detail bounty lengkap dan kriteria penerimaan
- Mengklaim bounty untuk mulai bekerja
- Mengirimkan pekerjaan yang telah selesai untuk ditinjau
- Melihat dan mengelola klaim aktif Anda
Untuk Pendiri:
- Membuat dan memperbarui bounty
- Menutup dan membuka kembali bounty
- Mengelola label proyek
- Membuat dan mengonfigurasi proyek (Mode Reputasi atau Mode Bagi Hasil)
Prasyarat
- Akun Shippy (daftar di sini)
- Token akses MCP (buat di Pengaturan Pengguna → Token Akses MCP)
Instalasi Cepat (Cursor)
Jika Anda menggunakan Cursor, klik tombol "Tambahkan ke Cursor" di pengaturan pengguna Anda setelah membuat token. Ini akan secara otomatis mengonfigurasi server MCP.
Instalasi Manual
Cursor
Tambahkan ini ke ~/.cursor/mcp.json:
{
"mcpServers": {
"shippy": {
"url": "https://shippy.sh/mcp",
"headers": {
"Authorization": "Bearer shp_YOUR_TOKEN"
}
}
}
}
Windsurf
Tambahkan ini ke ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"shippy": {
"serverUrl": "https://shippy.sh/mcp",
"headers": {
"Authorization": "Bearer shp_YOUR_TOKEN"
}
}
}
}
Catatan: Windsurf menggunakan
serverUrlalih-alihurluntuk server HTTP. Lihat dokumen Windsurf MCP.
Codex (OpenAI)
Codex menggunakan konfigurasi TOML di ~/.codex/config.toml. Anda memiliki dua opsi:
Opsi 1: Token langsung (lebih sederhana)
Tambahkan ini ke ~/.codex/config.toml:
[mcp_servers.shippy]
url = "https://shippy.sh/mcp"
http_headers = { "Authorization" = "Bearer shp_YOUR_TOKEN" }
Opsi 2: Variabel lingkungan (lebih aman)
[mcp_servers.shippy]
url = "https://shippy.sh/mcp"
bearer_token_env_var = "SHIPPY_MCP_TOKEN"
Kemudian atur variabel lingkungan di shell Anda (tambahkan ke ~/.zshrc atau ~/.bashrc):
export SHIPPY_MCP_TOKEN="shp_YOUR_TOKEN"
Catatan: Lihat dokumentasi Codex MCP untuk opsi konfigurasi lebih lanjut.
Claude Desktop
Claude Desktop hanya mendukung server MCP berbasis stdio, jadi Anda memerlukan mcp-remote untuk terhubung ke endpoint HTTP Shippy.
Tambahkan ke konfigurasi Claude Desktop Anda:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"shippy": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://shippy.sh/mcp",
"--header",
"Authorization: Bearer shp_YOUR_TOKEN"
]
}
}
}
Claude Code
Claude Code juga menggunakan server berbasis stdio. Anda dapat menambahkan Shippy melalui CLI:
claude mcp add shippy -- npx -y mcp-remote https://shippy.sh/mcp --header "Authorization: Bearer shp_YOUR_TOKEN"
Atau tambahkan ke .mcp.json proyek Anda:
### Other Clients (stdio-only)
For other MCP clients that only support stdio transport (not Streamable HTTP), use mcp-remote with the same configuration pattern as Claude Desktop above.
> Note: Cursor 0.50+ and Windsurf support Streamable HTTP natively. Claude Desktop, Claude Code, and older clients require mcp-remote.
## Available Tools
### Read Operations
| Tool | Description | Auth |
| --------------------- | ----------------------------------------------------- | ---------- |
| list\_projects | Browse projects on Shippy | Optional\* |
| read\_project | Get project details by slug | Optional\* |
| list\_bounties | List bounties for a project | Optional\* |
| read\_bounty | Get bounty by identifier (e.g., "SHP-42") | Optional\* |
| list\_labels | List all labels for a project | Optional\* |
| read\_label | Get label details by ID | Optional\* |
| list\_comments | List comments on a bounty | Optional\* |
| list\_attachments | List attachments for a bounty, submission, or comment | Optional\* |
| list\_my\_bounties | List bounties you have claimed | Required |
| list\_my\_submissions | List your submissions | Required |
\*Optional: Works without auth for public projects. With auth, also shows your private projects.
### Contributor Operations
| Tool | Description |
| ------------------------------ | ------------------------------------------------ |
| claim\_bounty | Claim a bounty to start working on it |
| release\_claim | Release your claim on a bounty |
| create\_submission | Submit work for a claimed bounty |
| update\_submission | Update a draft/pending submission |
| suggest\_bounty | Suggest a new bounty for founder review |
| create\_comment | Add a comment to a bounty (supports attachments) |
| update\_comment | Update your own comment |
| delete\_comment | Delete a comment (author or founder) |
| get\_contributor\_agreement | View project's contributor agreement |
| accept\_contributor\_agreement | Accept project's contributor agreement |
### Attachment Operations
| Tool | Description |
| ---------------------------- | -------------------------------------------------- |
| generate\_nanoid | Generate a unique ID for pre-uploading attachments |
| get\_attachment\_upload\_url | Get a signed URL to upload a file to R2 |
| create\_attachment | Register an uploaded attachment |
| delete\_attachment | Delete an attachment |
Attachments can be added to bounties, submissions, and comments. For comments, use the `PENDING_COMMENT` reference type when uploading before the comment exists, then pass the generated ID to `create_comment`.
### Founder Operations
| Tool | Description |
| --------------------- | ------------------------------------------------------ |
| create\_bounty | Create a new bounty for a project |
| update\_bounty | Update bounty title, description, points, etc. |
| close\_bounty | Close a bounty (expires claims) |
| reopen\_bounty | Reopen a closed bounty |
| create\_label | Create a new label for a project |
| update\_label | Update label name or color |
| delete\_label | Delete a label from a project |
| create\_project | Create a new project (reputation or profit share mode) |
| update\_project | Update project settings |
| update\_project\_logo | Update or remove project logo |
## Example Usage
Once connected, try prompts like:
> "What bounties am I working on?"
> "Show me bounty SHP-42"
> "List open bounties on the shippy project"
> "Claim bounty SHP-15"
> "Submit my work for SHP-15 with description: Implemented the dark mode toggle. See PR #42."
> "Update submission sub\_123 with description: Added screenshots and test results."
> "Update submission sub\_123 to status: PENDING"
> "Add a comment on SHP-42: Great work! Here's my feedback..."
> "Upload a screenshot to my comment on SHP-42"
For Founders:
> "Create a bounty for my project 'shippy' titled 'Add dark mode support' with 50 points"
> "Update SHP-42 to have 100 points"
> "Create a label called 'urgent' with color #FF0000 for my shippy project"
> "Create a reputation mode project called 'my-oss-project' for open source contributions"
> "Create a profit share project with 10% pool percentage and monthly payouts"
## Troubleshooting
### Server not connecting
1. Verify your token is correct and hasn't been deleted
2. Make sure you're using the correct config file path for your IDE
3. Restart your IDE after making config changes
4. Check that Shippy is accessible at https://shippy.sh/mcp
### Authentication errors
1. Check that your token starts with `shp_`
2. Ensure the `Authorization` header format is `Bearer shp_YOUR_TOKEN` (with a space)
3. Generate a new token if the current one isn't working
### Tools not appearing
1. Make sure the MCP server is enabled in your IDE's settings
2. Check your IDE's MCP logs for connection errors
3. Try refreshing/reloading the MCP server list
### 406 Not Acceptable errors
If you're building your own MCP client, ensure your requests include:
Accept: application/json, text/event-stream
## Keamanan
* Token MCP Anda terikat ke akun Shippy Anda
* Token dapat dicabut kapan saja dari pengaturan Anda
* Setiap token menunjukkan kapan terakhir digunakan untuk audit
* Kami merekomendasikan penggunaan token terpisah untuk mesin yang berbeda
* Awalan token `shp_` mengaktifkan pemindaian rahasia GitHub
## Sumber Daya
* Spesifikasi Model Context Protocol
* Dokumentasi Cursor MCP
* Dokumentasi Windsurf MCP
* Panduan Claude Desktop MCP
* mcp-remote di npm
## Butuh Bantuan?
Email [email protected]