ctx7-2685: Add Context7 SDK agent examples

[fahreddinozcan]

Summary

• add a standalone Vercel AI SDK 6 ToolLoopAgent backed by Context7 tools
• reuse the same agent in a deployable Next.js app
• add a filesystem-first Vercel Eve agent with native Context7 tools
• add one-click Vercel deploy buttons with required Context7 and OpenAI environment variables
• add a LangChain agent backed by Context7 SDK tools
• keep each example independently runnable with the published Context7 SDK
• run repository build and release workflows on Node 24, as required by Eve
• include example changes in workspace typecheck, lint, formatting, build, and CI checks

Validation

• pnpm --dir examples/ai-sdk agent -- "How do I revalidate a Next.js page on demand?"
• pnpm --dir examples/eve invoke "How do I revalidate a Next.js page on demand?"
• pnpm --dir examples/eve build
• Vercel-mode Eve build generated .vercel/output with the nodejs24.x runtime
• pnpm typecheck
• pnpm lint:check
• pnpm format:check
• pnpm build
• git diff --check

[linear-code]

CTX7-2685

[enesgules]

Thanks for this. Three blocking items, then smaller ones inline.

Blocking

1. The AI SDK example re-implements the tools that @upstash/context7-tools-ai-sdk already publishes (Context7Agent, resolveLibraryId, queryDocs). The example should use the package.
2. pnpm build is pnpm -r run build, so release and canary now run next build and eve build and install Next/React/LangChain/Eve on every publish. Filter examples out of release builds.
3. The Node 24 bump on release/canary is only needed by Eve. Published packages declare node >=20.18.1; CI should keep building them on 20.

Also

• Root package.json still has "workspaces": ["packages/*"]. pnpm ignores it, but it is now wrong. Update or remove.

Verified OK: SDK call signatures, deploy button URLs and env keys, npm (not workspace) dependency on the SDK so the clone installs standalone.

[enesgules]

This file duplicates packages/tools-ai-sdk. Replace with:

import { openai } from "@ai-sdk/openai";
import { Context7Agent } from "@upstash/context7-tools-ai-sdk";

export const agent = new Context7Agent({ model: openai("gpt-5-mini") });

An example that bypasses the official package signals that the package is not the recommended path.

[enesgules]

Keep 20 here. Published packages declare engines.node >=20.18.1; release CI should build on the minimum supported version. Node 24 is only required by the Eve example, which should not be part of the release build (see comment on examples/ai-sdk/package.json).

[enesgules]

Same as release.yml: keep 20.

[enesgules]

Bumping the single test job to 24 means packages are no longer tested on 20. Use a matrix ([20, 24]) or run the Eve typecheck in a separate job on 24.

[enesgules]

With examples/* in the workspace, root pnpm build (pnpm -r run build) now runs next build and eve build on every release and canary, and pnpm install --frozen-lockfile pulls Next, React, LangChain, and Eve (+1700 lockfile lines) into the publish pipeline. Either change the release workflows to pnpm --filter "./packages/*" build, or drop build scripts from the examples and keep only typecheck/lint.

[enesgules]

A new client per tool call is unnecessary. const context7 = new Context7(); at module level is enough (same in resolve_library.ts), as the LangChain example already does.

[enesgules]

Use ctx7sk-... like the other two examples. The SDK warns when the key does not start with ctx7sk.

[enesgules]

This example uses .env, the other two use .env.local. Pick one for all three.

[enesgules]

No .gitignore here or in examples/ai-sdk. examples/eve has one. The Vercel deploy button clones the folder into a fresh repo with no root .gitignore, so .env.local and .next can end up committed. Add the same .gitignore to both.

[enesgules]

Worth one line noting that the Eve example is on ai@7 / @ai-sdk/openai@4 (Eve peer requirement) while the AI SDK example is on ai@6 / @ai-sdk/openai@3, so readers do not assume a mistake.