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.
72 lines
2.2 KiB
TOML
72 lines
2.2 KiB
TOML
id = "jira"
|
|
name = "Jira"
|
|
description = "Access Jira issues, projects, boards, and sprints through the Atlassian MCP server"
|
|
category = "devtools"
|
|
icon = "lucide:clipboard-list"
|
|
tags = ["project-management", "issues", "agile", "atlassian", "tracking"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@aashari/mcp-server-atlassian-jira@3.3.0"]
|
|
|
|
[[required_env]]
|
|
name = "JIRA_API_TOKEN"
|
|
label = "Jira API Token"
|
|
help = "An API token generated from your Atlassian account"
|
|
is_secret = true
|
|
get_url = "https://id.atlassian.com/manage-profile/security/api-tokens"
|
|
|
|
[[required_env]]
|
|
name = "JIRA_INSTANCE_URL"
|
|
label = "Jira Instance URL"
|
|
help = "Your Jira Cloud instance URL (e.g., https://yourcompany.atlassian.net)"
|
|
is_secret = false
|
|
get_url = ""
|
|
|
|
[[required_env]]
|
|
name = "JIRA_USER_EMAIL"
|
|
label = "Jira User Email"
|
|
help = "The email address associated with your Atlassian account"
|
|
is_secret = false
|
|
get_url = ""
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a new API token.
|
|
2. Enter your Jira Cloud instance URL (e.g., https://yourcompany.atlassian.net) and the email linked to your Atlassian account.
|
|
3. Paste the API token into the JIRA_API_TOKEN field above.
|
|
"""
|
|
|
|
|
|
[i18n.zh]
|
|
name = "Jira"
|
|
description = "通过 Atlassian MCP 服务器访问 Jira 的工单、项目、看板与 Sprint。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "Jira"
|
|
description = "透過 Atlassian MCP 伺服器存取 Jira 的工單、專案、看板與 Sprint。"
|
|
|
|
[i18n.ja]
|
|
name = "Jira"
|
|
description = "Atlassian MCP サーバー経由で Jira の課題、プロジェクト、ボード、スプリントにアクセス。"
|
|
|
|
[i18n.ko]
|
|
name = "Jira"
|
|
description = "Atlassian MCP 서버를 통해 Jira 이슈, 프로젝트, 보드, 스프린트에 접근."
|
|
|
|
[i18n.de]
|
|
name = "Jira"
|
|
description = "Zugriff auf Jira-Vorgänge, -Projekte, -Boards und -Sprints über den Atlassian-MCP-Server."
|
|
|
|
[i18n.es]
|
|
name = "Jira"
|
|
description = "Accede a issues, proyectos, tableros y sprints de Jira mediante el servidor MCP de Atlassian."
|
|
|
|
[i18n.fr]
|
|
name = "Jira"
|
|
description = "Accès aux tickets, projets, tableaux et sprints Jira via le serveur MCP Atlassian."
|