Launchdog

dev.launchdogPublished by launchdog.devOfficial publisherv1.0.0Updated Oct 27, 2026

Launch your product on Launchdog's weekly board from your coding agent: list, verify, badge, book.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Launchdog MCP endpoint that lets a coding agent list a product on Launchdog's weekly board, verify it, add a badge and book a slot.

What you can do
  • List a product on Launchdog's weekly launch board
  • Verify a submitted product
  • Add a Launchdog badge to a product
  • Book a launch slot on the board
When to use it
Use it when you want to submit and schedule a product launch on Launchdog directly from a coding agent instead of the web dashboard.
Requirements
A remote MCP endpoint at launchdog.dev over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
The server publishes product information to a public launch board and can book launch slots, so actions are visible and may be hard to undo. Access is granted through an OAuth account sign-in.

Installation

In SourceWeft

  1. Open Launchdog in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.launchdog%2Fmaker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "launchdog": {
      "type": "http",
      "url": "https://launchdog.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Launchdog integrations

Launchdog (read-only)

dev.launchdogOfficial publisher

Launchdog (read-only)'s hosted MCP server, published by launchdog.dev; no sign-in required; Streamable HTTP; 4 tools.

Streamable HTTPWeb executable
4 toolsOct 26, 2026