Logpresso Store

Install Guide

This guide assumes the common on-premises setup where HTTPS is terminated with a private certificate (self-signed or an internal CA). If your deployment uses a publicly trusted certificate, see the simpler registration at the end.

Step 1. Install the App

Install the MCP Server app from the Logpresso Store. An MCP Server item is added to the left menu. In a redundant deployment, installing on one node deploys it across the cluster - there is no need to install it node by node.

The MCP endpoint is published on the Logpresso control node's HTTPS listener, the same one that serves the web console.

https://CONTROL_NODE_HOST/mcp

Step 2. Check Your API Key

MCP clients authenticate with a user API key. If your account has no key issued, ask an administrator to issue one.

Note

If your account restricts trusted hosts, the address of the machine running the MCP client must be on that list. When a valid key still returns 401, check the trusted-host restriction before the key itself.

Step 3. Copy the Configuration from the Setup Tab

Open the Setup tab of the MCP Server screen. It builds a configuration with your own API key already filled in, so there is nothing to assemble by hand.

Check the Server URL value. It is derived from the address your browser reached, so behind a load balancer or reverse proxy, replace it with the external address the client can reach.
Press Copy on the API key row. The key is masked on screen, but the clipboard receives the real value.
Press Copy on the code block for your client. It is already filled in and can be pasted directly into steps 4 and 5.

Step 4. Register with Claude Code

Node.js must be installed. Replace CONTROL_NODE_HOST and API_KEY with the values from step 3.

claude mcp add logpresso -e NODE_TLS_REJECT_UNAUTHORIZED=0 -- npx -y mcp-remote https://CONTROL_NODE_HOST/mcp --header "Authorization: Bearer API_KEY"

-e NODE_TLS_REJECT_UNAUTHORIZED=0 is what allows the private certificate. Without it the connection fails certificate validation.
The default scope is the directory the command was run in. Add -s user to use it in every project.
Use claude mcp list to see registered servers and claude mcp remove logpresso to remove one.

Step 5. Register with Claude Desktop

Open the configuration file in an editor and add the following. If other MCP servers are already registered, add only the logpresso entry inside mcpServers.

OS	Configuration file path
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`

{
  "mcpServers": {
    "logpresso": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://CONTROL_NODE_HOST/mcp",
        "--header", "Authorization: Bearer API_KEY"
      ],
      "env": {
        "NODE_TLS_REJECT_UNAUTHORIZED": "0"
      }
    }
  }
}

NODE_TLS_REJECT_UNAUTHORIZED in env serves the same purpose as the -e option in step 4.

Step 6. Verify the Connection

An MCP server is connected when the client session starts. Always restart the client after changing the configuration.

On success, initialize and tools/list requests appear in the Logs tab of the MCP Server screen.

Symptom	What to check
No requests in the log	Whether the client was restarted, and whether the server URL is reachable from it
Requests recorded with an `Error` status	The rejection reason in the log detail. For auth failures, the API key and trusted hosts
A certificate error in the client	Whether `NODE_TLS_REJECT_UNAUTHORIZED` is missing

With a Publicly Trusted Certificate

Where certificate validation passes normally, Claude Code can register the endpoint directly, without the bridge.

claude mcp add --transport http logpresso https://CONTROL_NODE_HOST/mcp -H "Authorization: Bearer API_KEY"