IntegrationsMCP Server
VS Code Configuration
Connect ConnectSafely MCP server to VS Code
Connect ConnectSafely to VS Code 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
- VS Code with MCP-compatible extension installed
Connection URL
Your MCP server URL format:
https://mcp.connectsafely.ai/?apiKey=YOUR_API_KEYSetup Instructions
Step 1: Install MCP Extension
- Open VS Code
- Go to Extensions (Cmd+Shift+X or Ctrl+Shift+X)
- Search for an MCP-compatible AI extension
- Install the extension
Step 2: Configure MCP Server
- Open VS Code settings (Cmd+, or Ctrl+,)
- Search for "MCP" or your extension's settings
- Add ConnectSafely MCP server:
{ "mcp.servers": { "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
- Save the settings file
- Restart VS Code
- The MCP server will be active on restart
Using ConnectSafely with VS Code
Once connected, you can use VS Code'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 postCreate a function to generate personalized responses to LinkedIn commentsHelp me write a script to filter and categorize LinkedIn commentsTroubleshooting
MCP Server Not Detected
- Verify the JSON syntax is correct
- Check that you saved the settings file
- Restart VS Code 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 VS Code 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
