# ReAI MCP Server

MCP (Model Context Protocol) server that provides Kiro Web access to ReAI's core capabilities for FSM report migration analysis.

## Tools

| Tool | Description |
|------|-------------|
| `reai_search_v10v11` | Fuzzy search 967+ S3/Lawson to FSM report mappings with navigation paths |
| `reai_v10v11_modules` | List all FSM modules with report counts |
| `reai_v10v11_stats` | Database overview: totals, module breakdown |
| `reai_search_bre100` | Fuzzy search 617+ report migration patterns from 11 clients |
| `reai_bre100_high_value` | Get standardization opportunities (multi-client patterns) |
| `reai_bre100_stats` | Pattern registry statistics by process and complexity |
| `reai_generate_columnar` | Generate Columnar LPL code package (.form, .list, .field, .csv) |

## Installation

### For Kiro Web (recommended)

Add to Kiro Web MCP settings:

```json
{
  "mcpServers": {
    "reai": {
      "command": "npx",
      "args": ["-y", "github:van0219/reai-mcp#main"],
      "env": {
        "REAI_DATA_DIR": "/path/to/reai_web/data"
      }
    }
  }
}
```

### For Local Development

```bash
cd reai-mcp
npm install
npm start
```

## Environment Variables

| Variable | Description | Default |
|----------|-------------|---------|
| `REAI_DATA_DIR` | Directory containing SQLite databases | `./data` (bundled with package) |
| `REAI_V10V11_DB` | Full path to v10v11_mapping.db | `$REAI_DATA_DIR/v10v11_mapping.db` |
| `REAI_BRE100_DB` | Full path to bre100_registry.db | `$REAI_DATA_DIR/bre100_registry.db` |

**Note:** You typically don't need to set any env vars. The databases are bundled. Only set `REAI_DATA_DIR` if you want to point to a different copy (e.g., the Hub's `reai_web/data/` for live writes).

## Database Requirements

The server **bundles** two SQLite database files in its `data/` folder — they ship with the package automatically:

1. **v10v11_mapping.db** (352KB) — S3/Lawson to FSM report mapping
   - `LawsonReportMapping` table: id, report_code, report_name, status, module, description
   - `FSMNavigation` table: id, report_id, navigation_path, path_order

2. **bre100_registry.db** (283KB) — BRE-100 pattern registry
   - `patterns` table: id, report_name, business_process, fsm_classification, navigation, future_state, tool_selection, timeline_estimate, complexity, comments, utilization_count, client_projects, created_at, updated_at

No additional setup needed — `npx github:van0219/reai-mcp#main` includes everything.

## Updating the Databases

The databases grow as new clients are onboarded and patterns are discovered. To update:

### From the Hub (Kiro IDE)

The Hub's native ReAI tool writes directly to `reai_web/data/*.db` via `better-sqlite3`. When patterns are added/edited in the Hub UI, those databases are the source of truth.

To sync updates to the MCP server:

1. Copy the updated databases from the Hub repo to the MCP repo:
   ```bash
   cp reai_web/data/v10v11_mapping.db reai-mcp/data/
   cp reai_web/data/bre100_registry.db reai-mcp/data/
   ```
2. Commit and push:
   ```bash
   cd reai-mcp
   git add data/
   git commit -m "Update databases (new patterns/mappings)"
   git push
   ```
3. New Kiro Web sessions auto-fetch the latest `#main` — no config change needed.

### From Kiro Web

Ask Kiro: "Copy the latest ReAI databases from the Hub repo to the reai-mcp repo and push them."

Kiro Web can clone both repos, copy the `.db` files from `fsm_innovationhub_landingpage/reai_web/data/` to `reai-mcp/data/`, and push.

### Database Locations Summary

| Context | Location | Writable |
|---------|----------|----------|
| Hub (desktop) | `reai_web/data/*.db` | Yes (via UI + IPC handlers) |
| MCP server (Kiro Web) | `reai-mcp/data/*.db` (bundled) | Read-only (query only) |
| Override | Set `REAI_DATA_DIR` env var | Depends on path |

## Example Usage

### Search V10-V11 Mappings

```
Use reai_search_v10v11 with query "GL Transaction" to find how S3 General Ledger reports map to FSM.
```

### Search BRE-100 Patterns

```
Use reai_search_bre100 with query "asset depreciation" to find known migration patterns.
```

### Generate Columnar Report

```
Use reai_generate_columnar with:
- report_name: "GLTransactionDetail"
- business_class: "GLTransactionDetail"
- fields: [{"name": "Company"}, {"name": "TransactionAmount"}, {"name": "PostingDate"}]
```

## Author

FSM Innovation Hub — Infor Manila FSM Team