super-feedback-mcp 0.2.1 → 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/dist/index.js +8 -2
- package/package.json +1 -1
- package/src/index.ts +8 -2
package/dist/index.js
CHANGED
|
@@ -39,7 +39,7 @@ async function callConvexAPI(endpoint, options) {
|
|
|
39
39
|
// Create MCP server
|
|
40
40
|
const server = new McpServer({
|
|
41
41
|
name: "super-feedback",
|
|
42
|
-
version: "0.2.
|
|
42
|
+
version: "0.2.2",
|
|
43
43
|
});
|
|
44
44
|
// Tool 1: Get feedback summary (lightweight overview)
|
|
45
45
|
server.registerTool("get_feedback_summary", {
|
|
@@ -50,7 +50,13 @@ Returns:
|
|
|
50
50
|
- Total comment count
|
|
51
51
|
- Open (unresolved) count
|
|
52
52
|
- Resolved count
|
|
53
|
-
- List of
|
|
53
|
+
- List of comments with index, ID, feedback text, status, and page path
|
|
54
|
+
|
|
55
|
+
Comments are sorted by createdAt ASCENDING (oldest first), so:
|
|
56
|
+
- Index 1 = the FIRST/OLDEST comment added
|
|
57
|
+
- Index N = the NEWEST/most recent comment
|
|
58
|
+
|
|
59
|
+
This matches the order users see comments in the UI, so when a user says "fix comment #3", you can use index 3 to find the exact comment they're referring to.
|
|
54
60
|
|
|
55
61
|
Use this first to understand what feedback exists, then use get_comment_details for full context on specific comments.`,
|
|
56
62
|
inputSchema: {
|
package/package.json
CHANGED
package/src/index.ts
CHANGED
|
@@ -115,7 +115,7 @@ async function callConvexAPI<T>(endpoint: string, options?: RequestInit): Promis
|
|
|
115
115
|
// Create MCP server
|
|
116
116
|
const server = new McpServer({
|
|
117
117
|
name: "super-feedback",
|
|
118
|
-
version: "0.2.
|
|
118
|
+
version: "0.2.2",
|
|
119
119
|
});
|
|
120
120
|
|
|
121
121
|
// Tool 1: Get feedback summary (lightweight overview)
|
|
@@ -129,7 +129,13 @@ Returns:
|
|
|
129
129
|
- Total comment count
|
|
130
130
|
- Open (unresolved) count
|
|
131
131
|
- Resolved count
|
|
132
|
-
- List of
|
|
132
|
+
- List of comments with index, ID, feedback text, status, and page path
|
|
133
|
+
|
|
134
|
+
Comments are sorted by createdAt ASCENDING (oldest first), so:
|
|
135
|
+
- Index 1 = the FIRST/OLDEST comment added
|
|
136
|
+
- Index N = the NEWEST/most recent comment
|
|
137
|
+
|
|
138
|
+
This matches the order users see comments in the UI, so when a user says "fix comment #3", you can use index 3 to find the exact comment they're referring to.
|
|
133
139
|
|
|
134
140
|
Use this first to understand what feedback exists, then use get_comment_details for full context on specific comments.`,
|
|
135
141
|
inputSchema: {
|