Evan
7881d327a5
* refactor: migrate icon fields from emoji to lucide:<name> tokens
Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:
- Emoji render very differently across OS/browser/font stacks; the
registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
their icons stored as literal Python-style escape strings
("\\U0001F3AC") because the TOML parser upstream never decoded
them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
[i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
up correctly.
87 files touched. example manifests left untouched (still "TODO").
* fix: backfill i18n name + drop the single-member email category
- Every existing [i18n.<lang>] block now has a `name` field. 60 files
previously translated description but kept the English name
implicitly — which rendered as "some English some Chinese" in the
registry UI. Fill in the missing name from the English brand (or a
known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
reclassify it as "messaging" so the sub-category filter chip list
on the category page isn't littered with singletons.
* feat(i18n): localize 76 agents/integrations/plugins into 7 languages
Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.
Coverage:
- 32 agents (academic-researcher, analyst, architect, assistant,
code-reviewer, coder, customer-support, data-scientist, debugger,
devops-lead, doc-writer, email-assistant, health-tracker,
hello-world, home-automation, legal-assistant, meeting-assistant,
ops, orchestrator, personal-finance, planner, recipe-assistant,
recruiter, researcher, sales-assistant, security-auditor,
social-media, test-engineer, translator, travel-planner, tutor,
writer)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
brand names kept as-is across all locales, only descriptions
translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
episodic-memory, guardrails, keyword-memory, mempalace-indexer,
sentiment-tracker, todo-tracker, topic-memory, user-profile)
The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.
* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam
Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.
- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
were already present). Brand names kept as-is in all locales so users
recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
translation mirrors the existing zh one in structure and tone so the
catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
(zh-TW, de, es, fr).
Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
58 lines
1.6 KiB
TOML
58 lines
1.6 KiB
TOML
id = "brave-search"
|
|
name = "Brave Search"
|
|
description = "Perform web searches using the Brave Search API through the MCP server"
|
|
category = "ai"
|
|
icon = "lucide:shield"
|
|
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.
|
|
"""
|
|
|
|
|
|
[i18n.zh]
|
|
name = "Brave Search"
|
|
description = "通过 MCP 服务器使用 Brave Search API 进行网页搜索。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "Brave Search"
|
|
description = "透過 MCP 伺服器使用 Brave Search API 進行網頁搜尋。"
|
|
|
|
[i18n.ja]
|
|
name = "Brave Search"
|
|
description = "MCP サーバー経由で Brave Search API を使ってウェブ検索を実行。"
|
|
|
|
[i18n.ko]
|
|
name = "Brave Search"
|
|
description = "MCP 서버를 통해 Brave Search API로 웹 검색을 수행."
|
|
|
|
[i18n.de]
|
|
name = "Brave Search"
|
|
description = "Websuche über die Brave-Search-API per MCP-Server."
|
|
|
|
[i18n.es]
|
|
name = "Brave Search"
|
|
description = "Realiza búsquedas web usando la API de Brave Search a través del servidor MCP."
|
|
|
|
[i18n.fr]
|
|
name = "Brave Search"
|
|
description = "Recherches web via l'API Brave Search et le serveur MCP."
|