modelcontextprotocol / modelcontextprotocol/servers
fetch fails without optional settings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Describe the bug
The docs clearly say:
fetch - Fetches a URL from the internet and extracts its contents as markdown.
url (string, required): URL to fetch
max_length (integer, optional): Maximum number of characters to return (default: 5000)
start_index (integer, optional): Start content from this character index (default: 0)
raw (boolean, optional): Get raw content without markdown conversion (default: false)
To Reproduce
Steps to reproduce the behavior:
- When I run fetch in LibreChat (Docker) + MCP/Fetch (Docker), I receive the attached errors
Expected behavior
It should disregard optional settings
another try:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the fetch request in the reported LibreChat and MCP/Fetch Docker setup, then inspect the attached errors and the fetch implementation. Confirm that a request with only the required URL succeeds when optional settings are omitted; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100