AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Connect Idea Launch to Claude Code, Cursor, Codex, ChatGPT, or Claude over MCP. Create ideas, draft the brief and ad creative, and read your market read without leaving the tool you build in.
Developer toolsGitHub @apsquaredOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Idea Launch plugin for Claude Code, Cursor, Codex and other agents: validate a product idea with real ad traffic without leaving your editor.
Taken from the repository README
Loading the full README.
Read the full README ↗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.
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.
The MCP server exposes capability. It does not carry judgement, and that is the part that decides whether a test is any good:
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".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.
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.
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.
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.
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.
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.
MIT — see LICENSE. The package is manifests and skill documents; the Idea Launch service itself is governed by its terms of service.
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.