Context7 Platform -- Up-to-date docs for AI agents
chore(release): version packages (#2576)
github-actions[bot]13f3ef03d995
diff --git a/.changeset/accept-hallucinated-tool-args.md b/.changeset/accept-hallucinated-tool-args.mddeleted file mode 100644index 374476c9..00000000--- a/.changeset/accept-hallucinated-tool-args.md+++ /dev/null@@ -1,5 +0,0 @@-----"@upstash/context7-mcp": patch------Accept hallucinated argument names on `tools/call` requests by rewriting them to the canonical names before validation. `userQuery` and `question` are mapped to `query` on either tool; on `query-docs`, `context7CompatibleLibraryID`, `libraryID`, and `libraryName` are mapped to `libraryId`. Some LLM clients produce these alternative names — likely echoing phrasing from each tool's description — and previously triggered `Invalid input: expected string, received undefined` errors. `libraryName` is only rewritten on `query-docs` calls because it is the canonical arg for `resolve-library-id`. Tool input schemas published via `tools/list` are unchanged: canonical names remain the documented required fields, the rewrite is purely a server-side compatibility shim that runs only on `tools/call` and only when the canonical key is absent.diff --git a/.changeset/handle-mcp-config-detection-errors.md b/.changeset/handle-mcp-config-detection-errors.mddeleted file mode 100644index a906dce0..00000000--- a/.changeset/handle-mcp-config-detection-errors.md+++ /dev/null@@ -1,5 +0,0 @@-----"ctx7": patch------Handle malformed MCP config files gracefully during `ctx7 remove` agent detection. Previously, an unparseable JSON config at any agent's well-known path (e.g. a hand-edited `~/.claude.json`) would crash the command with an unhandled `SyntaxError` before it could do anything. The detector now skips the offending file and logs a warning naming the path and parse error so the user can fix it, while detection continues for the remaining agents.diff --git a/.changeset/mcp-stdio-orphan-exit.md b/.changeset/mcp-stdio-orphan-exit.mddeleted file mode 100644index 5a5281bb..00000000--- a/.changeset/mcp-stdio-orphan-exit.md+++ /dev/null@@ -1,5 +0,0 @@-----"@upstash/context7-mcp": patch------Exit the stdio MCP server when the parent process closes its stdio. Previously, if the parent (e.g. Claude Code) was force-killed shortly after a tool call, an idle undici keep-alive socket to the Context7 API would keep libuv's event loop alive past stdin EOF, leaving an orphaned `node` process that consumed memory until the kernel tore the socket down (which on Cloudflare-fronted endpoints can take hours). The server now listens for `end`/`close` on stdin and `SIGHUP` and exits cleanly. Fixes #2542.diff --git a/.changeset/respect-claude-config-dir.md b/.changeset/respect-claude-config-dir.mddeleted file mode 100644index b63e0f36..00000000--- a/.changeset/respect-claude-config-dir.md+++ /dev/null@@ -1,5 +0,0 @@-----"ctx7": patch------Respect `CLAUDE_CONFIG_DIR` env var when resolving Claude Code's global config, rules, skills, and detection pathsdiff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.mdindex 54d2ae3f..544ee25e 100644--- a/packages/cli/CHANGELOG.md+++ b/packages/cli/CHANGELOG.md@@ -1,5 +1,12 @@# Changelog+## 0.4.2++### Patch Changes++- 6c71e4d: Handle malformed MCP config files gracefully during `ctx7 remove` agent detection. Previously, an unparseable JSON config at any agent's well-known path (e.g. a hand-edited `~/.claude.json`) would crash the command with an unhandled `SyntaxError` before it could do anything. The detector now skips the offending file and logs a warning naming the path and parse error so the user can fix it, while detection continues for the remaining agents.+- 4056850: Respect `CLAUDE_CONFIG_DIR` env var when resolving Claude Code's global config, rules, skills, and detection paths+## 0.4.1### Patch Changesdiff --git a/packages/cli/package.json b/packages/cli/package.jsonindex eacce5a0..f3b5552f 100644--- a/packages/cli/package.json+++ b/packages/cli/package.json@@ -1,6 +1,6 @@{"name": "ctx7",- "version": "0.4.1",+ "version": "0.4.2","description": "Context7 CLI - Manage AI coding skills and documentation context","type": "module","bin": {diff --git a/packages/mcp/CHANGELOG.md b/packages/mcp/CHANGELOG.mdindex e34cde95..0d57490a 100644--- a/packages/mcp/CHANGELOG.md+++ b/packages/mcp/CHANGELOG.md@@ -1,5 +1,12 @@# @upstash/context7-mcp+## 2.2.5++### Patch Changes++- 187287c: Accept hallucinated argument names on `tools/call` requests by rewriting them to the canonical names before validation. `userQuery` and `question` are mapped to `query` on either tool; on `query-docs`, `context7CompatibleLibraryID`, `libraryID`, and `libraryName` are mapped to `libraryId`. Some LLM clients produce these alternative names — likely echoing phrasing from each tool's description — and previously triggered `Invalid input: expected string, received undefined` errors. `libraryName` is only rewritten on `query-docs` calls because it is the canonical arg for `resolve-library-id`. Tool input schemas published via `tools/list` are unchanged: canonical names remain the documented required fields, the rewrite is purely a server-side compatibility shim that runs only on `tools/call` and only when the canonical key is absent.+- 78b9826: Exit the stdio MCP server when the parent process closes its stdio. Previously, if the parent (e.g. Claude Code) was force-killed shortly after a tool call, an idle undici keep-alive socket to the Context7 API would keep libuv's event loop alive past stdin EOF, leaving an orphaned `node` process that consumed memory until the kernel tore the socket down (which on Cloudflare-fronted endpoints can take hours). The server now listens for `end`/`close` on stdin and `SIGHUP` and exits cleanly. Fixes #2542.+## 2.2.4### Patch Changesdiff --git a/packages/mcp/package.json b/packages/mcp/package.jsonindex b3c77a3a..34559902 100644--- a/packages/mcp/package.json+++ b/packages/mcp/package.json@@ -1,6 +1,6 @@{"name": "@upstash/context7-mcp",- "version": "2.2.4",+ "version": "2.2.5","mcpName": "io.github.upstash/context7","description": "MCP server for Context7","scripts": {