Hosted OpenSearch MCP (Cursor / Claude)

Logit.io hosts a read-only OpenSearch MCP server (opens in a new tab) for your Logs and OpenSearch stacks. Connect AI clients such as Cursor or Claude Desktop without running MCP locally.

Public URL:

@mcp.endpointAddress

Available on Business and Custom plans. MCP uses a dedicated API key, separate from your OpenSearch HTTP API key on {stack-id}-es.logit.io.

When signed in with MCP enabled on your selected stack, examples auto-fill @mcp.endpointAddress, @mcp.username, @mcp.apiKey, and @mcp.base64encodedAuthString. If placeholders remain, enable MCP under stack Settings → Access, then refresh docs.

What you get

Hosted MCP endpoint per stack (no container or local process to maintain)
Read-only queries against that stack's OpenSearch data
Dashboard copy-paste config for Cursor / Claude
Independent key rotation on Settings → Endpoints

MCP is not a substitute for the full OpenSearch REST API. For programmatic write access or stack-key automation, use Connect to Your Cluster. For role-scoped human/CI API access, use OpenSearch API (user credentials).

Prerequisites

Account on a Business or Custom plan.
A Logs or OpenSearch stack.
Permission to enable MCP on the stack (stack administrator or account owner/admin).

Enable on a stack

Open the stack Settings page (Overview).
In Access, find OpenSearch MCP.
Select Enable.

Logit.io provisions {stack-id}-mcp.logit.io and generates a dedicated MCP API key.

Disable from the same Access card to remove the public MCP route for that stack.

Connection details

After enablement, open Settings → Endpoints. The OpenSearch MCP (read-only) section shows:

Field	Value
MCP URL	`@mcp.endpointAddress`
Username	`@mcp.username`
API Key	Dedicated MCP key (not the OpenSearch `-es` key) — `@mcp.apiKey` when signed in
Example config	JSON ready to paste into Cursor or Claude Desktop

You can rotate the MCP API key on the Endpoints page. The previous key stops working after rotation.

Cursor setup

Copy the example MCP config from Settings → Endpoints, or use the auto-filled example below when signed in.
Open Cursor MCP settings and add a server entry (or merge into your existing MCP config).

{
  "mcpServers": {
    "logit-opensearch": {
      "url": "@mcp.endpointAddress",
      "headers": {
        "Authorization": "Basic @mcp.base64encodedAuthString"
      }
    }
  }
}

The dashboard Endpoints page also provides a ready-to-copy block with the correctly encoded Authorization header.

Claude Desktop setup

Claude Desktop uses the same JSON shape. Paste the config from Settings → Endpoints (or the example above when signed in) into Claude's MCP server settings, then restart Claude Desktop if required by your client version.

Limitations

Topic	Behaviour
Write operations	Not available — MCP is always read-only
Credentials	Dedicated `{stack-id}-mcp` username + MCP API key; do not reuse the `-es` stack API key
Plan	Business and Custom only
Scope	One MCP endpoint per stack; enable separately on each stack you need

Troubleshooting

Symptom	What to check
401 Unauthorized	Using the MCP username (`@mcp.username`) and MCP API key from Endpoints? Key recently rotated?
404 / connection failed	MCP enabled on the stack? URL exact (`@mcp.endpointAddress`)? DNS may take a short time after enable.
Client cannot list tools	Confirm the client supports remote MCP over HTTPS with custom headers; re-paste the dashboard config.
Expected write tool missing	By design — hosted MCP does not expose write tools.
Docs still show placeholders	Select a stack with MCP enabled and refresh; JWT cookie only includes MCP fields when the feature is on.

Next steps

OpenSearch API (user credentials) — role-scoped REST API
Connect to Your Cluster — stack API key on -es
Search APIs
Managed Stack Limitations

OpenSearch API (user credentials)API Overview