feat: support gemini-extension file #776
Conversation
gemini-extension.json
Outdated
| "-y", | ||
| "@upstash/context7-mcp", | ||
| "--api-key", | ||
| "YOUR_API_KEY" |
There was a problem hiding this comment.
I would recommend having the API key stored in a named environment variable and then instructing the user to set it in your README
There was a problem hiding this comment.
Hi @chrstnb, thanks for the review!
We already support an env variable called CONTEXT7_API_KEY
If a user has this in their env, would the mcp server be able to use it through the extension? If so, should I just remove this flag?
There was a problem hiding this comment.
I think the common pattern is to pass it in via the MCP definition (so like you're doing here but just with the CONTEXT7_API_KEY)
There was a problem hiding this comment.
I couldn't understand exactly, would the following work?
"--api-key",
"${CONTEXT7_API_KEY}"
If not could you share the config that you meant?
There was a problem hiding this comment.
Yes it should! And then just include in the README that that env var needs to be set
fixes ctx7-661