Claude와 같은 LLM을 위해 API 키가 필요 없이 여러 언어 생태계에서 패키지 문서를 가져오는 MCP 서버입니다.
🌐 다양한 프로그래밍 언어 지원(JavaScript, Python, Java, .NET, Ruby, PHP, Rust, Go, Swift)
📦 이름이나 URL로 패키지에 대한 문서를 가져옵니다.
🔍 포괄적인 정보를 추출하기 위해 문서 사이트를 크롤링합니다.
📄 README, API 문서, 코드 예제 및 저장소 정보 추출
🧠 LLM 요약을 위한 구조화된 데이터 제공
💬 문서 분석을 위한 전문화된 프롬프트가 포함되어 있습니다.
🔑 API 키가 필요하지 않습니다 . Claude Desktop 및 Cursor IDE와 기본적으로 작동합니다.
Related MCP server: Context7 MCP
Claude Desktop → 설정 → 개발자를 엽니다.
"구성 편집"을 클릭하고 다음을 추가합니다.
지엑스피1
커서 IDE 열기 → 설정 → MCP -> 새 MCP 서버 추가
추가하다:
Name: docsFetcher
Command: npx -y @smithery/cli@latest run @cdugo/mcp-get-docs --config "{}"📋 Node.js 18 이상
git clone https://github.com/cdugo/package-documentation-mcp
cd package-documentation-mcp
npm install
npm run build설치가 완료되면 다음을 사용하여 서버를 로컬로 실행할 수 있습니다.
# From the project root directory
npm start파일 변경 시 자동 재시작 기능을 사용하여 개발하는 경우:
npm run dev서버는 기본 포트(보통 3000)에서 시작됩니다. 다음과 같은 출력이 표시됩니다.
🚀 DocsFetcher MCP Server running!
📋 Ready to fetch documentation사용자 지정 포트를 지정하려면:
PORT=8080 npm startfetch-url-docs : 🔗 특정 URL에서 문서 가져오기
fetch-package-docs : 📦 선택적 언어 사양을 사용하여 패키지에 대한 문서를 가져옵니다.
fetch-library-docs : 🧠 패키지 이름이나 URL을 사용하는 스마트 도구
fetch-multilingual-docs : 🌍 여러 언어 생태계에서 패키지에 대한 문서를 가져옵니다.
summarize-library-docs : 📚 포괄적인 도서관 요약을 작성하세요
explain-dependency-error : 🐛 종속성 오류 설명 생성
"Express.js란 무엇이고 어떻게 사용하나요?"
"React 라이브러리에 대해 알려주세요"
"Python에서 requests를 어떻게 사용하나요?"
"JavaScript에서 Lodash에 대한 문서를 보여주세요"
"Python의 pandas와 R의 data.table을 비교해보세요"
"@fetch-package-docs, packageName='express', language='javascript'"
"@fetch-package-docs, packageName='requests', language='python'"
"@fetch-multilingual-docs 패키지 이름='http' 및 언어=['javascript', 'python', 'rust']"
"@summarize-library-docs (라이브러리 이름='express')"
"@explain-dependency-error with packageName='dotenv'"
서버가 표시되지 않음 : ✅ 구성에서 절대 경로를 확인하세요
연결 오류 : 🔄 Claude Desktop 또는 Cursor IDE를 다시 시작하세요
가져오기 실패 : ⚠️ 일부 패키지에는 비표준 문서가 있을 수 있습니다.
언어 지원 : 🌐 언어가 작동하지 않으면 패키지의 직접 URL을 사용해 보세요.
MIT
| Name | Required | Description | Default |
|---|---|---|---|
| library | Yes | Name of the package or URL of the library documentation to fetch | |
| language | No | Programming language or repository type if providing a package name (e.g., javascript, python, java, dotnet) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| packageName | Yes | Name of the package to fetch documentation for | |
| languages | Yes | List of programming languages or repository types to check (e.g., javascript, python, java) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| packageName | Yes | Name of the package to fetch documentation for | |
| language | No | Programming language or repository type (e.g., javascript, python, java, dotnet) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL of the library documentation to fetch |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
fetch-library-docsfetch-multilingual-docsfetch-package-docsfetch-url-docsScored across 4 tools
The tools have overlapping purposes as they all fetch documentation, but the different targets (library, multilingual, package, URL) provide some distinction. However, without descriptions, it's unclear if 'library' and 'package' might overlap or if 'multilingual' is a subset of other categories, leading to potential confusion for agents.
All tool names follow a consistent verb_noun pattern with 'fetch-' prefix and hyphen-separated words (e.g., fetch-library-docs). There are no deviations in naming style, making the set predictable and easy to parse.
With 4 tools, the count is reasonable for a documentation fetching server, suggesting a focused scope. It's slightly thin but not inadequate, as each tool appears to target a specific documentation source type.
Inferring the domain as documentation retrieval, the surface lacks obvious operations like search, update, or delete, and there's no tool for general or unspecified docs fetching. The absence of descriptions makes it hard to assess gaps fully, but the limited set suggests significant coverage issues for broader documentation workflows.
@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…