Release notes for @neus/sdk, @neus/mcp-server, docs, and examples.
Format follows Keep a Changelog.
- Install SSOT —
docs/install.mdx,docs/mcp/setup.mdx, anddocs/mcp/journeys.mdxreplace the legacyintegrations/tree. - Public copy — first-touch README, install, MCP registry, plugin, and SDK surfaces use the GTM hierarchy (trust infrastructure → trust receipts → NEUS Verify).
- Version alignment —
@neus/sdk,@neus/mcp-server, plugin, marketplace, andserver.jsonaligned to1.1.5.
integrations/— redundant host install files; usenpx -y -p @neus/sdk neus setupand Install NEUS..github/PULL_REQUEST_TEMPLATE.md— use GitHub issue templates and a clear PR description instead.- Repo-root
scripts/— maintainer guardrails and OG generators are not part of the public integrator surface.
npx -y -p @neus/sdk@1.1.5 neus setup
npx -y -p @neus/sdk@1.1.5 neus auth
npx -y -p @neus/sdk@1.1.5 neus doctor --live- NEUS Trust install flow - product docs now start from hosted MCP setup for supported agent environments.
- Claude plugin path fix -
skillsfield changed from./skills/neus-trust-workflowtoskills/neus-trust-workflowto prevent Claude Code path-escape validation from silently dropping the plugin. - Install router - new docs page at
/installroutes users by environment. - Version alignment -
@neus/sdk,@neus/mcp-server, plugin, marketplace, andserver.jsonall aligned to1.1.3.
docs/install.mdx- single install router with platform cards and trust block.integrations/- host setup files for Cursor, Claude Code, VS Code, Codex, OpenAI, CI, MCP discovery, and Cline.- Cline support - added to docs, CLI hints, and integration adapters.
server.jsontitle changed from "NEUS MCP" to "NEUS Trust"; description aligned to product tagline.plugin.jsonandmarketplace.jsondescriptions aligned to product tagline.- Homepage URLs - all metadata
homepage/websiteUrlfields now point tohttps://docs.neus.network/install. - Docs reframe -
docs/mcp/ide-plugin.mdxreframed as "Install NEUS Trust"; Claude marketplace commands collapsed into<Accordion>. - Branding cleanup - removed "NEUS for AI assistants" as a page/card title across docs, READMEs, and SDK. Replaced with "Install NEUS Trust".
docs/mcp/setup.mdx- fixed corrupted UTF-8 characters (em-dash, middle-dot, arrow).docs/agents/agent-identity.mdx- removed speculative external links (agentskills.io,skills.sh).examples/trust-receipts-showcase/README.md- "trust marketplace" → "trust showcase".sdk/README.md- fixed MCP docs table alignment.- Placeholder realism - replaced
gate_abc123withgate_your-app-namein all docs and READMEs.
- Legacy
docs/images/neus-mark.png,docs/images/neus-logo.svg(embedded monogram), andsdk/neus-logo.svg.
npx -y -p @neus/sdk@1.1.3 neus setup
npx -y -p @neus/sdk@1.1.3 neus auth
npx -y -p @neus/sdk@1.1.3 neus doctor --live@neus/sdk/mcp-hosts- shared helper for MCP install URLs, setup/auth commands, and product "Open in" hosts (Cursor, Claude Code, Codex).
neus import --from auto- prefers Claude Code, Cursor, and Claude Desktop when multiple agent workspaces are detected.- Public setup docs keep assistant MCP setup separate from server-side setup.
- Product/UI alignment: Codex setup uses
--client codexand Codex-owned OAuth, not VS Code client flags.
1.1.1 - 2026-05-28
- MCP discovery + runtime alignment -
neus_contextreturns signed-in profile context; discovery metadata and docs match live hosted MCP behavior. - NEUS for AI assistants - install hub, plugin, and docs use one OAuth-first messaging stack across Cursor, Codex, VS Code, and Claude Code.
@neus/mcp-serverserver.json- updated tool descriptions, session bootstrap prompt, and ide-plugin discovery URL (requires npm republish; runtime ships with protocol deploy).neus setup/ CLI - Codex uses~/.codex/config.tomlthroughcodex mcp add; VS Code keeps its own MCP config paths. Setup hints point to NEUS for AI assistants.- NEUS Trust plugin (v1.1.1) - marketplace version tracks
@neus/sdk@1.1.1/@neus/mcp-server@1.1.1. - Docs, plugin skill, and public README aligned to trust-infrastructure positioning and streamlined MCP startup (
neus_contextonce;neus_mefor refresh or public lookup only).
- npm discovery metadata drift vs git and live MCP after the 1.1.0 publish window.
npx -y -p @neus/sdk@1.1.1 neus setup
npx -y -p @neus/sdk@1.1.1 neus auth
npx -y -p @neus/sdk@1.1.1 neus doctor --live1.1.0 - 2026-05-26
- OAuth-first MCP onboarding - connect editors and assistants in three commands:
neus setup->neus auth->neus doctor --live. @neus/mcp-serveron npm with OAuth discovery metadata for MCP registries and installers.- Twelve public MCP tools documented end-to-end, including encrypted secrets (
neus_secret_*). - NEUS Trust plugin (v1.1.0) - Claude Code marketplace install for hosted MCP + trust workflow skill.
@neus/mcp-servernpm package (discovery metadata only; runtime stays athttps://mcp.neus.network/mcp).- MCP docs: Encrypted secrets, OAuth client reference (
neus-cli), npm package table in MCP setup. - Roadmap - shipped work and planned milestones.
- CLI:
neus setupreminds you to runneus authwhen no credential is configured. - Hosted MCP server-card includes OAuth discovery (
authorization.resource_metadata_url).
- Default MCP auth path is OAuth, not Profile access keys. Keys remain supported for servers and CI only.
- Docs and setup flows on neus.network now lead with OAuth first.
- MCP discovery at
/.well-known/mcp.jsonpoints to the hosted server with the current twelve-tool listing. @neus/mcp-serverdiscovery metadata uses OAuth-first tool descriptions.
- Docs, setup flows, API discovery, and live MCP metadata now match.
- CLI setup no longer suggests unsupported MCP client names.
npx -y -p @neus/sdk@1.1.0 neus setup
npx -y -p @neus/sdk@1.1.0 neus auth
npx -y -p @neus/sdk@1.1.0 neus doctor --liveIf you already use a Profile access key for automation, keep neus setup --access-key <npk_...>. Interactive editors should prefer OAuth.
1.0.12 - 2026-05-26
@neus/sdkwith hosted MCP CLI (neus setup,neus auth, import/export) and OAuth browser flow.