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
830 B
TOML
29 lines
830 B
TOML
id = "brave-search"
|
|
name = "Brave Search"
|
|
description = "Perform web searches using the Brave Search API through the MCP server"
|
|
category = "ai"
|
|
icon = "🦁"
|
|
tags = ["search", "web", "brave", "api", "information-retrieval"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@modelcontextprotocol/server-brave-search@0.6.2"]
|
|
|
|
[[required_env]]
|
|
name = "BRAVE_API_KEY"
|
|
label = "Brave Search API Key"
|
|
help = "An API key from the Brave Search API dashboard"
|
|
is_secret = true
|
|
get_url = "https://brave.com/search/api/"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Go to https://brave.com/search/api/ and sign up for a Brave Search API plan (free tier available).
|
|
2. Generate an API key from your Brave Search API dashboard.
|
|
3. Paste the API key into the BRAVE_API_KEY field above.
|
|
"""
|