Skip to content

NOVA-COMMAND-ACTIVATION-FIX.md

Latest commit

 

History

History
183 lines (134 loc) · 5.82 KB

NOVA-COMMAND-ACTIVATION-FIX.md

File metadata and controls

183 lines (134 loc) · 5.82 KB

Nova Command Activation Fix

Problem Description

When users type /nova in Cursor, the Nova MCP is not being activated. Instead, Cursor responds with:

"The /nova command isn't activating the Nova MCP because it's not a standard command that automatically triggers the MCP. The Nova MCP tools are available in this environment, but you need to explicitly call them."

Root Cause Analysis

The issue is NOT with Nova's code or MCP server implementation. The problem is with Cursor's configuration:

  1. Nova MCP Server is Working: The MCP server is properly implemented and functional
  2. /nova is Not a Built-in Command: Cursor doesn't automatically recognize /nova as a command
  3. MCP Tools are Available: The mcp_nova_nova_ functions are working correctly
  4. Configuration is Missing: Cursor needs to be told to use Nova as an MCP server

Why This Happens

MCP Architecture

  • MCP (Model Context Protocol) is a protocol for AI assistants to communicate with external tools
  • Nova is an MCP server that provides planning and execution tools
  • Cursor needs to be configured to connect to Nova as an MCP server
  • /nova is not a built-in Cursor command - it's a custom command that needs configuration

Current State

  • ✅ Nova MCP server is running and functional
  • ✅ All MCP tools are working (mcp_nova_nova_*)
  • ❌ /nova command is not recognized by Cursor
  • ❌ Cursor is not configured to use Nova as an MCP server

Solutions

Solution 1: Configure Cursor to Use Nova MCP (Recommended)

Create a Cursor configuration file to enable Nova MCP:

Option A: Global Configuration

Create ~/.cursor/settings.json (or equivalent for your OS):

{
  "mcpServers": {
    "nova": {
      "command": "npx",
      "args": ["-y", "@meta-boltz/nova"],
      "env": {
        "NOVA_TASKS_DIR": ".cursor/tasks",
        "NOVA_AUTO_OPEN": "true",
        "NOVA_NOTIFICATIONS": "true"
      }
    }
  }
}

Option B: Project-Specific Configuration

Create .cursor/settings.json in your project root:

{
  "mcpServers": {
    "nova": {
      "command": "npx",
      "args": ["-y", "@meta-boltz/nova"],
      "env": {
        "NOVA_TASKS_DIR": ".cursor/tasks",
        "NOVA_AUTO_OPEN": "true",
        "NOVA_NOTIFICATIONS": "true"
      }
    }
  }
}

Option C: Use the Provided Config File

Copy the example configuration:

cp config/cursor-config-example.json .cursor/settings.json

Solution 2: Use Explicit MCP Function Calls (Current Workaround)

Since the MCP tools are available, you can use them directly:

// Instead of /nova create react todo
mcp_nova_nova_create_task("create react todo", "react-todo")

// Instead of /nova continue planning
mcp_nova_nova_continue_planning("react-todo")

// Instead of /nova continue tasks
mcp_nova_nova_continue_tasks("react-todo")

// Instead of /nova continue execution
mcp_nova_nova_continue_execution("react-todo")

How to Fix the /nova Command

Step 1: Install Nova Globally (if not already done)

npm install -g @meta-boltz/nova

Step 2: Create Cursor Configuration

Create the appropriate configuration file as shown in Solution 1.

Step 3: Restart Cursor

Restart Cursor to load the new MCP configuration.

Step 4: Test the Command

Type /nova followed by your command:

  • /nova create react todo
  • /nova continue planning
  • /nova generate ui test script

Verification Steps

Check if Nova MCP is Loaded

  1. Open Cursor
  2. Check the MCP status (usually in the bottom status bar)
  3. Look for "Nova MCP" or similar indicators

Test Basic Commands

  1. Type /nova - should show Nova help
  2. Type /nova create test project - should create a new task
  3. Check if .cursor/tasks/test-project/ directory is created

Check MCP Tools

  1. The mcp_nova_nova_* functions should be available
  2. Nova should appear in the MCP tools list

Troubleshooting

If /nova Still Doesn't Work

  1. Check Cursor Version: Ensure you're using a recent version of Cursor
  2. Verify MCP Support: Ensure your Cursor version supports MCP servers
  3. Check Configuration: Verify the configuration file is in the correct location
  4. Check Permissions: Ensure Nova has permission to run
  5. Check Logs: Look for MCP-related errors in Cursor's developer console

Common Issues

  1. "Command not found": Nova is not installed globally
  2. "Permission denied": Check file permissions and npm global installation
  3. "MCP server failed to start": Check Nova's dependencies and Node.js version
  4. "Configuration not loaded": Ensure the configuration file is in the correct location

Alternative Approaches

Option 1: Create a Custom Cursor Extension

Develop a Cursor extension that provides the /nova command interface.

Option 2: Use Keyboard Shortcuts

Configure keyboard shortcuts to trigger Nova MCP functions.

Option 3: Use Command Palette

Access Nova functions through Cursor's command palette.

Current Status

  • ✅ Nova MCP Server: Fully functional
  • ✅ All MCP Tools: Working correctly
  • ✅ File Management: Working correctly
  • ✅ Task Management: Working correctly
  • ❌ /nova Command: Requires Cursor configuration
  • ✅ MCP Function Calls: Working as fallback

Next Steps

  1. Immediate: Use mcp_nova_nova_* functions as workaround
  2. Short-term: Configure Cursor to use Nova MCP server
  3. Long-term: Consider developing a Cursor extension for better integration

Conclusion

The /nova command issue is a configuration problem, not a code problem. Nova is working perfectly as an MCP server. The solution is to properly configure Cursor to recognize and use Nova as an MCP server.

Once configured, users will be able to use the intuitive /nova command syntax instead of the more verbose mcp_nova_nova_* function calls.