@atlashub/smartstack-mcp 1.8.0 → 1.9.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +54 -6
- package/dist/index.js +2081 -237
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/templates/controller.cs.hbs +18 -0
- package/templates/migrations/seed-permissions.cs.hbs +108 -0
- package/templates/migrations/seed-roles.cs.hbs +261 -0
package/README.md
CHANGED
|
@@ -55,24 +55,72 @@ Config file location:
|
|
|
55
55
|
claude mcp add context7 -s user -- npx -y @upstash/context7-mcp
|
|
56
56
|
```
|
|
57
57
|
|
|
58
|
+
## Update & Restart
|
|
59
|
+
|
|
60
|
+
### Update to Latest Version
|
|
61
|
+
|
|
62
|
+
```bash
|
|
63
|
+
# Global installation
|
|
64
|
+
npm update -g @atlashub/smartstack-mcp
|
|
65
|
+
|
|
66
|
+
# Verify version
|
|
67
|
+
npm list -g @atlashub/smartstack-mcp
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
### Restart the MCP Server
|
|
71
|
+
|
|
72
|
+
After updating, you must restart the MCP server for changes to take effect:
|
|
73
|
+
|
|
74
|
+
| Environment | How to Restart |
|
|
75
|
+
|-------------|----------------|
|
|
76
|
+
| **VS Code** | Close and reopen VS Code, or run `Developer: Reload Window` (Ctrl+Shift+P) |
|
|
77
|
+
| **Claude Code CLI** | Exit and restart Claude Code (`/exit` then `claude`) |
|
|
78
|
+
| **Claude Desktop** | Quit and reopen Claude Desktop application |
|
|
79
|
+
|
|
80
|
+
> **Note**: The MCP server loads tools at startup. New or updated tools won't appear until restart.
|
|
81
|
+
|
|
58
82
|
## Configuration
|
|
59
83
|
|
|
60
84
|
| Variable | Description | Required |
|
|
61
85
|
|----------|-------------|----------|
|
|
62
|
-
| `SMARTSTACK_PROJECT_PATH` | Path to your SmartStack.app project | Yes |
|
|
86
|
+
| `SMARTSTACK_PROJECT_PATH` | Path to your SmartStack.app project | Yes (auto-detects if not set) |
|
|
63
87
|
| `SMARTSTACK_API_URL` | SmartStack API URL | No |
|
|
64
88
|
| `LOG_LEVEL` | Logging level (debug, info, warn, error) | No |
|
|
65
89
|
|
|
90
|
+
### Auto-Detection
|
|
91
|
+
|
|
92
|
+
The server automatically detects:
|
|
93
|
+
- **Project path**: Uses current working directory if `SMARTSTACK_PROJECT_PATH` not set
|
|
94
|
+
- **Namespaces**: Extracts from `.csproj` file names (e.g., `Aurora.Domain.csproj` → `Aurora`)
|
|
95
|
+
- **Web folder**: Searches `web/*/`, `web/`, `client/`, `frontend/`, `ui/`, `src/web/`
|
|
96
|
+
|
|
66
97
|
## Features
|
|
67
98
|
|
|
68
|
-
### Tools
|
|
99
|
+
### Tools (13 total)
|
|
100
|
+
|
|
101
|
+
#### Core Tools
|
|
102
|
+
| Tool | Description |
|
|
103
|
+
|------|-------------|
|
|
104
|
+
| `validate_conventions` | Validate AtlasHub/SmartStack conventions (tables, migrations, services, namespaces) |
|
|
105
|
+
| `check_migrations` | Analyze EF Core migrations for conflicts and ordering issues |
|
|
106
|
+
| `scaffold_extension` | Generate code: feature, entity, service, controller, component, dto, validator, repository |
|
|
107
|
+
| `api_docs` | Get API documentation from Swagger/OpenAPI or controller files |
|
|
108
|
+
| `suggest_migration` | Suggest migration name following SmartStack conventions |
|
|
109
|
+
|
|
110
|
+
#### Frontend Tools
|
|
111
|
+
| Tool | Description |
|
|
112
|
+
|------|-------------|
|
|
113
|
+
| `scaffold_routes` | Generate frontend routes from backend NavRoute attributes |
|
|
114
|
+
| `validate_frontend_routes` | Validate frontend routes match backend NavRoutes |
|
|
115
|
+
| `scaffold_api_client` | Generate TypeScript API client with React Query hooks |
|
|
69
116
|
|
|
117
|
+
#### Test Tools
|
|
70
118
|
| Tool | Description |
|
|
71
119
|
|------|-------------|
|
|
72
|
-
| `
|
|
73
|
-
| `
|
|
74
|
-
| `
|
|
75
|
-
| `
|
|
120
|
+
| `scaffold_tests` | Generate test files for entities, services, controllers |
|
|
121
|
+
| `analyze_test_coverage` | Analyze test coverage and identify missing tests |
|
|
122
|
+
| `validate_test_conventions` | Validate test naming and structure conventions |
|
|
123
|
+
| `suggest_test_scenarios` | Suggest test scenarios based on code analysis |
|
|
76
124
|
|
|
77
125
|
### Resources
|
|
78
126
|
|