mcp-consultant-tools 0.4.6 → 1.0.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 +49 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -97,7 +97,12 @@ For local development and testing, you can run the server directly from your clo
|
|
|
97
97
|
|
|
98
98
|
### Environment Variables Reference
|
|
99
99
|
|
|
100
|
-
**PowerPlatform
|
|
100
|
+
**Note:** Both PowerPlatform and Azure DevOps integrations are optional. You can configure only the services you need:
|
|
101
|
+
- PowerPlatform only: Set `POWERPLATFORM_*` variables
|
|
102
|
+
- Azure DevOps only: Set `AZUREDEVOPS_*` variables
|
|
103
|
+
- Both: Set all variables
|
|
104
|
+
|
|
105
|
+
**PowerPlatform/Dataverse (Optional):**
|
|
101
106
|
- `POWERPLATFORM_URL`: Your PowerPlatform environment URL
|
|
102
107
|
- `POWERPLATFORM_CLIENT_ID`: Azure AD app registration client ID
|
|
103
108
|
- `POWERPLATFORM_CLIENT_SECRET`: Azure AD app registration client secret
|
|
@@ -963,6 +968,49 @@ AZUREDEVOPS_ENABLE_WIKI_WRITE=true
|
|
|
963
968
|
# PAT with: vso.wiki (read/write), vso.work_write (read/write), vso.search (read)
|
|
964
969
|
```
|
|
965
970
|
|
|
971
|
+
## Development & Release Strategy
|
|
972
|
+
|
|
973
|
+
This project follows a structured branching strategy for development and releases:
|
|
974
|
+
|
|
975
|
+
### Branch Strategy
|
|
976
|
+
|
|
977
|
+
- **`feature/*` branches**: For active development of new features
|
|
978
|
+
- Create feature branches off `main`
|
|
979
|
+
- Develop and test changes locally
|
|
980
|
+
- Do NOT publish to npm from feature branches
|
|
981
|
+
|
|
982
|
+
- **`release/*` branches**: For testing versions before release
|
|
983
|
+
- Used to test and validate changes before merging to main
|
|
984
|
+
- Do NOT publish to npm from release branches
|
|
985
|
+
- Example: `release/1.0`, `release/2.0`
|
|
986
|
+
|
|
987
|
+
- **`main` branch**: Production-ready code
|
|
988
|
+
- **ONLY** publish to npm when main branch is updated
|
|
989
|
+
- Merge feature/release branches to main when ready
|
|
990
|
+
- Publishing workflow:
|
|
991
|
+
1. Merge changes to `main`
|
|
992
|
+
2. Update version: `npm version patch|minor|major`
|
|
993
|
+
3. Publish: `npm publish`
|
|
994
|
+
4. Push to GitHub: `git push && git push --tags`
|
|
995
|
+
|
|
996
|
+
### Local Development Setup
|
|
997
|
+
|
|
998
|
+
For local testing during development (feature/release branches):
|
|
999
|
+
|
|
1000
|
+
```json
|
|
1001
|
+
{
|
|
1002
|
+
"mcpServers": {
|
|
1003
|
+
"mcp-consultant-tools-dev": {
|
|
1004
|
+
"command": "node",
|
|
1005
|
+
"args": ["/absolute/path/to/mcp-consultant-tools/build/index.js"],
|
|
1006
|
+
"env": { ... }
|
|
1007
|
+
}
|
|
1008
|
+
}
|
|
1009
|
+
}
|
|
1010
|
+
```
|
|
1011
|
+
|
|
1012
|
+
This allows you to test changes locally without publishing to npm.
|
|
1013
|
+
|
|
966
1014
|
## License
|
|
967
1015
|
|
|
968
1016
|
MIT
|