LaunchChair

io.launchchairPublished by launchchair.iov0.4.10Updated Oct 24, 2026

Plan, validate, and build products and features with LaunchChair.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

LaunchChair's local MCP server lets an assistant plan, validate and build products and features through the LaunchChair platform.

What you can do
  • Plan, validate and build products and features with LaunchChair, per the registry description.
  • No tool list is published, so the exact actions the assistant can take are not documented here.
  • Runs as a local stdio process started with npx from the @launchchair/agent package.
When to use it
Consider it when you use LaunchChair for product or feature planning and validation and want an assistant to work with that material directly instead of copying it between tools.
Requirements
A local Node.js environment able to run the npm package @launchchair/agent via npx, on desktop only. A LaunchChair Agent API token, taken from Settings > API Access, supplied in the LAUNCHCHAIR_AGENT_TOKEN environment variable.
Before you install
The server requires a LaunchChair API token (LAUNCHCHAIR_AGENT_TOKEN); treat it as a secret and keep it out of shared configuration. The published description does not say which actions write, change or delete data in your LaunchChair workspace, so check the vendor documentation before granting access.

Installation

In SourceWeft

  1. Open LaunchChair in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.10LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.