MCP Insights Proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENSEARCH_URL | Yes | Cluster URL for OpenSearch | |
| OPENSEARCH_PASS | No | Basic auth password | |
| OPENSEARCH_USER | No | Basic auth username | |
| OPENSEARCH_INDEX | No | Default index name | channel_posts |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opensearch_queryA | Execute ANY OpenSearch DSL query and return synthesized results. You have FULL FLEXIBILITY to build any query:
The proxy executes your query and returns COMPACT formatted output instead of raw JSON. OUTPUT FORMATS:
IMPORTANT: Build the full DSL query object as you normally would. |
| opensearch_countA | Quick document count with optional query filter. Lighter than full query. |
| opensearch_mappingA | Get index mapping to understand available fields. Returns compact field list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: count for lightweight counts, query for arbitrary DSL queries, and mapping for schema inspection. No overlap or ambiguity between them.
All tool names follow the same pattern: 'opensearch_' prefix followed by a single descriptive verb/noun (count, query, mapping). This is perfectly consistent and predictable.
With 3 tools, the set is compact and focused on core OpenSearch operations (count, query, mapping). It feels slightly minimal but appropriate for a read-only insights proxy, and each tool earns its place.
The domain is OpenSearch insights/querying, and the set covers count, query, and schema discovery, which are the essential operations. Minor gaps like direct document fetch or index listing can be handled via queries or mapping, so no critical dead ends.