Cursor Configuration

Connect ConnectSafely to Cursor IDE for AI-powered LinkedIn engagement management directly in your development environment.

Prerequisites

• Pro or Agency plan subscription
• Your MCP server URL from MCP Setup page
• Cursor IDE installed

Connection URL

Your MCP server URL format:

https://mcp.connectsafely.ai/?apiKey=YOUR_API_KEY

Setup Instructions

Step 1: Open Cursor Settings

1. Open Cursor IDE
2. Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
3. Type "Preferences: Open User Settings (JSON)"
4. Press Enter

Step 2: Add ConnectSafely MCP Server

Add the following configuration to your settings file:

{
  "mcpServers": {
    "connectsafely": {
      "url": "https://mcp.connectsafely.ai/?apiKey=YOUR_API_KEY"
    }
  }
}

Replace YOUR_API_KEY with your actual API key from the MCP Setup page.

Step 3: Save and Restart

1. Save the settings file
2. Restart Cursor IDE
3. The MCP server will be active on restart

Using ConnectSafely with Cursor

Once connected, you can use Cursor's AI features with ConnectSafely context:

• Intelligent code assistance for LinkedIn integrations
• Comment analysis while coding
• Generate response templates
• Work with LinkedIn data directly in your IDE
• Build LinkedIn automation tools faster

Example Use Cases

Show me the sentiment analysis of comments on my recent post

Create a function to generate personalized responses to LinkedIn comments

Help me write a script to filter and categorize LinkedIn comments

Troubleshooting

MCP Server Not Detected

• Verify the JSON syntax is correct
• Check that you saved the settings file
• Restart Cursor IDE completely
• Ensure your API key is valid

Authentication Failed

• Confirm you have an active Pro or Agency subscription
• Regenerate your API key from ConnectSafely Settings
• Update the configuration with the new API key
• Restart Cursor after updating

Security Best Practices

⚠️ Security Warning

Never commit your MCP configuration file with API keys to version control. Use environment variables for sensitive data.

Best Practices:

• Never commit API keys to git
• Use environment variables for sensitive data
• Add settings files with secrets to .gitignore
• Regenerate keys if accidentally exposed
• Monitor API usage regularly

Learn More

• Claude Code Documentation
• Model Context Protocol Specification
• ConnectSafely API Documentation
• MCP Setup Guide