MCP (Model Context Protocol) server for return0 - a tool for debugging production applications in real-time.
return0 enables developers to debug production Node.js applications in real-time. It allows you to monitor and troubleshoot your applications by connecting to live variables, observing execution flow, and understanding runtime behavior directly within the Cursor IDE. This is especially powerful for debugging production applications built with Next.js and deployed on platforms like Vercel, where traditional debugging methods can be challenging.
- Website: getreturn0.com
- Live Demo: getreturn0.com/livedemo
- Documentation: getreturn0.com/docs
To use this MCP server with Cursor IDE, you need to configure it in your Cursor settings. First, you'll need to get your return0 API key.
To get your return0 API key, visit the return0 documentation. The documentation will guide you through the process of obtaining your API key.
Once you have your API key, you can configure the MCP server in one of two ways:
Click the button below to automatically install and configure the return0 MCP server in Cursor:
This will automatically configure the MCP server. Note: You'll need to add your return0 API key to the configuration after installation. See the Getting Your API Key section above for instructions on obtaining your API key, and the manual configuration section below for details on how to add it.
If you prefer to configure manually, follow these steps in Cursor IDE:
- Open Cursor IDE
- Go to Settings (or Preferences on macOS):
- Click the gear icon (⚙️) in the bottom left corner, or
- Use the keyboard shortcut:
Ctrl+,(Windows/Linux) orCmd+,(macOS)
- In the settings search bar, type "MCP" or "Model Context Protocol"
- Click on MCP Servers or navigate to the MCP configuration section
- Click Add Server or the + button to add a new MCP server
- Enter the following configuration:
- Name:
return0 - Command:
npx - Args:
-y,@return-0/mcp-server - Environment Variables: Add
RETURN0_API_KEYwith your API key as the value
- Name:
- Click Save or Apply to save the configuration
The configuration should look like this in your mcp.json file:
{
"mcpServers": {
"return0": {
"command": "npx",
"args": ["-y", "@return-0/mcp-server"],
"env": {
"RETURN0_API_KEY": "your-api-key-here"
}
}
}
}Note: Replace "your-api-key-here" with your actual return0 API key. If you don't have an API key yet, see the Getting Your API Key section above for instructions, or you can use "demo" for testing purposes. The MCP server will be automatically installed via npx when Cursor starts.
This MCP server provides a variable_extractor tool that can be used by MCP-compatible clients.
Extracts the runtime value, type, and timestamp of variables from production code.
Input Schema:
{
files: Array<{
fileName: string; // Full absolute path to the file
variables: Array<{
name: string; // Variable name to extract
lineNumber: number; // Line number where variable is defined
}>
}>
}Example:
{
"files": [
{
"fileName": "C:\\Users\\username\\project\\src\\app\\api\\route.ts",
"variables": [
{
"name": "userData",
"lineNumber": 42
}
]
}
]
}- The MCP server receives requests to extract runtime variable values from production code
- It reads the source files from the local filesystem
- Uses TypeScript AST analysis to correct line numbers for accurate variable location
- Connects to the running production application to retrieve live variable values
- Returns the corrected variable extraction data with real-time runtime values, types, and timestamps
See LICENSE file for details.
return0
