MCP for IDEs

Idea, niche validation and spec right in your IDE

Connect PeelBrief as an MCP server: your agent in Cursor, Claude Code or Codex checks demand on real Wordstat and Google Ads data and gets a build-ready spec.

What it does

analyze_idea - demand check, niche core, keywords with volumes, competitors and strong related niches (1-4 minutes, 24h cache)
generate_spec - prompt-spec for Cursor / Claude Code / Codex for an idea that passed validation
get_usage - remaining free quota and plan

Quota is shared with the site. Re-analyzing the same idea within 24h is free.

1. Access token

The token is tied to your account. Treat it like a password and never commit it.

2. Connect your IDE

Paste the config and restart the IDE or refresh its MCP server list.

Cursor

File: ~/.cursor/mcp.json

{
  "mcpServers": {
    "peelbrief": {
      "url": "https://peelbrief.app/api/mcp",
      "headers": {
        "Authorization": "Bearer pb_YOUR_TOKEN"
      }
    }
  }
}

Claude Code

Run in a terminal

claude mcp add --transport http --scope user peelbrief https://peelbrief.app/api/mcp \
  --header "Authorization: Bearer pb_YOUR_TOKEN"

Codex

File: ~/.codex/config.toml

[mcp_servers.peelbrief]
url = "https://peelbrief.app/api/mcp"
bearer_token_env_var = "PEELBRIEF_TOKEN"
tool_timeout_sec = 300

# export PEELBRIEF_TOKEN=pb_YOUR_TOKEN

Analysis takes up to 4 minutes. If Claude Code cuts it off, raise the timeout: MCP_TOOL_TIMEOUT=300000. Codex already has it in the config.

3. Ask your agent

Use peelbrief to validate this idea: an online tool that batch-converts PNG/JPG images to WebP for website owners. If the niche passes, generate a Cursor spec and save it to docs/SPEC.md.