Skip to content

Add @zunialab/mcp, and point the READMEs at the public relay - #12

Merged
danbaruka merged 2 commits into
mainfrom
sdk-mcp
Oct 13, 2026
Merged

danbaruka merged 2 commits into
mainfrom
sdk-mcp

Conversation

@danbaruka

Copy link
Copy Markdown
Member

What changes

  • New package @zunialab/mcp 0.1.0. An MCP server for coding assistants, over stdio and stateless Streamable HTTP (MCP SDK v2). It serves clients on the 2026-07-28 protocol and 2025-era clients alike.
    • It answers from the published docs (docs-index.json, written by every docs build), npm and the Zunia chain registry, read when asked. Nothing is bundled, so an answer is never older than what is published.
    • 12 read-only tools: search_docs, get_doc, list_docs, list_integrations, get_integration_guide, get_sdk_packages, get_chain, check_address, explain_error, verify_sign_in, ibc_denom, build_forward_memo.
    • The last four run the SDK's own explainZuniaError, verifySignIn, ibcDenomHash and buildForwardMemo, so answers match the shipped packages.
    • Docs pages are served as resources, plus one prompt, integrate_zunia.
  • READMEs. api.zunialab.com is open to any site: CORS is open on /v1/connect/, and Zunia mobile store builds trust only that relay. The examples now use it instead of telling dApps to run their own. The MCP package is listed.
  • Release checks. scripts/pack.mjs and smoke-tarballs.mjs now cover the new package. The smoke test installs the packed tarball and talks to its bin over stdio.

After merge

  • The redeploy timer rebuilds zunia-sdk on the server. With the zunia-infra PR merged, zunia-mcp.service serves https://docs.zunialab.com/mcp.
  • Publish to npm: 0.1.1 of sdk-core, sdk-web, sdk-react and interchain (npm still has 0.1.0), plus @zunialab/mcp 0.1.0. Then tag v0.1.1.

Checks run

  • pnpm build, typecheck and test pass: 720 tests (interchain 543, core 91, web 44, mcp 37, react 5).
  • check:packages passes (publint, attw), and so does smoke:tarballs (Node, Vite, and the MCP bin over stdio).
  • The MCP was tested end to end with the official v2 client:
    • over HTTP and stdio, on both protocol generations;
    • against the real docs build and live npm/GitHub;
    • behind the production nginx config, in a container.

🤖 Generated with Claude Code

danbaruka and others added 2 commits October 14, 2026 00:43
Stdio and stateless Streamable HTTP, on MCP SDK v2, for 2026-07-28 and
2025-era clients alike. It answers from the published docs-index.json, npm
and the Zunia chain registry, read when asked, and runs the SDK's own
explainZuniaError, verifySignIn, ibcDenomHash and buildForwardMemo, so an
answer matches the shipped packages. Read-only: it never signs and holds no
keys. The tarball checks and smoke test now cover it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…MCP server.

api.zunialab.com has served zunia.connect.v2 to any dApp origin since the
relay went public (CORS is open on /v1/connect/), so the examples use it
and no longer tell dApps to run their own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@danbaruka
danbaruka merged commit 34142ee into main Oct 13, 2026
1 check passed
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.

1 participant