context7 agent grants: nine grants, two retractions, one silent no-op

PR #3547 makes a deliberate per-agent decision about context7 for every agent that lacked it. Ten agents had no record of whether the absence was a decision or an oversight, and five more advertised context7 in body prose while their frontmatter granted nothing. Filter the 15 agents on the left, then use the three panels below to see why a prose mention grants nothing, why "it connected" never proves a key is in use, and how the gate caught a change that would have been completely inert.

Agents granting context7
22
of 37 agent files
Prose-only (claims, grants nothing)
5
advertised but uncallable
Mentioning mcp__context7__
27
27 mention, 22 grant
State
before
as shipped on main

mcpServers: in agent frontmatter is metadata. Claude Code ignores it for plugin agents; the actual capability grant is the tools: list. Body prose is what the agent reads about itself, so a prose-only mention tells the agent it can fetch library docs when it cannot.

What the body prose said


          
What the frontmatter granted

        

        

      


      

        

          Counterintuitive and worth showing: tools/list returns HTTP 200 for any auth state against https://mcp.context7.com/mcp. So "it connected" never proves the key is in use. Only tools/call discriminates. Byte sizes below were measured on one query-docs call.
        

        

        

        

      


      

        

          An earlier revision of this change inserted the grant into the keywords: list instead of tools:. That is a completely silent no-op: the file mentions the tools, the agent still cannot call them. tests/agents/test-mcp-declared-vs-granted.sh caught it. Pick a key and a spelling to run the gate's two assertions.