Setup and Installation
The MCP server is fully remote and does not require any local installation.
Connecting to the remote server
In any application supporting MCP (e.g., Cursor or Claude), add the following configuration to your mcp.json:
{
"mcpServers": {
"coralogix-server": {
"command": "npx",
"args": [
"mcp-remote",
"<your-coralogix-mcp-endpoint>",
"--header",
"Authorization:${CORALOGIX_API_KEY}"
],
"env": {
"CORALOGIX_API_KEY": "<your-api-key>"
}
}
}
}
Replace
<your-coralogix-mcp-endpoint>with the MCP endpoint associated with your Coralogix domain, for example https://api./mgmt/api/v1/mcp. Ensure that you have selected the correct domain in the domain selector.Replace
<your-api-key>with a personal Coralogix API key. The MCP server inherits the permissions associated with the user’s personal API key. Find out more in Permissions.
Direct integration with Cursor
Cursor supports direct MCP server integration (recommended), as follows:
{
"New-Coralogix-MCP-Server": {
"url": "<your-coralogix-mcp-endpoint>",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
Replace
<your-coralogix-mcp-endpoint>with the MCP endpoint associated with your Coralogix domain, for example https://api./mgmt/api/v1/mcp. Ensure that you have selected the correct domain in the domain selector.Replace
<your-api-key>with a personal Coralogix API key. The MCP server inherits the permissions associated with the user’s personal API key. Find out more in Permissions.
Using a proxy for outbound connections
If your network requires a proxy for outbound connections, run MCP with: mcp run <component> --enable-proxy. This ensures the MCP server uses your system’s proxy settings and avoids connectivity issues.
Starting a session
Start a conversation by entering a prompt such as:
The assistant should locate relevant log entries and identify problematic functions.
Requesting a fix for agent-based IDEs
After identifying the issue, for agent-based IDEs such as Cursor, instruct the assistant to fix it by saying:
You can also ask: