getComponent MCP Tool Fails with “t.parse is not a function” Error in Cursor IDE

[tashfiqul-islam]

Describe the Bug

The getComponent MCP tool for kibo-ui consistently fails when invoked from Cursor IDE, returning the following error message:

{"error":"MCP error -32603: t.parse is not a function"}

While the getComponents tool works correctly and returns the full list of components, the getComponent <component-name> call fails immediately, suggesting a parsing or serialization issue during request processing.

---

next-forge version

Using next-forge version: X.Y.Z (please specify your version)

---

To Reproduce

1. Open Cursor IDE.

2. Run the MCP command:

   getComponents

   ✅ Returns successfully with full component list.

3. Run:

   getComponent button

   ❌ Fails with error:

   {"error":"MCP error -32603: t.parse is not a function"}

4. Repeat with other component names — same result.

---

Expected Behavior

The getComponent <component-name> command should return the metadata and configuration details for the specified component, consistent with the MCP contract, instead of failing with a parse error.

---

Actual Behavior

• The getComponents command functions as expected.
• The getComponent command throws a JSON parsing error before returning component details.
• The issue occurs consistently across multiple valid component names.

---

Screenshots / Logs

---

MCP Configuration

"kibo-ui": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://www.kibo-ui.com/api/mcp/mcp"
  ]
}

---

Desktop Environment

Attribute	Details
OS	Windows 11 Version 25H2 (OS Build 26200.6899)
IDE	Cursor 1.7.52
Commit	9675251a06b1314d50ff34b0cbe5109b78f848c0
Chromium	132.0.6834.210
Electron	34.5.8
User Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Cursor/1.7.52 Chrome/132.0.6834.210 Electron/34.5.8 Safari/537.36

---

Additional Context

• The issue appears limited to the getComponent tool only.
• The MCP server responds almost instantly, suggesting the failure happens during local parsing or JSON serialization.
• Possible root cause: the MCP client attempts to run t.parse() on a non-JSON payload or malformed object.

[tashfiqul-islam]

@haydenbleasel -- hey did you get a chance to see this by any chance?