fetch - max_length customization

[jritsema]

Description

For the fetch MCP server, allows overriding of the default max_length argument using a MAX_LENGTH environment variable.

Server Details

• Server: fetch
• Changes to: tools

Motivation and Context

The default max_length of 5000 is sometimes too low and requires too many HTTP requests. It would be nice to be able to increase this value on a case by case basis.

How Has This Been Tested?

I tested this change with Amazon Q CLI.

Breaking Changes

No.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[jkwatson]

Yes! Would love this addition!

[olaservo]

@claude would you recommend merging this pull request?

[claude]

Claude encountered an error —— View job

Failed with exit code 128

---

I'll analyze this and get back to you.

[jritsema]

would you consider merging?

[domdomegg]

Thanks for the PR, and apologies for the long delay reviewing it. I think we want to reduce the number of possible configuration options for servers to reduce complexity, especially where there are alternative approaches to solving the same problem (e.g. setting your agent's system prompt to always set a particular max_length).

If this hard blocks some workflows, I'd be open to hearing more and reconsidering this. In the mean time you can workaround by running a fork locally.