Skip to content

site(ecosystem): feature mcp-server-ava and ai-sdk-ava - #1059

Open
DoubleCore wants to merge 2 commits into
antvis:aifrom
DoubleCore:feat/ecosystem-ai-sdk-mcp
Open

DoubleCore wants to merge 2 commits into
antvis:aifrom
DoubleCore:feat/ecosystem-ai-sdk-mcp

Conversation

@DoubleCore

@DoubleCore DoubleCore commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds the two integrations built for #1046 and #1047 to the ecosystem carousel:

Card Package Repository
mcp-server-ava MCP server over stdio https://github.com/DoubleCore/mcp-server-ava
ai-sdk-ava Vercel AI SDK tools https://github.com/DoubleCore/ai-sdk-ava

Names follow the maintainer guidance in the threads (@hustcc in #1046: ai-sdk-ava; @hustcc / @yvonneyx in #1047: mcp-server-ava). Both npm names are currently unclaimed.

Changes

  • site/components/landing/Ecosystem.tsx — two community cards, plus a protocol visual branch that renders a tool-chain preview for kind: 'mcp' | 'ai-sdk'. Wording goes through useTranslations, consistent with the existing cards.
  • site/components/landing/Ecosystem.module.css — .protocolVisual shares the layout rules with .sqlVisual / .traceVisual / .feishuVisual.
  • site/messages/{en,zh}.json — 9 new Ecosystem.* keys each, so the cards are localized rather than hardcoded English.

Diff: 4 files, +84 lines, no deletions.

Verification

  • next build (Next.js 16.4.3, Turbopack, static export) completes; out/index.html and out/zh/index.html both contain the two cards with the correct repo links and the translated visual copy.
  • TypeScript on the touched files reports no errors.

One local-only workaround was needed to build on Windows (new URL('..').pathname yields /C:/..., which Turbopack cannot canonicalize); it is not part of this PR — next.config.mjs is untouched.

Notes

Both packages are public and tested (12 and 6 vitest cases, plus an end-to-end MCP stdio smoke run against a live model). npm publication still needs an interactive login on my side, so install instructions point at the repos and reference @antv/ava@beta.

@DoubleCore
DoubleCore force-pushed the feat/ecosystem-ai-sdk-mcp branch from 287a538 to b30f607 Compare November 2, 2026 14:14
@DoubleCore DoubleCore changed the title site(ecosystem): feature the AVA MCP server and AI SDK tools site(ecosystem): feature mcp-server-ava and ai-sdk-ava Nov 2, 2026
@yvonneyx

yvonneyx commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

@DoubleCore 👍,帮忙也一起跟进下 MCP 和 AI SDK tools 的投递,进展直接回复在这个 PR 下就好,谢谢~

Comment thread site/messages/en.json Resolved
@DoubleCore

Copy link
Copy Markdown
Contributor Author

AI SDK tools / MCP Server 投递进展(当前状态,如实同步):

  • 两个包已在本地仓库完成:DoubleCore/ai-sdk-ava、DoubleCore/mcp-server-ava(版本 0.1.0,MIT)。
  • 阻塞点:本机 ~/.npmrc 的 npm_ token 已被 registry 判 401(/-/whoami 返回空对象、npm view 404),无法 npm publish;Vercel AI SDK Tools Registry 与 MCP Registry 都要求先有公开可安装的 npm 包,因此收录 PR 暂时无法提交。
  • 处理方式:需要重新执行 npm login(浏览器交互,非本机自动化可完成)。登录恢复后我会立即 publish 0.1.0 并在本 PR 下跟进两个收录 PR 的链接。

@hustcc

hustcc commented Nov 5, 2026

Copy link
Copy Markdown
Member

使用 npm 和 GitHub action 的 odic 安全发布方式,参考 ava 中的 publish action。

@DoubleCore

Copy link
Copy Markdown
Contributor Author

Trusted publishing (npm OIDC) release setup implemented per maintainer suggestion:

Repos / commits:

  • DoubleCore/ai-sdk-ava — a7b6365 (main, pushed, ls-remote verified)
  • DoubleCore/mcp-server-ava — d0d35bc (main, pushed, ls-remote verified)

What was added:

  • .github/workflows/publish.yml in both repos, modeled on AVA's ai branch publish workflow: triggers only on v*.*.* tags or workflow_dispatch; permissions: contents: read + id-token: write (no contents: write, no secrets, no NPM_TOKEN); steps = actions/checkout → actions/setup-node (Node 22.13.0, matching engines >= 22.13.0) → npm ci → typecheck → build → test → npm publish --provenance --access public. Both packages are public/unscoped.

Verified locally (both repos): tsc --noEmit clean, tsc -p tsconfig.build.json succeeds, vitest passes — ai-sdk-ava: 12/12 tests; mcp-server-ava: 6/6 tests (smoke script is a follow-up, not blocking).

Still pending (user-side): first publish requires npm Trusted Publisher configuration on npmjs.com binding repo DoubleCore/ai-sdk-ava / DoubleCore/mcp-server-ava + workflow publish.yml (no environment). READMEs document the binding + npm version/tag release flow. Nothing has been published yet; Registry/MCP directory submission is deferred until the first tagged release.

参考: antvis/AVA ai 分支的 publish.yml;改动为 tags+dispatch 触发、少权限、加 provenance 与 build/test 门禁。

@DoubleCore

Copy link
Copy Markdown
Contributor Author

已按评审意见在 82c8b9f1aaa0e9389da879c65c6c486e39397dd8 完成修复:将本 PR 新增的 9 个英文长句或含义不清的 i18n key 全部改为稳定的语义化标识(如 mcpServerAvaDescription、aiSdkVisualTitle、loadDataSchemaLabel),并同步更新 Ecosystem.tsx 引用。官网仍使用现有 use-intl / useTranslations('Ecosystem'),中英文文案与卡片行为保持不变,未在 JSX 中硬编码英文。

实际验证:Node.js 成功解析 site/messages/en.json 和 site/messages/zh.json,并断言 9 个新 key 在两种语言中均存在;git diff --check 通过;旧 key 定向检索无残留。当前环境没有 site/node_modules,因此未运行 TypeScript 检查或 Next.js 构建。

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants