docs/src/app/api/internal/[transport]/route.ts (9)

7-7: Type import is appropriate. Consider typing helper returns explicitly.
Import looks good. Recommend annotating extractOpenApiDetails to return Promise for consistency with getDocsById.

Apply this diff to the function signature at Lines 14-17:

-async function extractOpenApiDetails(
+async function extractOpenApiDetails(
   content: string,
   page: { data: { title: string, description?: string } },
-) {
+): Promise<CallToolResult> {

---

14-96: Harden OpenAPI helper and path handling (optional).

• Consider resolving specFile relative to a known root to avoid brittle relative paths.
• Regex parsing of JSX props is brittle; OK as a stopgap, but document or add TODO to replace with a proper parser.

---

124-128: Avoid potential unhandled promise rejections from PostHog capture.
Prefix with void (or .catch(() => {})) since posthog-node v4 methods are async.

-  nodeClient?.capture({
+  void nodeClient?.capture({
     event: "get_docs_by_id",
     properties: { id },
     distinctId: "mcp-handler",
   });

---

130-133: Mark not-found as error and include the requested id.
Improves client handling and observability.

-  if (!page) {
-    return { content: [{ type: "text", text: "Page not found." }] };
-  }
+  if (!page) {
+    return {
+      content: [{ type: "text", text: `Page not found: ${id}` }],
+      isError: true,
+    };
+  }

---

168-171: Deduplicate fallback paths to avoid content/docs/docs/...
If page.file.path already contains a docs/api prefix, this prevents broken double-prefixed attempts.

-    const altPaths = [
-      `content/docs/${page.file.path}`,
-      `content/api/${page.file.path}`,
-    ];
+    const altPaths = [
+      `content/docs/${page.file.path}`,
+      `content/api/${page.file.path}`,
+    ].filter((p) => p !== filePath);

---

349-376: Capabilities: add search/fetch looks good; consider aligning existing tool names.
Your newly added capability entries for search/fetch match the tool names. For consistency and discoverability, consider aligning earlier capability keys (listAvailableDocs, getDocById, getStackAuthSetupInstructions) to the actual registered tool names (list_available_docs, get_docs_by_id, get_stack_auth_setup_instructions).

If you decide to align, update the keys above accordingly (outside this hunk):

// In capabilities.tools:
list_available_docs: { /* ... */ },
get_docs_by_id: { /* ... */ },
get_stack_auth_setup_instructions: { /* ... */ },

Note: Verify @vercel/mcp-adapter and client expectations; some clients may use capabilities to resolve tools by key.

---

123-219: Minor content formatting consistency.
In several places, description may be undefined; consider using nullish coalescing to avoid “undefined” appearing in output.

Example change:

- text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nContent:\n${content}`,
+ text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ''}\nContent:\n${content}`,

---

9-11: PostHog SDK best practices (non-blocking analytics).
Current usage is fine; optionally add a process-exit hook to flush/shutdown in long-lived processes, or use captureImmediate in serverless. Not blocking for this PR.

---

281-309: Use structuredContent for JSON results
MCP SDK doesn’t define a “json” content type. When CallToolResult supports structuredContent, return your { results } via a structuredContent field instead of embedding JSON in a text item; otherwise fall back to the existing content: [{ type: 'text', text: JSON.stringify({ results }) }].

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

docs/src/app/api/internal/[transport]/route.ts (3)

73-81: Mark OpenAPI spec read failure as an error.

Return includes error text but lacks isError:true, making it harder for clients to detect failures.

Apply this diff:

         return {
           content: [
             {
               type: "text" as const,
               text: errorText,
             },
           ],
+          isError: true,
         };

---

148-165: Avoid 'undefined' in responses: normalize description field.

Some responses interpolate page.data.description without a fallback; template strings will print “undefined”.

Apply this diff:

-              text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nContent:\n${content}`,
+              text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ""}\nContent:\n${content}`,

-            text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nContent:\n${content}`,
+            text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ""}\nContent:\n${content}`,

-                text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nContent:\n${content}`,
+                text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ""}\nContent:\n${content}`,

-                text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nContent:\n${content}`,
+                text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ""}\nContent:\n${content}`,

-          text: `Title: ${page.data.title}\nDescription: ${page.data.description}\nError: Could not read file at any of the attempted paths: ${filePath}, ${altPaths.join(", ")}`,
+          text: `Title: ${page.data.title}\nDescription: ${page.data.description ?? ""}\nError: Could not read file at any of the attempted paths: ${filePath}, ${altPaths.join(", ")}`,

Also applies to: 183-201, 209-217

---

112-113: Use strict inequality.

Minor style/consistency improvement.

Apply this diff:

-    return !(v.slugs[0] == "API-Reference");
+    return v.slugs[0] !== "API-Reference";

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.