Skip to main content
Glama
README.md
# πŸ› οΈ Solution Engineer Notion MCP Assistant

> μ†”λ£¨μ…˜ μ—”μ§€λ‹ˆμ–΄(SE)의 업무 기둝, μœ μ§€λ³΄μˆ˜ μ‚¬μ΄νŠΈ 관리, 정기점검 일정 및 νŠΈλŸ¬λΈ”μŠˆνŒ… 내역을 **μžμ—°μ–΄ λŒ€ν™”λ‘œ λ…Έμ…˜(Notion)에 μžλ™ 적재 및 쑰회**ν•  수 μžˆλ„λ‘ μ§€μ›ν•˜λŠ” **MCP(Model Context Protocol) μ„œλ²„**μž…λ‹ˆλ‹€.

---

## πŸ“Œ μ£Όμš” κΈ°λŠ₯

* **🏒 μœ μ§€λ³΄μˆ˜ μ‚¬μ΄νŠΈ 관리 (`add_maintenance_site`)**
  * 고객사/μ‚¬μ΄νŠΈ 정보, λ‹΄λ‹Ήμž μ—°λ½μ²˜, 점검 μ£ΌκΈ°, λ°©λ¬Έ μœ„μΉ˜, μ‹œμŠ€ν…œ ν™˜κ²½μ„ λ…Έμ…˜ DB에 등둝 및 슀마트 κ°±μ‹ (Upsert)
* **πŸ“‹ 업무 일지 등둝 (`add_work_log`)**
  * μ˜¨μ‚¬μ΄νŠΈ/원격 정기점검 μˆ˜ν–‰ 일지, μ£Όμš” μž‘μ—… ν•­λͺ© 및 고객사 μš”μ²­μ‚¬ν•­ μžλ™ ν…œν”Œλ¦Ών™”
* **🚨 νŠΈλŸ¬λΈ”μŠˆνŒ… 사둀 적재 (`add_troubleshooting`)**
  * μž₯μ•  ν˜„μƒ, μ—λŸ¬ 둜그, 원인 뢄석, 쑰치 λ‚΄μš©, 재발 방지책을 κ΅¬μ‘°ν™”ν•˜μ—¬ 적재
* **πŸ” 이λ ₯ 및 사둀 검색 (`list_maintenance_sites`, `list_work_logs`, `search_troubleshooting`)**
  * κ³Όκ±° 점검 이λ ₯μ΄λ‚˜ μ—λŸ¬ ν‚€μ›Œλ“œ(예: SSL, Token, DB Timeout)λ₯Ό μ¦‰μ‹œ 검색

---

## πŸš€ λΉ λ₯Έ μ‹œμž‘ (Quick Start)

### 1. 사전 μš”κ΅¬μ‚¬ν•­
* **Node.js**: v18 이상 ꢌμž₯
* **Notion Integration Token**: [Notion Developers](https://www.notion.so/profile/integrations)μ—μ„œ λ°œκΈ‰

### 2. μ„€μΉ˜ 및 λΉŒλ“œ
```bash
# μ˜μ‘΄μ„± μ„€μΉ˜
npm install

# ν™˜κ²½ λ³€μˆ˜ μ„€μ •
cp .env.example .env
# .env νŒŒμΌμ„ μ—΄μ–΄ NOTION_API_KEY 및 3개 DB_ID μž…λ ₯

# TypeScript λΉŒλ“œ
npm run build

# λ…Έμ…˜ λ°μ΄ν„°λ² μ΄μŠ€ 연동 확인
npm run inspect
```

### 3. Antigravity / Gemini CLI μ‹€ν–‰ (μ˜¨λ””λ§¨λ“œ)
```bash
npm run se-agent
```

---

## βš™οΈ MCP 등둝 μ„€μ • (JSON)

Antigravity, Claude Desktop, λ˜λŠ” μ§€μ›λ˜λŠ” AI μ—μ΄μ „νŠΈμ— λ“±λ‘ν•˜μ—¬ μ‚¬μš©ν•  수 μžˆμŠ΅λ‹ˆλ‹€:

```json
{
  "mcpServers": {
    "se-notion": {
      "command": "node",
      "args": ["<ν”„λ‘œμ νŠΈκ²½λ‘œ>/dist/index.js"],
      "env": {
        "NOTION_API_KEY": "ntn_...",
        "MAINTENANCE_DB_ID": "3cd...",
        "WORKLOG_DB_ID": "3d9...",
        "TROUBLESHOOTING_DB_ID": "3d9..."
      }
    }
  }
}
```

---

## πŸ“š κ΄€λ ¨ λ¬Έμ„œ
* [초기 ν™˜κ²½ ꡬ좕 및 μ„ΈλΆ€ κ°€μ΄λ“œ (SETUP_GUIDE.md)](./SETUP_GUIDE.md)
* [ν–₯ν›„ κ°œμ„  μ œμ•ˆ 및 κΈ°λŠ₯ λ‘œλ“œλ§΅ (IMPROVEMENTS.md)](./IMPROVEMENTS.md)

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct resource (maintenance sites, work logs, troubleshooting) with a clear action (add/list/search), so selection is generally unambiguous. Minor overlap exists between add_work_log and add_troubleshooting since a troubleshooting record could be seen as a work log, but the descriptions differentiate them adequately.

Naming Consistency5/5

All six tools follow a clean verb_noun pattern (add_, list_, search_ + resource), with no mixed conventions or vague verbs. The pattern is entirely predictable and readable.

Tool Count4/5

Six tools is well-scoped for a Notion-based maintenance tracking server covering three resource types. The set is slightly thin in that each resource gets only one or two operations, but every tool earns its place.

Completeness3/5

The surface covers create/list for sites and work logs and add/search for troubleshooting, plus site upsert. However, update and delete operations are absent for work logs and troubleshooting, and there is no single-item retrieval, leaving notable lifecycle gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues