Hosted OpenSearch MCP quickstart

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

Public URL:

@mcp.endpointAddress

Related product pages: Hosted OpenSearch MCP (opens in a new tab), Hosted OpenSearch (opens in a new tab). New accounts can start with a 14-day trial (opens in a new tab).

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

1. A Logit.io account (opens in a new tab) on a Log Management or Custom plan.
2. A Logs or OpenSearch stack with data you can search.
3. Permission to enable MCP on the stack (stack administrator or account owner/admin).
4. An AI client that supports remote MCP over HTTPS with custom headers (Cursor or Claude Desktop).

1. Enable on a stack

1. Sign in to the Logit.io Dashboard (opens in a new tab).
2. Open the stack Settings page (Overview).
3. In Access, find OpenSearch MCP.
4. 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. Enable separately on each stack you want clients to reach.

2. Copy connection details

Open Settings → Endpoints. The OpenSearch MCP (read-only) section shows:

Rotate the MCP API key from the Endpoints page when you need to invalidate a previous key. Do not reuse your OpenSearch -es stack API key for MCP.

3. Connect Cursor

1. Copy the example MCP config from Settings → Endpoints, or use the auto-filled example below when signed in.
2. In Cursor, open Settings → MCP (or edit your MCP config file, for example .cursor/mcp.json).
3. Add a server entry, or merge the logit-opensearch block into an existing mcpServers object.
4. Save, then confirm the server connects and tools are listed.

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

The Endpoints page also provides a ready-to-copy block with the correctly encoded Authorization header. Prefer that over encoding credentials by hand.

4. Connect Claude Desktop

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 your client version requires it. Confirm the Logit.io server appears and tools are listed.

If your Claude build does not support remote HTTPS MCP with custom headers yet, use Cursor for now, or check Claude's MCP docs for the transport your version supports.

5. First successful query

Once tools are listed:

1. Ask the client to list indexes on the connected stack.
2. Pick an index name from the response.
3. Ask it to search that index for something you expect in the data — for example a recent timeout, 5xx, or service name.

You should see tool calls against the stack and either matching hits or an empty result set. Either way, the connection is working.

Hosted MCP is read-only. Write tools are not available. For writes and admin automation, use the OpenSearch REST API or the Developer API.

Limitations

Troubleshooting

Next steps

• Connect to Your Cluster — stack API key on -es
• OpenSearch API (user credentials) — role-scoped REST API
• Search APIs
• Managed Stack Limitations
• Hosted OpenSearch (opens in a new tab) — managed OpenSearch overview
• Start a trial (opens in a new tab) — 14 days, no credit card