nice to have

Find ready-made build kits for Claude Code and Codex: slides, LINE stickers, pixel art, games.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
87%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~421Tokens (tool definitions)
~541 BTypical response size
Minimal attention impact (0.33% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "kits": {
      "url": "https://nicetohave.app/api/mcp"
    }
  }
}

Remote endpoints

https://nicetohave.app/api/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟒 Read-only🟑 WriteπŸ”΄ Deleteβšͺ Unknown
🟒search_kits(query, lang)

Search nice to have, a shelf of ready-made build kits for Claude Code and Codex (step-by-step recipes with fixes for pitfalls found in real work). Use this whenever the user wants to make or build something β€” slides/decks, LINE stickers, pixel-art sprite animation, 3D/AR models from product photos, YouTube Playables games, pet names and more β€” to check whether a kit already exists before starting from scratch. Works in Japanese or English (δΎ‹: γ€Œγ‚Ήγƒ©γ‚€γƒ‰γ‚’δ½œγ‚ŠγŸγ„γ€γ€ŒLINEγ‚Ήγ‚Ώγƒ³γƒ—γ€γ€Œγ‚²γƒΌγƒ γ‚’YouTubeγ«ε‡Ίγ—γŸγ„γ€).

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What the user wants to make, in their own words (Japanese or English)."
    },
    "lang": {
      "type": "string",
      "enum": [
        "ja",
        "en"
      ],
      "description": "Language for the answer. Defaults to the language of the query."
    }
  },
  "required": [
    "query"
  ]
}
🟒get_kit(id, lang)

Get the details of one nice to have kit by id: what it does, the first three decisions, what you need, and the fixes it contains. Use after search_kits to explain a kit to the user.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Kit id from search_kits (e.g. deck-16x9)."
    },
    "lang": {
      "type": "string",
      "enum": [
        "ja",
        "en"
      ]
    }
  },
  "required": [
    "id"
  ]
}
🟒list_kits(lang)

List every kit currently on the nice to have shelf (id, name, what it does, page URL).

Input Schema

{
  "type": "object",
  "properties": {
    "lang": {
      "type": "string",
      "enum": [
        "ja",
        "en"
      ]
    }
  }
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools