Your Sumo Logic MCP server is now working perfectly! Here's how to configure it in Cursor.
- 25 tools successfully registered
- All tool categories working: Search, Dashboard, Metrics, Collector, Health
- Reference compatibility tools included (execute_query, list_metrics, etc.)
- VMware monitoring tools available
- Graceful startup without requiring valid credentials upfront
First, create your .env file with your actual Sumo Logic credentials:
# Copy the example file
cp .env.example .env
# Edit with your actual credentials
nano .envAdd your real credentials:
SUMOLOGIC_ACCESS_ID=your_actual_access_id_here
SUMOLOGIC_ACCESS_KEY=your_actual_access_key_here
SUMOLOGIC_ENDPOINT=https://api.sumologic.comAdd this configuration to Cursor. The exact location depends on your Cursor version:
- Open Cursor
- Go to Settings (Cmd/Ctrl + ,)
- Search for "MCP" or "Model Context Protocol"
- Add a new server:
{
"name": "sumologic",
"command": "/Users/vinitkumar/mcpservers/sumologic-mcp-env/bin/sumologic-mcp-server",
"env": {
"SUMOLOGIC_ACCESS_ID": "your_access_id_here",
"SUMOLOGIC_ACCESS_KEY": "your_access_key_here",
"SUMOLOGIC_ENDPOINT": "https://api.sumologic.com",
"SUMOLOGIC_LOG_LEVEL": "INFO"
}
}Create or edit the MCP configuration file:
macOS: ~/Library/Application Support/Cursor/mcp_servers.json
Linux: ~/.config/cursor/mcp_servers.json
Windows: %APPDATA%\Cursor\mcp_servers.json
{
"mcpServers": {
"sumologic": {
"command": "/Users/vinitkumar/mcpservers/sumologic-mcp-env/bin/sumologic-mcp-server",
"env": {
"SUMOLOGIC_ACCESS_ID": "your_access_id_here",
"SUMOLOGIC_ACCESS_KEY": "your_access_key_here",
"SUMOLOGIC_ENDPOINT": "https://api.sumologic.com",
"SUMOLOGIC_LOG_LEVEL": "INFO"
}
}
}
}If the direct command doesn't work:
{
"mcpServers": {
"sumologic": {
"command": "/Users/vinitkumar/mcpservers/sumologic-mcp-env/bin/python",
"args": ["-m", "sumologic_mcp"],
"cwd": "/Users/vinitkumar/mcpservers",
"env": {
"SUMOLOGIC_ACCESS_ID": "your_access_id_here",
"SUMOLOGIC_ACCESS_KEY": "your_access_key_here",
"SUMOLOGIC_ENDPOINT": "https://api.sumologic.com"
}
}
}
}- Restart Cursor after making configuration changes
- Open a new chat or conversation
- Test the connection:
Can you use the health_check tool to verify the Sumo Logic MCP server is working?
search_logs- Execute log search queriesexecute_query- Reference-compatible query executionget_search_job_status- Check search job statusget_search_results- Retrieve paginated resultsvalidate_query_syntax- Validate queries without executionlist_source_categories- Discover available source categoriesget_sample_data- Get sample data from source categoriesexplore_vmware_metrics- VMware metrics exploration
list_dashboards- List all dashboardsget_dashboard- Get dashboard detailscreate_dashboard- Create new dashboardsupdate_dashboard- Update existing dashboardsdelete_dashboard- Delete dashboards
query_metrics- Execute metrics querieslist_metric_sources- List available metricslist_metrics- Reference-compatible metrics listingget_metric_metadata- Get detailed metric information
list_collectors- List all collectorsget_collector- Get collector detailscreate_collector- Create new collectorsupdate_collector- Update collector configurationdelete_collector- Delete collectorslist_sources- List sources in collectorscreate_source- Create new sources
health_check- Get server health status
Once configured, try these prompts:
Search for application errors in the last 2 hours using search_logs:
- Query: _sourceCategory="app/logs" AND level=ERROR
- Time: -2h to now
- Limit: 100
Use execute_query (reference compatibility) to search for:
- Query: error OR exception
- Time range: last 1 hour
- Limit: 50
Use explore_vmware_metrics to analyze VMware performance metrics from the "otel/vmware" source category
List all dashboards and show me details of any dashboard related to "performance"
Run a health_check to verify the Sumo Logic MCP server status and include metrics
-
Check the command path:
# Verify the command exists ls -la /Users/vinitkumar/mcpservers/sumologic-mcp-env/bin/sumologic-mcp-server # Test it manually source sumologic-mcp-env/bin/activate sumologic-mcp-server --help
-
Check your credentials:
# Validate configuration source sumologic-mcp-env/bin/activate sumologic-mcp-server --validate-config
-
Enable debug logging:
{ "env": { "SUMOLOGIC_LOG_LEVEL": "DEBUG", "SUMOLOGIC_LOG_FORMAT": "text" } } -
Try the Python module approach (Option C above)
-
Check Cursor's MCP logs (if available in Cursor's developer tools)
- "Command not found": Use the full path to the executable
- "Authentication failed": Check your credentials with
--validate-config - "Tools not loading": Restart Cursor and wait a moment for initialization
- "Connection timeout": Check your network and firewall settings
You'll know it's working when:
- ✅ Cursor shows "Sumo Logic" tools in the available tools list
- ✅ You can successfully run
health_check - ✅ Search queries return results
- ✅ No authentication errors in logs
# Test server manually
source sumologic-mcp-env/bin/activate
sumologic-mcp-server --validate-config
# Test with debug output
SUMOLOGIC_LOG_LEVEL=DEBUG sumologic-mcp-server --validate-configYour Sumo Logic MCP server is ready to use! 🚀