IntegrationsMCP Server
Claude Code Configuration
Connect ConnectSafely MCP server to Claude Code
Connect ConnectSafely to Claude 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
- Claude Code extension installed in VS Code
Connection URL
Your MCP server URL format:
https://mcp.connectsafely.ai/?apiKey=YOUR_API_KEYSetup Instructions
Step 1: Open Claude Code Settings
- Open VS Code with Claude Code extension
- Click on Claude Code icon in the sidebar
- Open settings or configuration
Step 2: Add MCP Server
- Navigate to MCP Servers or Integrations section
- Click Add Server or Add Integration
- Enter server details:
- Name:
ConnectSafely - URL:
https://mcp.connectsafely.ai/?apiKey=YOUR_API_KEY
- Name:
- Save the configuration
Step 3: Verify Connection
The ConnectSafely MCP server should now be available in Claude Code and ready to use in your conversations.
Using ConnectSafely with Claude Code
Once connected, you can use Claude Code with ConnectSafely context:
- Get intelligent code assistance for LinkedIn integrations
- Analyze engagement data while coding
- Generate response templates and automation scripts
- Work with LinkedIn data directly in your IDE
- Build LinkedIn automation tools faster
Example Use Cases
Show me how to analyze LinkedIn comment sentiment in TypeScriptCreate a function to filter spam comments from LinkedIn postsHelp me build a LinkedIn engagement dashboardTroubleshooting
Connection Not Appearing
- Verify you entered the correct MCP server URL
- Check that your API key is active and valid
- Restart VS Code after adding the connection
Authentication Failed
- Ensure you have an active Pro or Agency subscription
- Regenerate your API key from ConnectSafely Settings
- Update the MCP server URL with the new API key
Security Best Practices
⚠️ Security Warning
Never commit your MCP configuration 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 configuration files with secrets to
.gitignore - Regenerate keys if accidentally exposed
- Monitor API usage regularly
