Idea Launch

io.idea-launchPublished by idea-launch.ioOfficial publisherv1.0.1Updated Oct 26, 2026

Validate SaaS and app ideas with real, managed ad tests from your coding agent.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Idea Launch runs a small managed ad test for a SaaS or app idea and returns a market read — click-through rate, signups, a validation score and a recommended…

What you can do
  • Set up a managed ad test for a SaaS or app idea, or for a product already shipped, from inside a coding agent.
  • Read the result of a test as a market read: click-through rate, signups, a validation score and a recommended next move.
  • Use bundled skills that help write a brief worth testing and interpret a result honestly.
  • Connect through a browser sign-in rather than an API key.
When to use it
Useful when you want early market evidence on a product idea or positioning without leaving your editor, and want the result framed as evidence about a positioning rather than proof about a business.
Requirements
Remote MCP server reached over streamable HTTP at the provider's endpoint; no local package or API key. OAuth sign-in is required: the first call opens a browser sign-in over OAuth 2.1 with dynamic client registration, and until you authenticate the server answers 401. Paid tests are started in the provider's web app.
Before you install
Tests are paid ad runs; the README states no agent can spend money and each paid test is confirmed by the user in the web app, so expect a purchase step outside the assistant. Results are evidence about a positioning, not proof about a business, and a low-confidence score is easy to misread. Sign-in grants the server access to your account; the bundled config files carry no credentials by design.

Installation

In SourceWeft

  1. Open Idea Launch 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/io.idea-launch%2Fidea-launch/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": {
    "idea-launch": {
      "type": "http",
      "url": "https://www.idea-launch.io/api/mcp"
    }
  }
}

README

Idea Launch — Agent Plugin

Idea Launch runs a small, managed ad test for a SaaS or app idea, or for a product you already shipped, and returns a market read: click-through rate, signups, a validation score and a recommended next move. This plugin lets Claude Code, Cursor, Codex and other coding agents set up that test and read the result without leaving the editor. It connects the Idea Launch MCP server (browser sign-in, no API key) and adds two skills: one for writing a brief worth testing, one for reading the result honestly. No agent can spend money; you start each paid test in the web app.

In Claude Code:

/plugin marketplace add apsquared/idea-launch-plugin/plugin install idea-launch@apsquared

The two skills only, for any agent that reads SKILL.md (connect the server as well): npx skills add apsquared/idea-launch-plugin. Every other client, and the MCP server on its own: https://www.idea-launch.io/mcp.

The package

A portable Agent Plugins v1.0.0 package that connects the Idea Launch MCP server and adds the judgement needed to use it well.

One package, two manifest formats. The Agent Plugins entrypoints sit at the root; Claude Code reads its own manifests from .claude-plugin/ and .mcp.json. Both formats read the same skills/ directory, unmodified.

agent-plugin/├── plugin.json                          # Agent Plugins manifest├── mcp.json                             # Agent Plugins MCP server (streamable-http)├── .claude-plugin/│   ├── plugin.json                      # Claude Code manifest│   └── marketplace.json                 # Claude Code marketplace entry (source ./)├── .mcp.json                            # Claude Code MCP server (http)├── LICENSE                              # MIT└── skills/    ├── reading-a-market-read/SKILL.md   # how to interpret a result honestly    └── setting-up-an-idea-test/SKILL.md # how to get a test worth paying for

The two MCP files describe the same server at the same URL and carry no credentials. They differ only in the name each format gives the transport: Agent Plugins calls it streamable-http, Claude Code calls it http.

Why a plugin and not just the MCP server

The MCP server exposes capability. It does not carry judgement, and that is the part that decides whether a test is any good:

  • A validationScore of 45 at low confidence, on a traffic_backed read, is easy to misreport as "mixed signal, refine the angle". It is closer to "not settled, and it cannot speak to demand at all".
  • A targetCustomer of "founders" produces targeting that underperforms, and the user blames the product rather than the brief.

Both skills also restate the two hard rules: an Ad Run is evidence about a positioning rather than proof about a business, and no agent can spend the user's money — starting a run is confirmed by the user in the web app.

Installing — Agent Plugins clients

Install through any client that supports the Agent Plugins format; the client handles discovery, installation, and permissions. Installing the plugin also configures the MCP server, so there is no separate connection step.

For a client that does not support the format yet, connect the MCP server directly — see https://www.idea-launch.io/mcp.

Installing — Claude Code

Add the marketplace, then install from it:

/plugin marketplace add apsquared/idea-launch-plugin/plugin install idea-launch@apsquared

Then complete the sign-in:

/mcp

Pick idea-launch and authenticate. Until you do, the server answers 401 and Claude Code reports it as failed to connect — that is the unauthenticated state, not a broken install. The skills load either way; the tools need the sign-in.

Installing — Cursor

[Add to Cursor]

The button connects the MCP server only. Cursor also supports the Agent Plugins format, which adds the skills too — see https://cursor.com/docs/plugins.

Installing — skills only, any agent

For an agent that reads SKILL.md files but not this plugin format, install the two skills with the skills.sh CLI:

npx skills add apsquared/idea-launch-plugin

That installs the skills, not the server. Connect the MCP server as well (https://www.idea-launch.io/mcp), since the skills call its tools.

Auth

None to configure. Neither mcp.json nor .mcp.json carries credentials by design. The first call opens a browser sign-in over OAuth 2.1 with dynamic client registration.

License

MIT — see LICENSE. The package is manifests and skill documents; the Idea Launch service itself is governed by its terms of service.

Conformance

This package targets Agent Plugins v1.0.0 and the Agent Skills specification, and additionally ships the Claude Code plugin layout. Conformance is enforced by an automated check on every change: the manifest's closed field set and name rules, the streamable-http server shape, and each skill's frontmatter — including that a skill's name matches its directory. The check also asserts that mcp.json carries no credential-shaped values, since this package is distributed publicly.

Source: README.md at commit 999d7e5

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

2
  1. v1.0.1LatestOct 26, 2026
  2. v1.0.0Oct 13, 2026

Score

85% 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
  • License10 pts