Skip to main content

​
Overview

Configure Deepcon MCP in Cursor through the MCP configuration file. You can set it up at the project level or globally for all projects.
Requirements: Cursor version 0.45.6 or higher

​
Installation Methods

  • UI Configuration (v0.48.6+)
  • UI Configuration (v0.45.6)
  • Manual File Configuration

​
Using Cursor Settings UI

1

Open Cursor Settings

Click the gear icon or use Cmd/Ctrl + ,
2

Navigate to MCP Servers

Go to Features → MCP Servers
3

Add New Server

Click ”+ Add new global MCP server”
4

Enter Configuration

Paste the following configuration:
{
  "mcpServers": {
    "deepcon": {
      "command": "npx",
      "args": ["-y", "deepcon-mcp"],
      "env": {
        "DEEPCON_API_KEY": "your-api-key-here"
      }
    }
  }
}
5

Save and Restart

Save the configuration and restart Cursor
Replace your-api-key-here with your actual API key from the dashboard

​
Verify Connection

After configuration, verify the setup:
1

Restart Cursor

Completely quit and restart Cursor IDE
2

Open Composer

Open the Cursor Composer using Cmd/Ctrl + K
3

Select Agent Mode

Click “Agent” next to the submit button
4

Check MCP Tools

The AI should now have access to Deepcon tools:
  • search_documentation
5

Test Search

Try asking: “Use Deepcon to search the React documentation for hooks”

​
Team Setup

For teams, commit the project-level configuration:
Terminal
git add .cursor/mcp.json
git commit -m "Add Deepcon MCP configuration"
git push
Security Note: If you commit the config file, use environment variables for the API key instead of hardcoding it.

​
Using Environment Variables

For team setups, reference an environment variable:
.cursor/mcp.json
{
  "mcpServers": {
    "deepcon": {
      "command": "npx",
      "args": ["-y", "deepcon-mcp"],
      "env": {
        "DEEPCON_API_KEY": "${DEEPCON_API_KEY}"
      }
    }
  }
}
Then each team member sets their own API key:
.env or shell profile
export DEEPCON_API_KEY="your-api-key-here"

​
Troubleshooting

Solution: Ensure Node.js is installed and accessibleCheck Node.js version (need 19+):
node --version
Verify npx is available:
npx --version
Solution: Verify your API key is correct
  1. Check the API key in mcp.json
  2. Ensure no extra spaces or quotes
  3. Get a fresh key from dashboard
  4. Restart Cursor after updating
Solution: Check file location and permissionsVerify the file exists:
# For project-level
ls -la .cursor/mcp.json

# For global
ls -la ~/.cursor/mcp.json
Ensure proper read permissions:
chmod 644 .cursor/mcp.json
Solution: Validate your JSONUse a JSON validator to check for errors:
# On macOS/Linux with jq
cat .cursor/mcp.json | jq .
Or use jsonlint.com

​
Next Steps

Search Documentation

Learn how to use the search tool

Best Practices

Tips for effective searches

Examples

Real-world usage examples