Repository navigation
chore(deps): update dependency @upstash/context7-mcp to v4.7.1 - #1240
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
🔒 MCP Security Scan Results✅ context7
Summary: Scanned 1 MCP server(s), all passed security checks. ✅ |
Contributor
🛡️ Grype Vulnerability Scan Results✅ No fixable High or Critical vulnerabilities found.
|
renovate
Bot
force-pushed
the
renovate/upstash-context7-mcp-4.x
branch
from
November 9, 2026 19:45
97b9795 to
224b953
Compare
renovate
Bot
force-pushed
the
renovate/upstash-context7-mcp-4.x
branch
from
November 12, 2026 12:40
224b953 to
254c332
Compare
renovate
Bot
force-pushed
the
renovate/upstash-context7-mcp-4.x
branch
from
November 16, 2026 15:00
254c332 to
0ffe273
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.4.4→4.7.1Release Notes
upstash/context7 (@upstash/context7-mcp)
v4.7.1Compare Source
Patch Changes
d80a84c: While a library's source is being indexed,ctx7 codeandquery-codenow say to call again for up to 3 minutes instead of at most twice: a first index usually takes 1 to 3 minutes. When the server message already gives this rule, the clients no longer repeat it.d53d88d: The research preview is now called experimental tools. Each signed-in user picks the experimental tools to list at Settings > MCP Tools in the Context7 dashboard, where "All experimental tools" also includes tools added later. The old flags (--research-preview,CONTEXT7_RESEARCH_PREVIEW=1,?research_preview=1) and the new--experimental,CONTEXT7_EXPERIMENTAL=1and?experimental=1still turn on every experimental tool.6e469e3: Update@modelcontextprotocol/nodeto 2.1.2 and@modelcontextprotocol/serverto 2.4.0, which bring in security fixes for@hono/node-server,honoand their dependencies.0718ba8:query-codeno longer greps a docs-stylequeryof several words, which matched nothing: it answers with a correction thatpatternis a regex matched within one line. A one-wordquery, or a phrase withfixed_strings, still works as the pattern.patternnow takes up to 1000 characters, like the server.c5e26f6: Describe query-code references as name matches, resolved only for libraries with a SCIP indexv4.7.0Compare Source
Minor Changes
d451493: Add apageargument to theget-upgrade-guideresearch preview tool: a long guide now comes in pages, each in full detail. Page 1 starts with everything needed to migrate (summary, before you start, codemods, breaking changes, deprecations), which continues on the next pages when it is longer than one page; behavior, config and API changes follow. A guide is served only once it is complete, so its pages always fit together; until then the tool says it is being prepared and when to call again, or that it could not be prepared.Patch Changes
f2daacb:get-upgrade-guideno longer tells the agent never to retry a guide that could not be prepared: the agent usesquery-docsnow and calls again only after the time the answer gives. Telemetry records an unavailable guide asunavailableand a page past the last asinvalid, instead ofnot_found; neither is shown to the agent as an error.v4.6.0Compare Source
Minor Changes
2111b92: Add thequery-codeMCP tool and thectx7 codecommand. They search and read a library's source code at the version its docs describe:grepwith ripgrep's options, plusdefinition,references,outline,readandlist.ctx7 librarymarks the libraries whose source is searchable, andresolve-library-iddoes so with the research preview on. The MCP tool is part of the research preview: it is listed only with--research-preview,CONTEXT7_RESEARCH_PREVIEW=1or?research_preview=1.7765f35: Add theget-upgrade-guideresearch preview tool: everything that changes between two versions of a library in one response, from the release notes and guides of every release in between and the public API diff of both versions.v4.5.1Compare Source
Patch Changes
fc65a5a: Keep the teamspace library-filter notice in resolve-library-id results when no libraries match.v4.5.0Compare Source
Minor Changes
7836c58: Research preview: asubmit-docs-feedbacktool sends feedback on the documentation thatquery-docsreturned: a score from 0 to 5, what was wrong, and a short comment. It is listed only with research preview on:--research-previeworCONTEXT7_RESEARCH_PREVIEW=1for stdio, and?research_preview=1on the MCP URL for the hosted server. With research preview on, the server instructions also ask the agent to send this feedback after it answers. API calls carryX-Context7-Research-Preview: 1, so Context7 can count how many people use the research preview.Patch Changes
5f41ea5: Record whether an OAuth client uses a Client ID Metadata Document or a registered client ID in MCP authentication telemetry.c964733: In stdio mode, an API key that is an unset variable placeholder (${CONTEXT7_API_KEY}or$CONTEXT7_API_KEY) now counts as no key: the server falls back toCONTEXT7_API_KEY, and when that is not usable either it logs one warning and runs without a key. Before, it sent the placeholder as the key and every tool call failed with 401. Gemini CLI passes the placeholder through when the user skips the Context7 extension's API key prompt. API keys are now trimmed, so a key with surrounding spaces is sent without them. The HTTP transport is unchanged.Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.