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
29 lines
795 B
TOML
29 lines
795 B
TOML
id = "exa-search"
|
|
name = "Exa Search"
|
|
description = "Perform AI-powered neural searches and retrieve web content through the Exa MCP server"
|
|
category = "ai"
|
|
icon = "🔎"
|
|
tags = ["search", "web", "ai", "neural", "semantic", "information-retrieval"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "exa-mcp-server@3.1.9"]
|
|
|
|
[[required_env]]
|
|
name = "EXA_API_KEY"
|
|
label = "Exa API Key"
|
|
help = "An API key from the Exa dashboard"
|
|
is_secret = true
|
|
get_url = "https://dashboard.exa.ai/api-keys"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Go to https://dashboard.exa.ai/ and create an account or sign in.
|
|
2. Navigate to API Keys (https://dashboard.exa.ai/api-keys) and generate a new key.
|
|
3. Paste the API key into the EXA_API_KEY field above.
|
|
"""
|