@vespermcp/mcp-server 1.2.29 → 1.3.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.
@@ -0,0 +1,116 @@
1
+ # Vesper MCP Migration Guide (Pre-Production)
2
+
3
+ This guide documents the MCP surface consolidation for Vesper as a general-purpose data layer.
4
+
5
+ ## What Changed
6
+
7
+ - Removed: `configure_kaggle`
8
+ - Merged quality tools into `quality_analyze`
9
+ - Merged fusion tools into `fuse`
10
+ - Merged lineage tools into `lineage`
11
+ - Kept separate by design: `vesper_normalize_schema` and `vesper_convert_format`
12
+
13
+ ## Deprecation Map
14
+
15
+ - `configure_kaggle` -> `configure_keys`
16
+ - Map: `username` -> `kaggle_username`, `key` -> `kaggle_key`
17
+
18
+ - `analyze_quality` -> `quality_analyze` with `operation="dataset"`
19
+ - `analyze_image_quality` -> `quality_analyze` with `operation="image"`
20
+ - `analyze_media_quality` -> `quality_analyze` with `operation="media"`
21
+ - `generate_quality_report` -> `quality_analyze` with `operation="report"`
22
+
23
+ - `fuse_datasets` -> `fuse` with `operation="tabular"`
24
+ - `vesper_fuse` -> `fuse` with `operation="web"`
25
+
26
+ - `get_lineage` -> `lineage` with `operation="get"`
27
+ - `diff_lineage_versions` -> `lineage` with `operation="diff"`
28
+
29
+ ## Migration Examples
30
+
31
+ ### Credentials
32
+
33
+ Old:
34
+
35
+ ```json
36
+ { "name": "configure_kaggle", "arguments": { "username": "u", "key": "k" } }
37
+ ```
38
+
39
+ New:
40
+
41
+ ```json
42
+ {
43
+ "name": "configure_keys",
44
+ "arguments": {
45
+ "kaggle_username": "u",
46
+ "kaggle_key": "k"
47
+ }
48
+ }
49
+ ```
50
+
51
+ ### Quality
52
+
53
+ Old:
54
+
55
+ ```json
56
+ { "name": "analyze_quality", "arguments": { "dataset_id": "my_ds" } }
57
+ ```
58
+
59
+ New:
60
+
61
+ ```json
62
+ {
63
+ "name": "quality_analyze",
64
+ "arguments": {
65
+ "operation": "dataset",
66
+ "dataset_id": "my_ds"
67
+ }
68
+ }
69
+ ```
70
+
71
+ ### Fusion
72
+
73
+ Old:
74
+
75
+ ```json
76
+ { "name": "fuse_datasets", "arguments": { "sources": ["a", "b"], "strategy": "concat" } }
77
+ ```
78
+
79
+ New:
80
+
81
+ ```json
82
+ {
83
+ "name": "fuse",
84
+ "arguments": {
85
+ "operation": "tabular",
86
+ "sources": ["a", "b"],
87
+ "strategy": "concat"
88
+ }
89
+ }
90
+ ```
91
+
92
+ ### Lineage
93
+
94
+ Old:
95
+
96
+ ```json
97
+ { "name": "get_lineage", "arguments": { "dataset_id": "my_ds" } }
98
+ ```
99
+
100
+ New:
101
+
102
+ ```json
103
+ {
104
+ "name": "lineage",
105
+ "arguments": {
106
+ "operation": "get",
107
+ "dataset_id": "my_ds"
108
+ }
109
+ }
110
+ ```
111
+
112
+ ## Notes for Agent Builders
113
+
114
+ - Prefer the new unified tools for all new integrations.
115
+ - Do not merge `vesper_normalize_schema` and `vesper_convert_format` unless your client can present explicit operation-specific schemas.
116
+ - If you have old prompts/tool maps, migrate now before production rollout.