Skip to main content
Glama
danilin-em

opensearch-dashboard-mcp

by danilin-em
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SSH_PROXY_TONoIf set (e.g. user@host), route all requests through an embedded SSH SOCKS5 tunnel to that host.
SSH_PROXY_PORTNoLocal port for the SSH tunnel; a free port is picked when unset.auto
OPENSEARCH_DASHBOARDS_URLNoBase URL of the OpenSearch Dashboards instance.http://localhost:5601
OPENSEARCH_DASHBOARDS_PASSWORDNoBasic auth / session-login password.
OPENSEARCH_DASHBOARDS_USERNAMENoBasic auth / session-login user.
OPENSEARCH_DASHBOARDS_VERIFY_TLSNoWhether to verify TLS certificates.true

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Check OpenSearch Dashboards connectivity and authenticate.

Hits the security authinfo endpoint. If unauthenticated (HTTP 401) and credentials are configured, performs a session login and re-checks. Reports {connected, authenticated, user, tenants} or the error reason.

list_saved_objectsA

List saved objects of a given type (dashboard, index-pattern, search, ...).

Calls the Dashboards saved_objects/_find API and returns a compact list of {id, title, type} so the LLM is not flooded with raw fields.

Saved objects are stored per multi-tenancy tenant. tenant selects which one to read via the securitytenant header:

  • a tenant name (e.g. "Developers Core", "Global")

  • "user" for the caller's private tenant

  • None (default) uses the user's configured default tenant Use the get_tenants tool to discover available tenant names.

get_tenantsA

List multi-tenancy tenants configured in OpenSearch Dashboards.

Uses the security plugin config API (/api/v1/configuration/tenants), which returns a map of tenant name -> metadata. Flattened here to a list of {name, description, reserved, hidden}.

get_index_patternsA

List index patterns configured in OpenSearch Dashboards.

Index patterns are saved objects of type index-pattern. Returns {id, title, time_field} where title is the pattern glob (e.g. logs-*) and time_field its time field, if any.

discover_searchA

Fetch documents like the Discover app.

Runs a search against an index pattern through the internal search API that OpenSearch Dashboards' Discover uses (/internal/search/opensearch), so it works even when the raw OpenSearch REST API is not exposed.

  • index: index-pattern glob, e.g. logs-api-* (discover them via list_saved_objects with type_="index-pattern").

  • query: Lucene query_string, e.g. level:error AND service:api. None matches everything.

  • time_from / time_to: range on time_field, e.g. now-15m / now or an ISO timestamp. Both optional.

  • time_field: timestamp field to filter/sort on (default @timestamp).

  • size: max hits to return (default 10; keep small — these are logs).

  • fields: restrict _source to these fields to avoid flooding the context. None returns the full document.

  • tenant: securitytenant header; usually unnecessary for raw data.

Returns {index, total, count, hits: [{_id, _index, _source}]} where total is the full match count (may be an estimate for large indices).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource or action: search, index patterns, tenants, saved objects, and connectivity. No overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., discover_search, get_index_patterns), and 'ping' is a standard imperative verb, fitting the pattern.

Tool Count5/5

5 tools is well-scoped for a dashboard interaction server, covering essential query and listing operations without being overly numerous.

Completeness4/5

Covers core read operations (search, list index patterns, tenants, saved objects) but lacks write operations (create/update/delete) and direct retrieval of saved object details, which are minor gaps for a query-focused tool.

Maintenance

ActivityStale
ResponsivenessUnresponsive

Resources