Skip to content

docs(everything): fix get-env description to match actual behavior#3991

Open
Will-hxw wants to merge 5 commits intomodelcontextprotocol:mainfrom
Will-hxw:fix/3986-get-env-docs
Open

docs(everything): fix get-env description to match actual behavior#3991
Will-hxw wants to merge 5 commits intomodelcontextprotocol:mainfrom
Will-hxw:fix/3986-get-env-docs

Conversation

@Will-hxw
Copy link
Copy Markdown

Summary

  • Fixed incorrect documentation for the get-env tool in features.md and structure.md
  • The tool requires a key parameter and returns only that specific environment variable, not all variables

Why

The documentation previously stated:

Returns all environment variables from the running process as pretty-printed JSON text

But the actual implementation (fixed in commit f2d1095) requires a key parameter and returns only that variable's value. The documentation was misleading.

Validation

  • Docs changes are accurate descriptions of current implementation
  • Only documentation files modified (no code changes)
  • Build not required for docs-only changes

Related

Addresses the documentation aspect of Issue #3986 (security concern was already fixed in code)

Will-hxw and others added 5 commits April 21, 2026 04:35
The resourceType argument in the resource-prompt was missing a
description of allowed values. Added "must be 'Text' or 'Blob'" to
help automated callers understand the expected input format.

Issue: modelcontextprotocol#3985

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Prevent leaking all process.env variables by requiring a specific key.
This addresses a security concern where the tool was returning the
entire environment without any parameter or filtering.

Issue: modelcontextprotocol#3986

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
When a client supports MCP roots, the server was unconditionally
replacing CLI-provided allowed directories with the client's roots.
This made it impossible to scope the server to a directory outside
the client's project root.

Now CLI arguments take precedence - only fetch and apply MCP roots
when no CLI directories were provided.

Fixes: modelcontextprotocol#3929

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The has_changes() function only considered .py and .ts files when
deciding whether to bump a package version. This caused packages
with only lockfile changes (e.g., uv.lock from dependabot) to be
skipped during release.

Now includes .lock files in the check so that any meaningful
change to a package triggers a version bump.

Fixes: modelcontextprotocol#3870

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The get-env tool requires a 'key' parameter and returns only the value
of that specific environment variable, not all environment variables as
the previous description stated.

Fixes the misleading documentation that described behavior that was
already fixed in commit f2d1095.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant