Evan
c25a321e88
* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
36 lines
1.1 KiB
TOML
36 lines
1.1 KiB
TOML
id = "elasticsearch"
|
|
name = "Elasticsearch"
|
|
description = "Search and manage Elasticsearch indices and documents through the MCP server"
|
|
category = "data"
|
|
icon = "🔍"
|
|
tags = ["search", "database", "indexing", "analytics", "full-text"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@elastic/mcp-server-elasticsearch@0.3.1"]
|
|
|
|
[[required_env]]
|
|
name = "ELASTICSEARCH_URL"
|
|
label = "Elasticsearch URL"
|
|
help = "The base URL of your Elasticsearch cluster (e.g., https://my-cluster.es.us-east-1.aws.found.io:9243)"
|
|
is_secret = false
|
|
get_url = ""
|
|
|
|
[[required_env]]
|
|
name = "ELASTICSEARCH_API_KEY"
|
|
label = "Elasticsearch API Key"
|
|
help = "An API key with read/write permissions for the target indices"
|
|
is_secret = true
|
|
get_url = ""
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Obtain your Elasticsearch cluster URL from your Elastic Cloud dashboard or self-hosted instance configuration.
|
|
2. Create an API key in Kibana (Stack Management > API Keys) with appropriate index permissions.
|
|
3. Paste the cluster URL and API key into the fields above.
|
|
"""
|