npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gpt-5-plan-mcp

v1.0.0

Published

MCP server that generates structured development plans using GPT-5. npx-friendly, no local clone required

Readme

gpt-5-plan MCP Server (npx-first)

Generate clear development plans using GPT-5 with a structured Japanese YAML specification. This server runs via npx, so you don't need to clone or build locally.

Key features

  • npx-friendly: install-and-run with a single command
  • OpenAI-compatible: works with OpenAI or compatible endpoints via OPENAI_BASE_URL
  • Safe defaults: STDIO transport for broad MCP client compatibility

Requirements

  • Node.js 18+
  • An MCP-capable client (Cursor, Claude Code, VS Code MCP, Windsurf, etc.)
  • OpenAI API Key (OPENAI_API_KEY)

Getting started (npx, no clone required)

Most MCP clients support launching servers via npx. Use the standard configuration below and inject your environment variables.

Standard client config (JSON)

{
  "mcpServers": {
    "gpt-5-plan": {
      "command": "npx",
      "args": ["gpt-5-plan-mcp@latest"],
      "env": {
        "OPENAI_API_KEY": "sk-REPLACE_ME",
        "OPENAI_MODEL": "gpt-5",
        "OPENAI_TEXT_VERBOSITY": "low"
      },
      "autoStart": true
    }
  }
}

Claude Code (recommended)

Add this server with the CLI (no local clone needed):

claude mcp add gpt-5-plan -s user -e OPENAI_API_KEY="sk-REPLACE_ME" -e OPENAI_MODEL="gpt-5" -e OPENAI_TEXT_VERBOSITY="low" -- npx -y gpt-5-plan-mcp@latest

Remove if needed:

claude mcp remove gpt-5-plan

Cursor

Project-local example in .cursor/mcp.json:

{
  "mcpServers": {
    "gpt-5-plan": {
      "command": "npx",
      "args": ["gpt-5-plan-mcp@latest"],
      "env": {
        "OPENAI_API_KEY": "sk-REPLACE_ME",
        "OPENAI_MODEL": "gpt-5",
        "OPENAI_TEXT_VERBOSITY": "low"
      },
      "autoStart": true
    }
  }
}

VS Code / VS Code Insiders

Use the standard JSON config in your MCP extension, or install via your MCP client UI. Pin a version with @1.0.0 if you need stability.

Other clients (Windsurf, LM Studio, Goose, Qodo Gen, etc.)

  • Command: npx
  • Args: ["gpt-5-plan-mcp@latest"]
  • Env: OPENAI_API_KEY=... and optional variables below

Configuration

  • OPENAI_API_KEY (required): your API key
  • OPENAI_MODEL (default: gpt-5)
  • OPENAI_TEXT_VERBOSITY (low | medium | high, default: low)
  • OPENAI_BASE_URL (optional): set when using a compatible proxy endpoint
  • OPENAI_REASONING_EFFORT (low | medium | high, default: medium)

Notes:

  • The server chooses reasoning effort per request; defaults may be overridden in code paths for gpt5_plan.

Tools

  • gpt5_plan: Generate a YAML plan from inputs using the Japanese YAML spec

Input fields (all optional, strings): goal, context, user_request, scope, focus_features, project_type, non_functionals, constraints, kpi_preferences, paneling, panel_count, targets.

Example call (conceptual):

{
  "name": "gpt5_plan",
  "arguments": {
    "user_request": "新規機能Xの開発計画を作って",
    "scope": "full",
    "project_type": "web-app",
    "focus_features": "auth, i18n"
  }
}

Troubleshooting

  • 401 Unauthorized: verify OPENAI_API_KEY (no extra whitespace)
  • Use Node 18+
  • Do not console.log to stdout in STDIO servers; use stderr for logs
  • Claude logs: tail -n 50 -f ~/Library/Logs/Claude/mcp*.log

Local development (optional)

You can still clone and build locally if desired:

npm i
npm run build
node build/index.js

License

ISC