mason-context 0.2.0 → 0.2.2
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/LICENSE +21 -0
- package/README.md +7 -1
- package/dist/bin/mason-mcp.js +1 -1
- package/dist/bin/mason-mcp.js.map +1 -1
- package/dist/bin/mason.js +1 -1
- package/dist/bin/mason.js.map +1 -1
- package/dist/src/cli.js +1 -1
- package/dist/src/cli.js.map +1 -1
- package/package.json +14 -4
package/dist/src/cli.js
CHANGED
|
@@ -1786,7 +1786,7 @@ function createMcpServer() {
|
|
|
1786
1786
|
const server = new McpServer(
|
|
1787
1787
|
{
|
|
1788
1788
|
name: "mason",
|
|
1789
|
-
version: "0.
|
|
1789
|
+
version: "0.2.2"
|
|
1790
1790
|
},
|
|
1791
1791
|
{
|
|
1792
1792
|
instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."
|