MCP Parameter Mismatch: 'informationToGet' vs 'query' in Supermemory Search Tool - Works on VS Code but fails on Cursor

[sakuchoman]

Environment

• OS: macOS 25.1.0
• Cursor Version: 2.0.69
• Node.js: v22.17.0
• npm: 10.9.2
• MCP Endpoint: https://api.supermemory.ai/mcp
• MCP Server Name: supermemory (https://api.supermemory.ai/mcp)

Problem Description

The Supermemory MCP search tool does not work in Cursor IDE, but works perfectly on VS Code with Codex CLI using the same server endpoint.

Error Message:

Error calling tool: Required parameter 'query' is missing for tool search

MCP Configuration

~/.cursor/mcp.json:

{
  "mcpServers": {
    "supermemory-test": {
      "command": "npx -y mcp-remote https://api.supermemory.ai/mcp",
      "env": {},
      "args": []
    }
  }
}

Root Cause Analysis

Tool Schema Definition

• Parameter name in schema: informationToGet
• Server implementation expects: query parameter
• Symptom: Parameter name mismatch between tool definition and server

Test Results Comparison

Environment	MCP Connection	Authentication	Search Execution	Parameter Definition	Result
VS Code + Codex CLI	✅ SUCCESS	✅ SUCCESS	✅ SUCCESS	informationToGet	Works
Cursor (Normal Mode)	✅ SUCCESS	✅ SUCCESS	❌ FAILED	Expected query	Error
Cursor (Safe Mode)	✅ SUCCESS	✅ SUCCESS	❌ FAILED	Expected query	Error

Troubleshooting Steps Taken

1. MCP Configuration Verification ✅

   • Syntax validation
   • Server endpoint verification
   • Tool definition confirmation

2. Multi-Level Cache Clearing ✅

   • MCPキャッシュ削除: rm -rf ~/.cursor/projects/*/mcp-cache.json
   • NPM cache: npm cache clean --force
   • NPX cache: rm -rf ~/.npm/_npx
   • Cursor cache: rm -rf ~/.cursor/Code\ Cache/

3. Version Verification ✅

   • Node.js: v22.17.0 (Latest - no update needed)
   • npm: 10.9.2 (Latest)
   • Cursor: 2.0.69 (Near latest - no update needed)

4. IDE Restart ✅

   • Multiple restarts in normal mode
   • Multiple restarts in safe mode

5. Server Name Change ✅

   • Changed from supermemory-mcp to supermemory-test
   • Re-registration and restart
   • Result: Same error persists

6. Safe Mode Verification ✅

   • Tested with --disable-extensions flag
   • Extensions are NOT the cause
   • Error still occurs = Core Cursor implementation issue

7. Cross-Platform Comparison Test ✅

   • Same endpoint: https://api.supermemory.ai/mcp
   • Same credentials: Same authentication tokens
   • VS Code: Works with informationToGet parameter
   • Cursor: Fails, expects query parameter

8. Developer Consultation ✅

   • VS Code Codex CLI analyzed the issue
   • Conclusion: "Cursor client-side implementation likely forcing 'query' parameter"

Key Findings

1. Server is working correctly - Verified with VS Code + Codex CLI
2. Configuration is correct - MCP settings verified and tested
3. Not an environment issue - Node.js and dependencies are current
4. Not an extension issue - Reproduced in Safe Mode
5. Cursor-specific problem - Identical setup works on VS Code

Expert Assessment

After testing with VS Code Codex CLI:

"Since the same endpoint and credentials work on VS Code but fail on Cursor with the same parameter name 'informationToGet' in the tool schema, the issue appears to be in Cursor's MCP implementation converting or expecting 'query' instead of 'informationToGet'."

Hypothesis

Cursor's MCP client implementation has a parameter mapping issue where it:

1. Reads the tool schema correctly (tool name: search, parameter: informationToGet)
2. But forcefully converts or remaps the parameter to query during tool invocation
3. The server receives a request with query instead of informationToGet
4. The server returns error: "Required parameter 'query' is missing" (because it expects informationToGet)

Expected Behavior

Cursor should pass MCP tool parameters exactly as defined in the tool schema, using the parameter name informationToGet as specified by the Supermemory MCP server.

Actual Behavior

Cursor is sending requests with a query parameter instead of informationToGet, causing the Supermemory search tool to fail.

Logs & Evidence

• DevTools Network inspection attempted but MCP communication appears to occur at a level not visible in standard browser DevTools
• Comparison data with VS Code Codex CLI shows identical configuration behaves differently

Steps to Reproduce

1. Add Supermemory MCP server to Cursor:

   {
     "mcpServers": {
       "supermemory": {
         "command": "npx -y mcp-remote https://api.supermemory.ai/mcp",
         "env": {},
         "args": []
       }
     }
   }
   

2. Restart Cursor

3. Attempt to use search tool with informationToGet parameter

4. Error occurs: "Required parameter 'query' is missing for tool search"

Questions for Cursor Team

1. Is there a known issue with MCP parameter mapping in Cursor 2.0.69?
2. Are parameter names subject to any transformation or remapping in Cursor's MCP implementation?
3. Could this be related to the MCPoison/CurXecute vulnerabilities (CVE-2025-54135/54136) fixed in previous versions?
4. Is there a workaround or known fix for this issue?

Affected Users

This issue may affect any MCP server that uses non-standard parameter names (anything other than query for search operations).