[Bug]: plugin-based install is not documented and seems like doesn't support the API keys

[alexander-m-loris]

MCP Client

Claude Code

Context7 MCP Version

1.0.0 (as plugin)

Bug Description

First of all, there is no documentation about using upstash7 Claude Code plugins instead just pure MCP server.
It does work more or less, though, when a custom marketplace is added using upstash/contest7 address.

But there is no clear path how to use the API keys when Context7 is used via a plugin. Setting a CONTEXT7_API_KEY environment variable in ~/.zshrc doesn't help (maybe you need to put "env": {"CONTEXT7_API_KEY": "${CONTEXT7_API_KEY}"} inside the .mcp.json file of the plugin?). Whenever I use context7 as a plugin-installed, it works perfectly, but my dashboard on context7 shows no usage of the token plan.

Steps to Reproduce

1. In Claude Code, run /plugin, go to "Marketplaces", do "Add Marketplace". Use upstash/context7 address.
2. Inside /plugin command, in "Discover" section, search for context7. context7-marketplace will be found.
3. Add context7-marketplace plugin (assuming you have all the other local dependencies like npx).

Expected Behavior

There is a way to configure and pass the API key to the context7-marketplace plugin.

Actual Behavior

context7-marketplace plugin doesn't take the API key.

Error Messages / Logs

Transport Method

http

Node.js Version

No response

Operating System

macOS

Configuration

None (used as a plugin)

Additional Context

No response

[mattsilv]

I am hitting this too but found workaround via the compound-engineering Claude Code plugin, which bundles Context7 as an MCP server with no auth headers. The "Monthly quota exceeded" error is misleading — it's not a quota issue, it's unauthenticated requests hitting the anonymous tier.

Workaround: manually edit the plugin cache at ~/.claude/plugins/cache/every-marketplace/compound-engineering/<version>/.claude-plugin/plugin.json and add "headers": { "CONTEXT7_API_KEY": "your-key" } to the context7 MCP server config.

Restart Claude Code.

Filed a separate issue on compound-engineering to add API key passthrough: EveryInc/compound-engineering-plugin#153

UPDATE 2/22/26: my workaround doenst work, still having a lot of trouble with this issue

[fahreddinozcan]

Hey, thanks for raising this issue.

Claude Code's plugins doesn't allow plugins to pass API keys for MCPs while installing. So after installing the plugin, you'd always have to manually update the configuration file of claude plugin with your API key, and this would create too much friction for the users, that's why default plugin config uses anonymous one.

I will get in touch with claude code team about what we can do about this.

• If it's possible to pass dynamic values for headers while installing, this can be an option.
• The second and the most probable option is having the OAuth endpoint in the plugin, where users would have to manually authenticate after installing the plugin. I think this makes the most sense.
• I will check if environment variables can be utilized in the plugins.

Until we can resolve this issue, you can use the command below to add Context7 MCP to Claude Code without plugin

claude mcp add --header "CONTEXT7_API_KEY: YOUR_API_KEY" --transport http context7 https://mcp.context7.com/mcp

This is a critical friction and we'll make sure to prioritize this to resolve ASAP

[alexander-m-loris]

I will check if environment variables can be utilized in the plugins.

@fahreddinozcan , according to https://code.claude.com/docs/en/mcp#plugin-provided-mcp-servers, the syntax with "env" should work.