MCP server
launch from Claude Code or Cursor.
connect your AI assistant to ShipDesk.dev once. then, inside your project, ask it to launch: it reads your README and website, writes the launch and makes the draft. you pick the day and send it in.
you, in Claude Code or Cursor:
> launch this project on ShipDesk
your assistant:
read the README and pocketplan.app
✓ create_launch_draft: Pocketplan
✓ add_screenshot: 2 screenshots
draft ready → pick a launch day and send it in
- 1. make a key in settings. it is free.
- 2. connect your assistant with one of the setups below.
- 3. ask it to launch your project on ShipDesk.
- 4. finish on the site: check the draft, pick a launch day, send it in.
- sign up free to get a key
connect your assistant
put your own key where it says sd_your_key.
Claude Code
run this once in your terminal:
claude mcp add --transport http shipdesk https://shipdesk.dev/mcp \
--header "Authorization: Bearer sd_your_key"Cursor
add this to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):
{
"mcpServers": {
"shipdesk": {
"url": "https://shipdesk.dev/mcp",
"headers": { "Authorization": "Bearer sd_your_key" }
}
}
}VS Code
add this to .vscode/mcp.json:
{
"servers": {
"shipdesk": {
"type": "http",
"url": "https://shipdesk.dev/mcp",
"headers": { "Authorization": "Bearer sd_your_key" }
}
}
}Claude Desktop
add this to claude_desktop_config.json (it needs Node.js):
{
"mcpServers": {
"shipdesk": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://shipdesk.dev/mcp",
"--header", "Authorization: Bearer sd_your_key"]
}
}
}what your assistant can do
create_launch_draftStart a new launch on ShipDesk.dev as a private draft. Give at least one link: website, app_store or google_play. Name, one line, description and tags are read from the website when left out. Returns the draft with an edit_link where the maker picks a launch day and sends it in.
update_launch_draftChange a draft's links, name, one line, description or tags. Only the fields you give change. A launch already in review or live can only change its one line, description and tags.
add_screenshotAdd a screenshot to a launch: a png, jpg or webp up to 2 MB, either as a public https image_url or as image_base64. The first screenshot is the cover. Use real screenshots of the product, never made-up ones.
my_launchesList the maker's launches with their status (draft, pending, scheduled, approved, denied), links and what each draft still needs.
search_launchesSearch the products live on ShipDesk.dev by name, line or category.
list_tagsThe categories a launch can be filed under.
or use the CLI
no AI assistant needed: the same tools, from any terminal, with the same key. it needs Node 18 or newer.
npx shipdesk login # paste your key once
npx shipdesk launch yourproduct.com # a draft, filled in from your site
npx shipdesk screenshot <id> ./cover.png # the first one is the cover
npx shipdesk list # what each draft still needslaunch and update also take --name, --line, --description and --tags. run npx shipdesk --help for everything.
questions
can my AI assistant publish or pay for a launch?
no. it can make and change drafts and add screenshots. picking the launch day, sending it in for review and paying for a plan stay with you, on the site.
what does it cost?
nothing. the MCP server, the CLI and API keys are free for every account. the writing happens in your own AI assistant.
what happens to my key?
each account has one key. it is shown once when you make it, and ShipDesk keeps only a hash of it. you can replace or remove it in settings at any time, and anything using the old key stops working at once.
what is MCP?
the Model Context Protocol: an open standard that lets AI assistants use tools from other services. ShipDesk speaks it at https://shipdesk.dev/mcp.
