docs(mcp): rewrite initialize.instructions + add CHANGELOG (round-3 P1s)#25
Merged
Merged
Conversation
The `instructions` field returned by `initialize` still said "all operations require a valid DevHelm API token", which contradicted the new tool schemas (api_token was removed from every tool's inputSchema in 0.7.0). LLMs reading the instructions field would infer they need to thread the token into tool args — the exact behavior the schema change was meant to prevent. Rewrite the trailing sentence to point at the transport-layer auth (`Authorization: Bearer …` for hosted, `DEVHELM_API_TOKEN` env for stdio) and explicitly state that tool schemas no longer accept tokens. Also add a CHANGELOG.md retroactively covering 0.6.0 → 0.8.2. The 0.6.0 → 0.7.0 cut renamed several required fields on tool schemas (`api_token` removed everywhere; `delete_*.id` → `*_id`; `list_*` no longer requires an empty `body` envelope) without any user- visible release notes — DevEx round 3 caught this drift. Going forward, every release should land with a corresponding stanza. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two round-3 DevEx P1 fixes for the MCP server:
`initialize.instructions` — the trailing sentence said "All operations require a valid DevHelm API token", contradicting the 0.7.0 schema change that removed `api_token` from every tool's `inputSchema`. LLMs reading the instructions string would still try to thread tokens into tool args. Rewritten to point at the transport-layer auth (`Authorization: Bearer ...` for hosted, `DEVHELM_API_TOKEN` env for stdio) and explicitly note that tool schemas no longer accept tokens.
`CHANGELOG.md` — written retroactively covering 0.6.0 → 0.8.2. The 0.6.0 → 0.7.0 cut renamed several required fields on tool schemas without user-visible release notes (DevEx round 3 caught this drift on a third-party client cached against 0.6.0). Going forward, every release should land with a corresponding stanza.
Test plan
Made with Cursor