CleanSlice
Architecture docs and patterns for NestJS + Nuxt full-stack apps
使うべきか
品質と安全性
検出事項（3）
- LOWTool 'get-started' doesn't follow camelCase/snake_caseget-started 内
- LOWTool 'list-categories' doesn't follow camelCase/snake_caselist-categories 内
- LOWTool 'read-doc' doesn't follow camelCase/snake_caseread-doc 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"mcp": {
"url": "https://mcp.cleanslice.org/mcp"
}
}
}リモートエンドポイント
https://mcp.cleanslice.org/mcpstreamable-httpできること
ツール一覧
ツール（4）
🟢get-started
⚠️ CRITICAL: request this tool first before creating any code! Returns essential slice creation rules. READ THIS FIRST before creating any slices! Contains the MOST IMPORTANT naming rule: ALWAYS use SINGULAR names (user/ not users/).
入力スキーマ
{
"type": "object",
"properties": {},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list-categories
List all available documentation categories. Use this to discover what categories are available before searching.
入力スキーマ
{
"type": "object",
"properties": {},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢search(query, framework, sliceName, phase, feature, ...)
Search for relevant documentation. Use `list-categories` first to see available categories. Filter by query text, framework, phase, feature, category, or tags. Returns documents sorted by relevance.
入力スキーマ
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search query text (searches in document names, descriptions, and keywords)"
},
"framework": {
"type": "string",
"description": "Framework identifier (e.g., nestjs, nuxt)"
},
"sliceName": {
"type": "string",
"description": "Name of the slice to find documentation for"
},
"phase": {
"type": "string",
"enum": [
"initialization",
"setup",
"implementation",
"testing",
"deployment"
],
"description": "Development phase to filter by"
},
"feature": {
"type": "string",
"description": "Feature name (e.g., authentication, user-management, file-upload)"
},
"workingOn": {
"type": "string",
"enum": [
"api",
"app",
"admin",
"full-stack"
],
"description": "Which application you are currently working on"
},
"category": {
"type": "string",
"description": "Category filter (e.g., quickstart, pattern, best-practices)"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Array of tags to filter by"
},
"limit": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Max results to return (default: 5)"
},
"offset": {
"type": "integer",
"minimum": 0,
"description": "Number of results to skip for pagination (default: 0)"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢read-doc(path)
Read the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.
入力スキーマ
{
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Document path from search results"
}
},
"required": [
"path"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}コミュニティ
エビデンス