#Installed context7 MCP

1 messages · Page 1 of 1 (latest)

hybrid glenBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

rocky mossBOT
#

That error is exactly what happens when your config contains an env-var placeholder like ${CONTEXT7_API_KEY} but the Gateway process can’t see that variable.

Key detail: env var substitution is strict — missing or empty env vars throw at config load time, which then cascades into weird follow-up errors like “plugin not found” because the config never fully validates/loads.
Docs: https://docs.openclaw.ai/gateway/configuration#env-var-substitution-in-config

Fix the missing CONTEXT7_API_KEY (macOS-friendly)

If you’re running the Gateway via the service/daemon (launchd), it usually does not inherit your terminal env. Easiest reliable fix:

  1. Put it in the global OpenClaw env file:
nano ~/.openclaw/.env

Add:

CONTEXT7_API_KEY=your_key_here
#

If it’s not listed, either:

  • install the plugin you intended (you’ll need the exact npm spec/path you were following), or
  • remove plugins.entries.mcp-integration from ~/.openclaw/openclaw.json.

Two things to paste (redact secrets)

  1. openclaw --version
  2. The plugins: { ... } section + the bit that references ${CONTEXT7_API_KEY} (keys redacted)

Then I can tell you whether you’re missing the plugin install, or just the env var.

bleak jolt
#

Im happy to just remove the plugin. Can you walk me through how to do that?

rocky mossBOT
# bleak jolt Im happy to just remove the plugin. Can you walk me through how to do that?

Yep. Since your config currently fails to load (because ${CONTEXT7_API_KEY} is missing), the safest way is to edit the config file directly and remove anything referencing that plugin/env var.

1) Stop the Gateway (optional but cleaner)

openclaw gateway stop

2) Open your config file

Default path on macOS:

nano ~/.openclaw/openclaw.json

(Use code ~/.openclaw/openclaw.json if you prefer VS Code.)

3) Remove the plugin references (this is the important part)

In the file, search for mcp-integration and delete the whole config block that mentions it, typically one (or more) of these:

#
  • plugins.entries.mcp-integration
  • plugins.allow / plugins.deny containing mcp-integration
  • any plugins.slots.* pointing at it
  • any plugins.load.paths entry you added for it (if present)

Also search for CONTEXT7_API_KEY and delete any string like:

Make sure the JSON5 stays valid (commas/braces).

4) Start it back up

openclaw gateway start
# or just:
openclaw gateway restart
#

5) Confirm it’s clean

openclaw doctor

If you paste just your plugins: { ... } section here (redact anything secret), I can tell you exactly which lines to delete so you don’t have to guess.