Context7 MCP server tools enabled but never invoked in Continue.dev Agent mode

6 answers

• Best answerAgentArmor teamTeam2d ago

  Status: Fixed. The reporter confirmed on 2025-07-17 that the Context7 MCP server was working as expected in Continue; the thread does not identify which version introduced the fix.

  The setup used was the standard Context7 config:

  yamlCopy to clipboard

  mcpServers:
    - name: context7
      command: npx
      args:
        - "-y"
        - "@upstash/context7-mcp"
  

  In Agent mode, Continue showed the MCP tools as enabled, but when asked to "get the latest cal.com api docs. use context7," it never invoked the tool and instead returned generic advice about visiting GitHub or scraping websites. The user had tool access set to ask before accessing, but no approval prompt appeared.

  What was tried while debugging:

  • The pre-release version of Continue produced the same behavior.
  • Uninstalling the extension, deleting ~/.continue, and reinstalling fresh (latest and pre-release) did not fix it. The documented Continue Console log commands could not be found in that VS Code setup.
  • A maintainer asked the user to check the Continue Console logs for tool calls and to try the server in another MCP client. The user later reported the MCP ran in the Zed editor, confirming the server was functional in at least one other MCP client.

  General advice: if MCP tools are visible but never invoked, inspect Continue's logs for tool-call activity and test the same server in another MCP client to narrow down whether the problem is on the client side or the server side. Also note that MCP servers launched with npx run locally with your user permissions, so only add servers you trust.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam2d ago

  What @habsfanongit tried on GitHub (Worked)

  Reporter confirmed the Context7 MCP server was working as expected in Continue, without specifying which version or setting fixed it.

  Source: https://github.com/continuedev/continue/issues/5836#issuecomment-3082110972 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam2d ago

  What @habsfanongit tried on GitHub (Outcome unclear)

  User reported the Context7 MCP server ran in the Zed editor, showing the server could work outside Continue, but the thread does not connect this to a fix.

  Source: https://github.com/continuedev/continue/issues/5836#issuecomment-2974754843 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam2d ago

  What @habsfanongit tried on GitHub (Didn't work)

  Uninstalled the Continue extension, deleted ~/.continue, and reinstalled fresh with both latest and pre-release versions while restarting VS Code. Tools were still not invoked, and the documented Continue Console log settings could not be found.

  Source: https://github.com/continuedev/continue/issues/5836#issuecomment-2968712424 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam2d ago

  What @habsfanongit tried on GitHub (Didn't work)

  Tried the Continue pre-release version in Agent mode and still received the same generic response instead of a Context7 tool call.

  Source: https://github.com/continuedev/continue/issues/5836#issuecomment-2928509027 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam2d ago

  What @habsfanongit tried on GitHub (Didn't work)

  Configured Context7 with the documented mcpServers YAML, used Agent mode, and asked Continue for the latest Cal.com API docs via Context7. Continue ignored the tool and returned generic GitHub/web-scraping advice.

  Source: https://github.com/continuedev/continue/issues/5836 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport