Context7 Platform -- Up-to-date docs for AI agents
chore(release): version packages (#3341)
github-actions[bot]47ef702bf591
diff --git a/.changeset/quick-owls-refresh.md b/.changeset/quick-owls-refresh.mddeleted file mode 100644index 2cbcfc3d..00000000--- a/.changeset/quick-owls-refresh.md+++ /dev/null@@ -1,5 +0,0 @@-----"@upstash/context7-mcp": patch------Answer an expired or revoked OAuth access token (`oat_…`) on the hosted HTTP transport with an HTTP 401 and a `WWW-Authenticate: Bearer error="invalid_token"` challenge, so MCP clients refresh the token instead of showing a tool error. The server checks the token against the Context7 API before serving the request, caches the verdict in memory per token hash for about a minute on each replica, and fails open when the check is unavailable. Set `MCP_OAUTH_TOKEN_VALIDATION=off` to disable the check. When the Context7 API still rejects an OAuth token on a tool call, the tool text now says the sign-in expired instead of describing API keys.diff --git a/.changeset/tough-ants-authenticate.md b/.changeset/tough-ants-authenticate.mddeleted file mode 100644index 142df532..00000000--- a/.changeset/tough-ants-authenticate.md+++ /dev/null@@ -1,5 +0,0 @@-----"@upstash/context7-mcp": minor------Require credentials on the HTTP `/mcp` endpoint by default. Set `MCP_AUTH_ENFORCEMENT=observe` to keep anonymous `/mcp` access and record privacy-safe authentication migration events; `/mcp/oauth` and Claude Code plugin requests keep their challenge in both modes. `/mcp/oauth` stays as a compatibility alias, each endpoint publishes its own OAuth protected-resource metadata, an empty or scheme-only `Authorization: Bearer` header counts as a missing credential, and CORS responses expose `WWW-Authenticate` and `MCP-Session-Id`.diff --git a/packages/mcp/CHANGELOG.md b/packages/mcp/CHANGELOG.mdindex 79fbc6df..370106de 100644--- a/packages/mcp/CHANGELOG.md+++ b/packages/mcp/CHANGELOG.md@@ -1,5 +1,15 @@# @upstash/context7-mcp+## 4.2.0++### Minor Changes++- 48eb9f0: Require credentials on the HTTP `/mcp` endpoint by default. Set `MCP_AUTH_ENFORCEMENT=observe` to keep anonymous `/mcp` access and record privacy-safe authentication migration events; `/mcp/oauth` and Claude Code plugin requests keep their challenge in both modes. `/mcp/oauth` stays as a compatibility alias, each endpoint publishes its own OAuth protected-resource metadata, an empty or scheme-only `Authorization: Bearer` header counts as a missing credential, and CORS responses expose `WWW-Authenticate` and `MCP-Session-Id`.++### Patch Changes++- 126379b: Answer an expired or revoked OAuth access token (`oat_…`) on the hosted HTTP transport with an HTTP 401 and a `WWW-Authenticate: Bearer error="invalid_token"` challenge, so MCP clients refresh the token instead of showing a tool error. The server checks the token against the Context7 API before serving the request, caches the verdict in memory per token hash for about a minute on each replica, and fails open when the check is unavailable. Set `MCP_OAUTH_TOKEN_VALIDATION=off` to disable the check. When the Context7 API still rejects an OAuth token on a tool call, the tool text now says the sign-in expired instead of describing API keys.+## 4.1.3### Patch Changesdiff --git a/packages/mcp/package.json b/packages/mcp/package.jsonindex c40eee5c..0ef9a70c 100644--- a/packages/mcp/package.json+++ b/packages/mcp/package.json@@ -1,6 +1,6 @@{"name": "@upstash/context7-mcp",- "version": "4.1.3",+ "version": "4.2.0","mcpName": "io.github.upstash/context7","description": "MCP server for Context7","scripts": {