A collection of high-quality, framework-agnostic tools for building AI applications in Node.
GemStack is shared, community-governed infrastructure built with the Vike team. Each tool is a standalone, well-tested package that works in any Node app and composes cleanly with the others. Packages join GemStack by graduating one at a time, when they prove framework-agnostic value, not by bulk-moving a framework's package set in.
All packages publish under the @gemstack/ scope (e.g. npm install @gemstack/ai-sdk).
Full documentation lives in docs/ (a hosted site is on the way): a guide, a getting-started walkthrough, and a deep guide per package (linked in the Docs column below).
| Package | Description | Docs | Version |
|---|---|---|---|
ai‑sdk |
The agent runtime: providers, the agent loop, tools, streaming, middleware, structured output, memory, and evals. The engine the rest of the AI family builds on. | Guide |  |
ai‑skills |
Portable capability bundles: load SKILL.md skills (instructions + tools + resources) and compose them onto an agent on demand. |
Guide |  |
ai‑autopilot |
Orchestration: a Supervisor that plans, dispatches subagents (bounded concurrency + budget guardrails), and synthesizes the result. | Guide |  |
ai‑mcp |
The agent/MCP bridge: consume a remote MCP server's tools as agent tools, and expose an agent as an MCP server. | Guide |  |
mcp |
A standalone framework for authoring MCP servers: tools, resources, prompts, decorators, OAuth 2.1, a framework-neutral HTTP handler, and a test client. Agent-agnostic. | Guide |  |
@gemstack/ai-sdk agent runtime (the "verbs")
@gemstack/ai-skills capability bundles (the composable "nouns") -> ai-sdk
@gemstack/ai-autopilot orchestration / autonomy (the "director") -> ai-sdk (+ skills)
@gemstack/ai-mcp agent <-> MCP bridge (the "adapter") -> ai-sdk
-----------------------------------------------------------------------------------
@gemstack/mcp standalone MCP server framework agent-agnostic, not ai-*
The ai- prefix means "depends on the agent runtime." skills, autopilot, and ai-mcp all depend on ai-sdk; ai-sdk depends on none of them, and nothing depends "up." A package about AI that is agent-agnostic (like @gemstack/mcp) is a peer of the family, not a member of it.
See Architecture.md for the full layering, naming rule, and graduation policy.
The two MCP packages point in opposite directions, so they are never duplicates:
Exposing an existing agent? Use
@gemstack/ai-mcp. It makes an agent speak MCP, or feeds remote MCP tools into one.Authoring a server from scratch (tools / resources / prompts / auth)? Use
@gemstack/mcp. A full server framework, with no agent involved.
pnpm install
pnpm build # build all packages (Turborepo)
pnpm dev # watch mode
pnpm typecheck
pnpm testThis is a pnpm + Turborepo + Changesets monorepo. Runnable examples live under examples/ (e.g. examples/mcp-quickstart). See .changeset/README.md for the release flow.
The AI family was spun out of Rudder's mature @rudderjs/ai (v1.17.x) and re-versioned under the GemStack umbrella; @gemstack/mcp is the graduation of @rudderjs/mcp. The old @rudderjs/* names live on as the Rudder bindings over these engines: they re-export the agnostic core and add the framework-specific pieces that cannot graduate (e.g. @rudderjs/ai's AiProvider, ORM-backed stores, doctor check, and make:agent / ai:eval CLI).
GemStack is co-governed (shared npm @gemstack org + gemstack-land GitHub org). New tools join by mutual agreement; publish rights and 2FA are shared per the governance note.