Shippy MCP Server
oficialEnvía trabajo. Gana regalías.
Documentación
Instalación del Servidor MCP
Shippy proporciona un servidor remoto del Protocolo de Contexto de Modelo (MCP) que permite a los asistentes de codificación con IA interactuar con tus recompensas directamente en tu IDE.
Servidor MCP de Documentación
Ten en cuenta que también ofrecemos un endpoint MCP separado para leer la documentación de Shippy a través de MCP:
Endpoint: https://shippy.sh/mcp/docs
Este endpoint no requiere autenticación y proporciona dos herramientas:
| Herramienta | Descripción |
|---|---|
| list_docs | Listar todas las páginas de documentación disponibles |
| read_doc | Leer una página de documentación específica por ID |
Esto es útil si quieres que tu asistente de IA pueda consultar la documentación de Shippy sin salir de tu IDE.
Funcionalidades
Con el servidor MCP de Shippy, tu asistente de IA puede:
Para Contribuidores:
- Explorar y buscar recompensas en todos los proyectos
- Leer los detalles completos de las recompensas y los criterios de aceptación
- Reclamar recompensas para empezar a trabajar
- Enviar el trabajo completado para revisión
- Ver y gestionar tus reclamaciones activas
Para Fundadores:
- Crear y actualizar recompensas
- Cerrar y reabrir recompensas
- Gestionar las etiquetas del proyecto
- Crear y configurar proyectos (Modo Reputación o Modo Reparto de Beneficios)
Requisitos Previos
- Una cuenta de Shippy (regístrate aquí)
- Un token de acceso MCP (genera uno en Configuración de Usuario → Tokens de Acceso MCP)
Instalación Rápida (Cursor)
Si usas Cursor, haz clic en el botón "Añadir a Cursor" en tu configuración de usuario después de generar un token. Esto configurará automáticamente el servidor MCP.
Instalación Manual
Cursor
Añade esto a ~/.cursor/mcp.json:
{
"mcpServers": {
"shippy": {
"url": "https://shippy.sh/mcp",
"headers": {
"Authorization": "Bearer shp_YOUR_TOKEN"
}
}
}
}
Windsurf
Añade esto a ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"shippy": {
"serverUrl": "https://shippy.sh/mcp",
"headers": {
"Authorization": "Bearer shp_YOUR_TOKEN"
}
}
}
}
Nota: Windsurf usa
serverUrlen lugar deurlpara servidores HTTP. Consulta la documentación de Windsurf MCP.
Codex (OpenAI)
Codex usa configuración TOML en ~/.codex/config.toml. Tienes dos opciones:
Opción 1: Token directo (más simple)
Añade esto a ~/.codex/config.toml:
[mcp_servers.shippy]
url = "https://shippy.sh/mcp"
http_headers = { "Authorization" = "Bearer shp_YOUR_TOKEN" }
Opción 2: Variable de entorno (más seguro)
[mcp_servers.shippy]
url = "https://shippy.sh/mcp"
bearer_token_env_var = "SHIPPY_MCP_TOKEN"
Luego establece la variable de entorno en tu shell (añadir a ~/.zshrc o ~/.bashrc):
export SHIPPY_MCP_TOKEN="shp_YOUR_TOKEN"
Nota: Consulta la documentación de Codex MCP para más opciones de configuración.
Claude Desktop
Claude Desktop solo soporta servidores MCP basados en stdio, por lo que necesitarás mcp-remote para conectarte al endpoint HTTP de Shippy.
Añade a tu configuración de Claude Desktop:
- 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 también usa servidores basados en stdio. Puedes añadir Shippy mediante la CLI:
claude mcp add shippy -- npx -y mcp-remote https://shippy.sh/mcp --header "Authorization: Bearer shp_YOUR_TOKEN"
O añádelo al .mcp.json de tu proyecto:
### 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
## Seguridad
* Tu token MCP está vinculado a tu cuenta de Shippy
* Los tokens pueden ser revocados en cualquier momento desde tu configuración
* Cada token muestra cuándo fue usado por última vez para auditoría
* Recomendamos usar tokens separados para diferentes máquinas
* El prefijo de token `shp_` permite el escaneo de secretos de GitHub
## Recursos
* Especificación del Protocolo de Contexto de Modelo
* Documentación de Cursor MCP
* Documentación de Windsurf MCP
* Guía de Claude Desktop MCP
* mcp-remote en npm
## ¿Necesitas Ayuda?
Envía un correo a [email protected]