Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

fetch: ask for native markdown through Accept content negotiation

未关闭
#5,198 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
markdown, python
领域
api, backend

调研方向

Start with fetch_url in src/fetch/src/mcp_server_fetch/server.py and inspect how it builds the request and handles text/markdown responses; the issue notes prior PR #4052 as a prototype. Add markdown content negotiation and return markdown without the raw-content prefix. Done when markdown-capable sites receive a markdown Accept preference and markdown responses are returned as-is.

由索引模型根据 Issue 内容生成。

描述

enhancement server-fetch v2
Problem

fetch_url in src/fetch/src/mcp_server_fetch/server.py sends no Accept header, so a site that can serve markdown directly through content negotiation sends HTML, which is then simplified. When a site does return text/markdown, the tool labels it as content that "cannot be simplified to markdown" and prefixes the raw-content notice.

Proposal

Prefer text/markdown in the Accept header and return a markdown response as-is, without the raw-content prefix. This is an enhancement, so whether it fits the reference server is a maintainer's call.

Prior work
  • #4052 by @sidney

The PR(s) above targeted the pre-refactor code and are closed as part of the backlog triage in #4875; this issue is where the work continues, with the PR(s) as a prototype. Thank you to their authors.

主要语言
TypeScript
星标
91.6k
派生
11.9k
平均合并
6 小时 2 分钟
30 天内合并 PR
162

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/servers 的其他 Issue

查看 modelcontextprotocol/servers 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。