Developer Access & MCP Server Bridge
Your Access &
Agent Configuration
Authorize your local AI coding agent to connect to the LaunchNests Ship MCP control plane. Generate tailor-made configuration snippets for Claude Code, Cursor, Windsurf, and Codex in seconds.
30-Second Integration
Generate Your Agent MCP Config
Select your coding agent to see the exact file destination and JSON snippet.
~/.claude/mcp_config.json
{
"mcpServers": {
"ship-launchnests": {
"command": "npx",
"args": ["-y", "@repo/mcp@latest"],
"env": {
"LAUNCHNESTS_API_KEY": "YOUR_API_TOKEN_HERE"
}
}
}
}Paste this block inside your agent's MCP settings file.Transport: Stdio Pipe
3-Stage Agent Launch Sequence
1Terminal Login
Run our official CLI once in your terminal to create a local keychain pairing:
npx launchnests-ship login
2Configure Agent
Add the snippet above to your agent's MCP config. The agent automatically discovers the 7 launch tools.
Verified: Claude Code, Cursor, Windsurf, Codex, Antigravity
3Trigger Launch
Ask your agent to discover eligible directories and submit verified listings:
"Query ship-launchnests to launch my product in ./product-brief.json"
Zero Credential Transmission Guarantee
Your MCP server communicates strictly with platform metadata, submission constraints, and verified HTTP receipts. Passwords, session cookies, and 2FA tokens never leave your workstation.