docs-v2/pages/connect/mcp/openai.mdx (5)

5-5: Fix typo in "capabilties".

The word “capabilties” is misspelled—should be capabilities.

---

37-37: Introduce "Discover available MCP servers" section.

Great to show how to find which MCP servers (apps) are available. Consider explaining what process.env.PUBLIC_APPS resolves to in the docs build context.

Also applies to: 39-39

---

41-45: Provide code examples for listing all apps.

The snippet is concise and informative. You may want to add a note about paginating through apps.next if more than one page of results is expected.

Also applies to: 47-49

---

52-53: Add "Search for a specific app" tab.

These examples clearly demonstrate how to filter apps by name. Consider mentioning that the query is case-insensitive.

Also applies to: 54-57

---

124-127: Optional: Polish the cURL example.

The end-to-end flow is clear, but you can streamline quoting for bash substitution and ensure consistency:

-  "client_secret": "'$PIPEDREAM_CLIENT_SECRET'"
+  "client_secret": "$PIPEDREAM_CLIENT_SECRET"

Also, consider adding -s to subsequent curl commands for quieter output and noting that jq is required.

Also applies to: 130-133, 135-138, 140-144, 156-161

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

docs-v2/pages/connect/mcp/openai.mdx (3)

39-39: Duplicate: Flagged PUBLIC_APPS usage
(See earlier comment on line 5 about process.env.PUBLIC_APPS consistency.)

---

75-83: ⚠️ Potential issue

Incorrect env var references in createBackendClient
You’re passing raw identifiers instead of process.env.*, which will cause runtime errors. For example:

 const pd = createBackendClient({
-  environment: PIPEDREAM_ENVIRONMENT,
+  environment: process.env.PIPEDREAM_ENVIRONMENT,
   credentials: {
-    clientId: PIPEDREAM_CLIENT_ID,
-    clientSecret: PIPEDREAM_CLIENT_SECRET,
+    clientId: process.env.PIPEDREAM_CLIENT_ID,
+    clientSecret: process.env.PIPEDREAM_CLIENT_SECRET,
   },
-  projectId: PIPEDREAM_PROJECT_ID
+  projectId: process.env.PIPEDREAM_PROJECT_ID,
 });

---

104-111: ⚠️ Potential issue

Fix env var usage in tool headers
As with the Pipedream client, these need process.env.*. For example:

  headers: {
-   Authorization: `Bearer ${accessToken}`,
-   "x-pd-project-id": PIPEDREAM_PROJECT_ID,
-   "x-pd-environment": PIPEDREAM_ENVIRONMENT
+   Authorization: `Bearer ${accessToken}`,
+   "x-pd-project-id": process.env.PIPEDREAM_PROJECT_ID,
+   "x-pd-environment": process.env.PIPEDREAM_ENVIRONMENT,
  },

Also verify the MCP domain (mcp.pipedream.net) is correct and accessible.

docs-v2/pages/connect/mcp/openai.mdx (5)

20-20: Verify project link anchor
Ensure /projects/#creating-projects matches the actual heading slug in that page (e.g., it might be #creating-a-project). Confirm the fragment to avoid a broken link.

---

44-45: Clarify pd context in snippet
The snippet uses pd.getApps() without showing how pd was initialized. Add a note such as:

// `pd` is the Pipedream client from createBackendClient()—see “Node.js” tab for init

---

85-89: Add error handling for app search
If apps.data is empty, apps.data[0] will throw. Consider guarding this:

if (!apps.data?.length) {
  throw new Error("No MCP apps found for the given query");
}
const appSlug = apps.data[0].name_slug;

---

90-91: Optional: Handle access token errors
await pd.rawAccessToken() may fail. Wrapping in try/catch can surface errors more clearly:

try {
  accessToken = await pd.rawAccessToken();
} catch (err) {
  console.error("Failed to fetch MCP access token:", err);
  throw err;
}

---

93-94: Use a placeholder or env var for externalUserId
Hardcoding 'abc-123' may confuse readers. Consider:

const externalUserId = process.env.EXTERNAL_USER_ID || "abc-123";

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting