@typescape-ai/mcp 1.9.26 → 1.9.31
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 +3 -11
- package/dist/mcp.js +1032 -178
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Typescape MCP server for external agent harnesses that need canonical review, finding, decision, rules, corpus, and export workflows.
|
|
4
4
|
|
|
5
|
-
The published package
|
|
5
|
+
The published package exposes a broad multi-family tool registry for review, finding, workflow, rules, advisory, project, issue, and repository operations. MCP is the easiest discovery surface for agent clients such as Claude Code, Cursor, and Windsurf, but it is not the whole product surface. Typescape also ships the same operating model over the API and CLI.
|
|
6
6
|
|
|
7
7
|
## Requirements
|
|
8
8
|
|
|
@@ -97,9 +97,8 @@ Rules workflow:
|
|
|
97
97
|
|
|
98
98
|
1. `typescape_get_rules`
|
|
99
99
|
2. `typescape_check_content`
|
|
100
|
-
3. `typescape_import_rules`
|
|
101
|
-
4. `
|
|
102
|
-
5. `typescape_decide_rule_proposal`
|
|
100
|
+
3. `typescape_import_rules`
|
|
101
|
+
4. `typescape_rules_dashboard`
|
|
103
102
|
|
|
104
103
|
API/CLI parity:
|
|
105
104
|
|
|
@@ -164,12 +163,7 @@ Rules:
|
|
|
164
163
|
- `typescape_rules_pack` (compatibility-only)
|
|
165
164
|
- `typescape_check_content`
|
|
166
165
|
- `typescape_import_rules`
|
|
167
|
-
- `typescape_propose_rule`
|
|
168
|
-
- `typescape_list_rule_proposals`
|
|
169
|
-
- `typescape_list_rule_proposals_legacy`
|
|
170
166
|
- `typescape_rules_dashboard`
|
|
171
|
-
- `typescape_promote_rule_proposal`
|
|
172
|
-
- `typescape_decide_rule_proposal`
|
|
173
167
|
|
|
174
168
|
Repo, asset, and collection support:
|
|
175
169
|
|
|
@@ -182,8 +176,6 @@ Repo, asset, and collection support:
|
|
|
182
176
|
|
|
183
177
|
## Notes
|
|
184
178
|
|
|
185
|
-
- `typescape_list_rule_proposals_legacy` exists only as a bounded compatibility surface while the rules cutover finishes. New integrations should prefer `typescape_list_rule_proposals`.
|
|
186
|
-
- Approval submission is still a human action. MCP can request approval and read status, but it does not replace the reviewer/operator approval flow.
|
|
187
179
|
- Feature-gated tools return `feature_disabled` when the backing capability is off for the tenant.
|
|
188
180
|
|
|
189
181
|
## Response Shape
|