Integrations

Validate before your build agent scaffolds a line of code.

Trigvale ships an MCP server (@trigvale/mcp) that exposes the validation endpoint to any MCP-aware build agent. Wire it into Cursor, Claude Code, Codex, or ChatGPT-with-MCP and the agent can call validate_idea on a raw founder idea before generating a project skeleton.

1. Issue an agent token

Agent tokens are available on the Integrate plan. Issue and revoke them in Settings. Token format is tv_…; the plaintext is shown exactly once at issue time. Treat it like a password.

2. Drop the MCP config into your agent

Same JSON shape across every MCP-aware client. The transport is stdio; no daemon, no port. Your agent runs npx -y @trigvale/mcp on first tool call.

{
  "mcpServers": {
    "trigvale": {
      "command": "npx",
      "args": ["-y", "@trigvale/mcp"],
      "env": {
        "TRIGVALE_AGENT_TOKEN": "tv_..."
      }
    }
  }
}

Where the config goes, by client:

ClientConfig location
Claude CodeProject's `.mcp.json` (or run `claude mcp add`)
Cursor`~/.cursor/mcp.json`
CodexCodex MCP config (same shape, stdio transport)
ChatGPT (with MCP)Settings → Integrations → MCP servers

3. Tell the agent to use it

The MCP server exposes one tool today: validate_idea(rawIdea, save?). A minimal system-prompt nudge that flips the behaviour on:

Before scaffolding a new project from a founder idea, call
trigvale.validate_idea(rawIdea). Show the verdict + the dominant
archetype's structural cautions to the user. Only proceed with
scaffolding if the user confirms after reading them.

What gets returned

What we don't claim

Trigvale exposes assumptions; it does not predict outcomes. The rubric score is one term in a noisy equation dominated by execution, marketing, distribution, timing, and luck. See methodology for the full stance.