{
"canonical_name": "modelcontextprotocol/servers",
"compilation_id": "pack_900662d822a748a1b06553233ae5aedf",
"created_at": "2026-05-15T20:19:02.007446+00:00",
"created_by": "project-pack-compiler",
"feedback": {
"carrier_selection_notes": [
"viable_asset_types=mcp_config, recipe, host_instruction, eval, preflight",
"recommended_asset_types=mcp_config, recipe, host_instruction, eval, preflight"
],
"evidence_delta": {
"confirmed_claims": [
"identity_anchor_present",
"capability_and_host_targets_present",
"install_path_declared_or_better"
],
"missing_required_fields": [],
"must_verify_forwarded": [
"Run or inspect `npx -y @modelcontextprotocol/server-memory` in an isolated environment.",
"Confirm the project exposes the claimed capability to at least one target host."
],
"quickstart_execution_scope": "allowlisted_sandbox_smoke",
"sandbox_command": "npx -y @modelcontextprotocol/server-memory",
"sandbox_container_image": "node:22-slim",
"sandbox_execution_backend": "docker",
"sandbox_planner_decision": "deterministic_isolated_install",
"sandbox_validation_id": "sbx_86b8871ec3e8471abaab40e9ac04fe9f"
},
"feedback_event_type": "project_pack_compilation_feedback",
"learning_candidate_reasons": [],
"template_gaps": []
},
"identity": {
"canonical_id": "project_76326ae04ef28e5085469316723a893e",
"canonical_name": "modelcontextprotocol/servers",
"homepage_url": null,
"license": "unknown",
"repo_url": "https://github.com/modelcontextprotocol/servers",
"slug": "servers",
"source_packet_id": "phit_109744362e1e442e9582d8e5ff9242aa",
"source_validation_id": "dval_e719397ea4654b7d9aa9c05ded209583"
},
"merchandising": {
"best_for": "需要工具连接与集成能力，并使用 local_cli的用户",
"github_forks": 10649,
"github_stars": 85356,
"one_liner_en": "Model Context Protocol Servers",
"one_liner_zh": "Model Context Protocol Servers",
"primary_category": {
"category_id": "tool-integrations",
"confidence": "high",
"name_en": "Tool Integrations",
"name_zh": "工具连接与集成",
"reason": "curated popular coverage category matched project identity"
},
"target_user": "使用 local_cli 等宿主 AI 的用户",
"title_en": "servers",
"title_zh": "servers 能力包",
"visible_tags": [
{
"label_en": "MCP Tools",
"label_zh": "MCP 工具",
"source": "repo_evidence_project_characteristics",
"tag_id": "product_domain-mcp-tools",
"type": "product_domain"
},
{
"label_en": "Knowledge Base Q&A",
"label_zh": "知识库问答",
"source": "repo_evidence_project_characteristics",
"tag_id": "user_job-knowledge-base-q-a",
"type": "user_job"
},
{
"label_en": "Code Review",
"label_zh": "代码审查",
"source": "repo_evidence_project_characteristics",
"tag_id": "core_capability-code-review",
"type": "core_capability"
},
{
"label_en": "Node-based Workflow",
"label_zh": "节点式流程编排",
"source": "repo_evidence_project_characteristics",
"tag_id": "workflow_pattern-node-based-workflow",
"type": "workflow_pattern"
},
{
"label_en": "Evaluation Suite",
"label_zh": "评测体系",
"source": "repo_evidence_project_characteristics",
"tag_id": "selection_signal-evaluation-suite",
"type": "selection_signal"
}
]
},
"packet_id": "phit_109744362e1e442e9582d8e5ff9242aa",
"page_model": {
"artifacts": {
"artifact_slug": "servers",
"files": [
"PROJECT_PACK.json",
"QUICK_START.md",
"PROMPT_PREVIEW.md",
"HUMAN_MANUAL.md",
"AI_CONTEXT_PACK.md",
"BOUNDARY_RISK_CARD.md",
"PITFALL_LOG.md",
"REPO_INSPECTION.json",
"REPO_INSPECTION.md",
"CAPABILITY_CONTRACT.json",
"EVIDENCE_INDEX.json",
"CLAIM_GRAPH.json"
],
"required_files": [
"PROJECT_PACK.json",
"QUICK_START.md",
"PROMPT_PREVIEW.md",
"HUMAN_MANUAL.md",
"AI_CONTEXT_PACK.md",
"BOUNDARY_RISK_CARD.md",
"PITFALL_LOG.md",
"REPO_INSPECTION.json"
]
},
"detail": {
"capability_source": "Project Hit Packet + DownstreamValidationResult",
"commands": [
{
"command": "npx -y @modelcontextprotocol/server-memory",
"label": "Node.js / npx · 官方安装入口",
"source": "https://github.com/modelcontextprotocol/servers#readme",
"verified": true
}
],
"display_tags": [
"MCP 工具",
"知识库问答",
"代码审查",
"节点式流程编排",
"评测体系"
],
"eyebrow": "工具连接与集成",
"glance": [
{
"body": "判断自己是不是目标用户。",
"label": "最适合谁",
"value": "需要工具连接与集成能力，并使用 local_cli的用户"
},
{
"body": "先理解能力边界，再决定是否继续。",
"label": "核心价值",
"value": "Model Context Protocol Servers"
},
{
"body": "未完成验证前保持审慎。",
"label": "继续前",
"value": "publish to Doramagic.ai project surfaces"
}
],
"guardrail_source": "Boundary & Risk Card",
"guardrails": [
{
"body": "Prompt Preview 只展示流程，不证明项目已安装或运行。",
"label": "Check 1",
"value": "不要把试用当真实运行"
},
{
"body": "local_cli",
"label": "Check 2",
"value": "确认宿主兼容"
},
{
"body": "publish to Doramagic.ai project surfaces",
"label": "Check 3",
"value": "先隔离验证"
}
],
"mode": "mcp_config, recipe, host_instruction, eval, preflight",
"pitfall_log": {
"items": [
{
"body": "README/documentation is current enough for a first validation pass.",
"category": "能力坑",
"evidence": [
"capability.assumptions | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | README/documentation is current enough for a first validation pass."
],
"severity": "medium",
"suggested_check": "将假设转成下游验证清单。",
"title": "能力判断依赖假设",
"user_impact": "假设不成立时，用户拿不到承诺的能力。"
},
{
"body": "未记录 last_activity_observed。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | last_activity_observed missing"
],
"severity": "medium",
"suggested_check": "补 GitHub 最近 commit、release、issue/PR 响应信号。",
"title": "维护活跃度未知",
"user_impact": "新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。"
},
{
"body": "no_demo",
"category": "安全/权限坑",
"evidence": [
"downstream_validation.risk_items | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium"
],
"severity": "medium",
"suggested_check": "进入安全/权限治理复核队列。",
"title": "下游验证发现风险项",
"user_impact": "下游已经要求复核，不能在页面中弱化。"
},
{
"body": "no_demo",
"category": "安全/权限坑",
"evidence": [
"risks.scoring_risks | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium"
],
"severity": "medium",
"suggested_check": "把风险写入边界卡，并确认是否需要人工复核。",
"title": "存在评分风险",
"user_impact": "风险会影响是否适合普通用户安装。"
},
{
"body": "issue_or_pr_quality=unknown。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | issue_or_pr_quality=unknown"
],
"severity": "low",
"suggested_check": "抽样最近 issue/PR，判断是否长期无人处理。",
"title": "issue/PR 响应质量未知",
"user_impact": "用户无法判断遇到问题后是否有人维护。"
},
{
"body": "release_recency=unknown。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | release_recency=unknown"
],
"severity": "low",
"suggested_check": "确认最近 release/tag 和 README 安装命令是否一致。",
"title": "发布节奏不明确",
"user_impact": "安装命令和文档可能落后于代码，用户踩坑概率升高。"
}
],
"source": "ProjectPitfallLog + ProjectHitPacket + validation + community signals",
"summary": "发现 6 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：能力坑 - 能力判断依赖假设。",
"title": "踩坑日志"
},
"snapshot": {
"contributors": 1025,
"forks": 10649,
"license": "unknown",
"note": "站点快照，非实时质量证明；用于开工前背景判断。",
"stars": 85356
},
"source_url": "https://github.com/modelcontextprotocol/servers",
"steps": [
{
"body": "不安装项目，先体验能力节奏。",
"code": "preview",
"title": "先试 Prompt"
},
{
"body": "理解输入、输出、失败模式和边界。",
"code": "manual",
"title": "读说明书"
},
{
"body": "把上下文交给宿主 AI 继续工作。",
"code": "context",
"title": "带给 AI"
},
{
"body": "进入主力环境前先完成安装入口与风险边界验证。",
"code": "verify",
"title": "沙箱验证"
}
],
"subtitle": "Model Context Protocol Servers",
"title": "servers 能力包",
"trial_prompt": "# servers - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for modelcontextprotocol/servers.\n\nProject:\n- Name: servers\n- Repository: https://github.com/modelcontextprotocol/servers\n- Summary: Model Context Protocol Servers\n- Host target: local_cli\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: Model Context Protocol Servers\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Model Context Protocol Servers\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. repository-structure: Repository Structure. Produce one small intermediate artifact and wait for confirmation.\n2. quick-start: Quick Start Guide. Produce one small intermediate artifact and wait for confirmation.\n3. everything-server: Everything Server. Produce one small intermediate artifact and wait for confirmation.\n4. filesystem-server: Filesystem Server. Produce one small intermediate artifact and wait for confirmation.\n5. memory-server: Memory Server. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/modelcontextprotocol/servers\n- https://github.com/modelcontextprotocol/servers#readme\n- package.json\n- tsconfig.json\n- CLAUDE.md\n- src/everything/package.json\n- src/filesystem/package.json\n- src/fetch/pyproject.toml\n- README.md\n- src/memory/package.json\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n",
"voices": [
{
"body": "来源平台：github, reddit。github/github_issue: The filesystem server stopped working with the OpenAI Agent SDK.（https://github.com/modelcontextprotocol/servers/issues/3051）；github/github_issue: Filesystem extension: Frequent timeout or outright failures since claude（https://github.com/modelcontextprotocol/servers/issues/3281）；github/github_issue: filesystem MCP server doesn't support legal Windows pathnames in claude_（https://github.com/modelcontextprotocol/servers/issues/447）；github/github_issue: Latest release of @modelcontextprotocol/server-filesystem is not on npmj（https://github.com/modelcontextprotocol/servers/issues/4130）；github/github_issue: Filesystem server canonicalizes configured Windows mapped-drive paths to（https://github.com/modelcontextprotocol/servers/issues/4129）；github/github_issue: Add baselings-mcp — 42 DeFi tools for Base chain (swaps, reactor burns, （https://github.com/modelcontextprotocol/servers/issues/4127）；github/github_issue: confusing documentation（https://github.com/modelcontextprotocol/servers/issues/521）；github/github_issue: memory: safer persistence defaults, atomic writes, quotas, redaction, an（https://github.com/modelcontextprotocol/servers/issues/4117）；github/github_issue: puppeteer: update old MCP SDK and add browser-automation guardrails by d（https://github.com/modelcontextprotocol/servers/issues/4118）；github/github_issue: Reference implementation: self-evolving macOS MCP server (Swift, 71 tool（https://github.com/modelcontextprotocol/servers/issues/4126）；github/github_issue: Schema quality: missing property descriptions across official MCP server（https://github.com/modelcontextprotocol/servers/issues/3669）；reddit: A curated list of Model Context Protocol (MCP) servers : r/ClaudeAI（https://www.reddit.com/r/ClaudeAI/comments/1h2cnf1/a_curated_list_of_model_context_protocol_mcp/）。这些是项目级外部声音，不作为单独质量证明。",
"items": [
{
"kind": "github_issue",
"source": "github",
"title": "The filesystem server stopped working with the OpenAI Agent SDK.",
"url": "https://github.com/modelcontextprotocol/servers/issues/3051"
},
{
"kind": "github_issue",
"source": "github",
"title": "Filesystem extension: Frequent timeout or outright failures since claude",
"url": "https://github.com/modelcontextprotocol/servers/issues/3281"
},
{
"kind": "github_issue",
"source": "github",
"title": "filesystem MCP server doesn't support legal Windows pathnames in claude_",
"url": "https://github.com/modelcontextprotocol/servers/issues/447"
},
{
"kind": "github_issue",
"source": "github",
"title": "Latest release of @modelcontextprotocol/server-filesystem is not on npmj",
"url": "https://github.com/modelcontextprotocol/servers/issues/4130"
},
{
"kind": "github_issue",
"source": "github",
"title": "Filesystem server canonicalizes configured Windows mapped-drive paths to",
"url": "https://github.com/modelcontextprotocol/servers/issues/4129"
},
{
"kind": "github_issue",
"source": "github",
"title": "Add baselings-mcp — 42 DeFi tools for Base chain (swaps, reactor burns, ",
"url": "https://github.com/modelcontextprotocol/servers/issues/4127"
},
{
"kind": "github_issue",
"source": "github",
"title": "confusing documentation",
"url": "https://github.com/modelcontextprotocol/servers/issues/521"
},
{
"kind": "github_issue",
"source": "github",
"title": "memory: safer persistence defaults, atomic writes, quotas, redaction, an",
"url": "https://github.com/modelcontextprotocol/servers/issues/4117"
},
{
"kind": "github_issue",
"source": "github",
"title": "puppeteer: update old MCP SDK and add browser-automation guardrails by d",
"url": "https://github.com/modelcontextprotocol/servers/issues/4118"
},
{
"kind": "github_issue",
"source": "github",
"title": "Reference implementation: self-evolving macOS MCP server (Swift, 71 tool",
"url": "https://github.com/modelcontextprotocol/servers/issues/4126"
},
{
"kind": "github_issue",
"source": "github",
"title": "Schema quality: missing property descriptions across official MCP server",
"url": "https://github.com/modelcontextprotocol/servers/issues/3669"
},
{
"kind": "searxng_indexed",
"source": "reddit",
"title": "A curated list of Model Context Protocol (MCP) servers : r/ClaudeAI",
"url": "https://www.reddit.com/r/ClaudeAI/comments/1h2cnf1/a_curated_list_of_model_context_protocol_mcp/"
}
],
"status": "已收录 23 条来源",
"title": "社区讨论"
}
]
},
"homepage_card": {
"category": "工具连接与集成",
"desc": "Model Context Protocol Servers",
"effort": "安装已验证",
"forks": 10649,
"icon": "link",
"name": "servers 能力包",
"risk": "可发布",
"slug": "servers",
"stars": 85356,
"tags": [
"MCP 工具",
"知识库问答",
"代码审查",
"节点式流程编排",
"评测体系"
],
"thumb": "gray",
"type": "MCP 配置"
},
"manual": {
"markdown": "# https://github.com/modelcontextprotocol/servers 项目说明书\n\n生成时间：2026-05-15 19:59:58 UTC\n\n## 目录\n\n- [Home](#home)\n- [Repository Structure](#repository-structure)\n- [Quick Start Guide](#quick-start)\n- [Everything Server](#everything-server)\n- [Filesystem Server](#filesystem-server)\n- [Memory Server](#memory-server)\n- [Git Server](#git-server)\n- [Time Server](#time-server)\n- [Fetch Server](#fetch-server)\n- [Sequential Thinking Server](#sequential-thinking-server)\n\n\n\n## Home\n\n### 相关页面\n\n相关主题：[Repository Structure](#repository-structure), [Quick Start Guide](#quick-start)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n \n\n# Home\n\n## Overview\n\nThe **Model Context Protocol (MCP) Servers** repository is the official collection of reference implementations for MCP servers. MCP is a protocol that enables AI models to interact with external tools, resources, and data sources through a standardized interface.\n\nThis repository serves as a central hub for developing, documenting, and distributing MCP server implementations that can be integrated with AI assistants and development tools.\n\n资料来源：[CLAUDE.md:1]()\n\n## Repository Architecture\n\nThe repository follows a monorepo structure where each MCP server resides in its own directory under `src/`.\n\n```mermaid\ngraph TD\n A[Model Context Protocol Servers] --> B[fetch]\n A --> C[sequential-thinking]\n A --> D[everything]\n A --> E[filesystem]\n A --> F[time]\n A --> G[memory]\n \n H[Shared Infrastructure] --> A\n H --> I[CLAUDE.md Guidelines]\n H --> J[Contributing Standards]\n```\n\n## Available MCP Servers\n\n### Server Comparison Table\n\n| Server | Language | Primary Use Case | Transport |\n|--------|----------|------------------|-----------|\n| `fetch` | Python | HTTP content fetching | stdio |\n| `sequential-thinking` | Node.js | Chain-of-thought reasoning | stdio, SSE, HTTP |\n| `everything` | Node.js | Comprehensive tool suite | stdio, SSE, HTTP |\n| `filesystem` | Node.js | File system operations | stdio |\n| `time` | Python | Time/timezone utilities | stdio |\n| `memory` | Node.js | Knowledge graph storage | stdio |\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md), [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n\n### Fetch Server\n\nThe `fetch` server provides HTTP content retrieval capabilities with support for:\n\n- Web content fetching via tools\n- User-initiated requests\n- robots.txt compliance (configurable)\n- Custom user-agent headers\n- Proxy support\n\n**Installation Methods:**\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-50]()\n\n### Filesystem Server\n\nThe filesystem server exposes file system operations with security boundaries:\n\n- Read operations: read_file, read_media_file, read_multiple_files\n- Directory operations: list_directory, directory_tree, search_files\n- Write operations: create_directory, write_file, edit_file, move_file\n- All paths validated against allowed directories\n\n**File Operation Annotations:**\n\n| Tool | readOnlyHint | idempotentHint | destructiveHint |\n|------|--------------|----------------|-----------------|\n| `write_file` | false | true | true |\n| `edit_file` | false | false | true |\n| `move_file` | false | false | true |\n| `create_directory` | false | true | false |\n\n资料来源：[src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n\n### Memory Server\n\nThe memory server implements a knowledge graph for persistent entity storage:\n\n- **create_entities**: Create new entities with type classification\n- **create_relations**: Establish relationships between entities\n- **add_observations**: Append observations to existing entities\n- **delete_entities**: Remove entities and cascading relations\n- **delete_observations**: Remove specific observations\n\nStorage backend: JSONL file format (configurable via `MEMORY_FILE_PATH`)\n\n资料来源：[src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n\n### Time Server\n\nThe time server provides timezone-aware time utilities:\n\n- Get current time in any timezone\n- Convert times between timezones\n- Automatic system timezone detection\n- Configurable via `--local-timezone` argument\n\n资料来源：[src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n\n### Everything Server\n\nThe everything server aggregates multiple MCP capabilities into a single server. Supports multiple transport protocols:\n\n- stdio (default)\n- SSE (deprecated as of 2025-03-26)\n- Streamable HTTP\n\n资料来源：[src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n\n## Development Standards\n\n### TypeScript Servers\n\n| Aspect | Standard |\n|--------|----------|\n| Target | ES2022 |\n| Module | Node16 |\n| Type System | Strict mode |\n| Testing | vitest with @vitest/coverage-v8 |\n| Node Version | 22 |\n\n**Code Style Guidelines:**\n\n- ES modules with `.js` extension in import paths\n- Zod schemas for tool input validation\n- 2-space indentation, trailing commas in multi-line objects\n- camelCase for variables/functions, PascalCase for types/classes\n- kebab-case for file names and registered tools/prompts/resources\n- Verb-first tool names (e.g., `get-file-info`)\n\n资料来源：[CLAUDE.md:5-15]()\n\n### Python Servers\n\n| Aspect | Standard |\n|--------|----------|\n| Build System | hatchling (uv build) |\n| Package Manager | uv (not pip) |\n| Python Version | >= 3.10 |\n| Type Checking | pyright |\n| Linting | ruff |\n\n**Development Commands:**\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\nuv run pytest\nuv run pyright\nuv run ruff check .\n```\n\n资料来源：[CLAUDE.md:16-26]()\n\n## Contributing\n\n### Accepted Contributions\n\n- Bug fixes\n- Usability improvements\n- Enhancements demonstrating MCP protocol features (Resources, Prompts, Roots)\n\n### Testing Requirements\n\nAll new functionality requires corresponding tests under `tests/` or `test/` directories.\n\n### Code Review\n\n- Pull requests welcome\n- CI enforces type checking and linting standards\n\n资料来源：[CLAUDE.md:27-35]()\n\n## Client Integration\n\n### Claude Desktop\n\nAdd server configurations to `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-something\"]\n }\n }\n}\n```\n\n### VS Code\n\nOne-click installation buttons available in each server's README for quick setup.\n\n### Zed\n\nConfiguration via `settings.json` using the `context_servers` array format.\n\n### Docker Installation\n\nAll servers support Docker deployment:\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/server-name\"]\n }\n }\n}\n```\n\n## Debugging\n\nUse the MCP Inspector for debugging:\n\n```bash\n# For uvx installations\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n\n# For local development\ncd path/to/servers/src/\nnpx @modelcontextprotocol/inspector uv run mcp-server-\n```\n\n资料来源：[src/fetch/README.md:1]()\n\n## License\n\nAll MCP servers in this repository are licensed under the MIT License, permitting free use, modification, and distribution subject to MIT License terms.\n\n---\n\n\n\n## Repository Structure\n\n### 相关页面\n\n相关主题：[Home](#home), [Quick Start Guide](#quick-start)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [package.json](https://github.com/modelcontextprotocol/servers/blob/main/package.json)\n- [tsconfig.json](https://github.com/modelcontextprotocol/servers/blob/main/tsconfig.json)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [src/everything/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/package.json)\n- [src/filesystem/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/package.json)\n- [src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n \n\n# Repository Structure\n\n## Overview\n\nThe [modelcontextprotocol/servers](https://github.com/modelcontextprotocol/servers) repository is a monorepo containing implementations of Model Context Protocol (MCP) servers. MCP is a protocol that enables AI models to interact with external tools, resources, and data sources. The repository houses multiple independent server implementations, each providing different capabilities such as filesystem access, web fetching, time utilities, and more.\n\nThe repository supports two primary implementation languages: **TypeScript/Node.js** and **Python**. This dual-language approach allows developers to choose their preferred runtime environment while maintaining feature parity across servers.\n\n## Directory Layout\n\nThe repository follows a modular structure where each MCP server lives in its own directory under the `src/` prefix.\n\n```\nservers/\n├── package.json # Root workspace configuration\n├── tsconfig.json # TypeScript configuration\n├── CLAUDE.md # Developer guidelines\n├── .github/ # GitHub workflows and PR templates\n├── src/\n│ ├── everything/ # Multi-feature demonstration server (TypeScript)\n│ ├── filesystem/ # File operations server (TypeScript)\n│ ├── fetch/ # Web content fetching server (Python)\n│ ├── memory/ # Knowledge graph memory server (TypeScript)\n│ ├── sequentialthinking/ # Chain-of-thought reasoning server (TypeScript)\n│ └── time/ # Time utilities server (Python)\n```\n\nEach server directory is self-contained with its own dependencies, build configuration, and documentation. The `src/everything` server serves as a reference implementation demonstrating all MCP capabilities including tools, resources, and prompts.\n\n## Technology Stack\n\n### TypeScript Servers\n\nTypeScript-based servers use the following technology stack:\n\n| Component | Technology | Version |\n|-----------|------------|---------|\n| Runtime | Node.js | 22 |\n| Language | TypeScript | ES2022 target |\n| Module System | Node16 | ES modules |\n| Type Checking | TypeScript strict mode | - |\n| Testing | Vitest | With @vitest/coverage-v8 |\n| SDK | @modelcontextprotocol/sdk | Latest |\n\n资料来源：[CLAUDE.md:2-8]()\n\nThe TypeScript servers share common patterns:\n\n- **ES Modules** with `.js` extension in import paths\n- **Strict TypeScript typing** for all functions and variables\n- **Zod schemas** for tool input validation\n- **2-space indentation** with trailing commas\n- Naming conventions: `camelCase` for variables/functions, `PascalCase` for types/classes, `kebab-case` for file names and registered tools/prompts/resources\n\n资料来源：[CLAUDE.md:24-30]()\n\n### Python Servers\n\nPython servers follow these specifications:\n\n| Component | Technology | Version |\n|-----------|------------|---------|\n| Runtime | Python | >= 3.10 |\n| Package Manager | uv | - |\n| Build System | hatchling | - |\n| Type Checking | pyright | Enforced in CI |\n| Linting | ruff | - |\n| Async | pytest-asyncio | For testing |\n\n资料来源：[CLAUDE.md:10-17]()\n\nPython server development commands follow a consistent pattern:\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\nuv run pytest # Run tests\nuv run pyright # Type checking\nuv run ruff check . # Linting\n```\n\n资料来源：[CLAUDE.md:12-16]()\n\n## Server Organization\n\n### Server Categories\n\nThe servers in this repository can be categorized by their implementation language and primary function:\n\n```mermaid\ngraph TD\n A[modelcontextprotocol/servers] --> B[TypeScript Servers]\n A --> C[Python Servers]\n \n B --> B1[everything]\n B --> B2[filesystem]\n B --> B3[memory]\n B --> B4[sequentialthinking]\n \n C --> C1[fetch]\n C --> C2[time]\n \n B1 --> B1a[Tools, Resources, Prompts]\n B2 --> B2a[File Operations]\n B3 --> B3a[Knowledge Graph]\n B4 --> B4a[Chain-of-Thought]\n C1 --> C1a[HTTP Fetching]\n C2 --> C2a[Timezone Operations]\n```\n\n### TypeScript Server Structure\n\nEach TypeScript server follows a consistent internal structure:\n\n```\nsrc//\n├── package.json\n├── tsconfig.json\n├── src/\n│ ├── index.ts # Main entry point\n│ ├── tools/ # Tool definitions\n│ ├── resources/ # Resource definitions\n│ ├── prompts/ # Prompt templates\n│ └── types/ # TypeScript type definitions\n├── docs/ # Server documentation\n└── tests/ # Test files\n```\n\n资料来源：[CLAUDE.md:35-37]()\n\nThe modular structure allows each server to register its capabilities through standardized functions:\n\n- `registerTools(server)` - Register MCP tools\n- `registerResources(server)` - Register MCP resources\n- `registerPrompts(server)` - Register MCP prompts\n\n资料来源：[CLAUDE.md:41-43]()\n\n### Python Server Structure\n\nPython servers use `pyproject.toml` for configuration and follow this pattern:\n\n```\nsrc//\n├── pyproject.toml # Project metadata and dependencies\n├── src/\n│ └── mcp_server_/ # Package directory\n│ ├── __init__.py\n│ └── server.py # Main server implementation\n└── tests/ # Test files\n```\n\n资料来源：[src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n\n## Configuration Patterns\n\n### Claude Desktop Integration\n\nServers can be integrated with Claude Desktop through JSON configuration. Each server provides installation instructions for different deployment methods.\n\n#### NPX Installation (Node.js servers)\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-\"]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:1-10]()\n\n#### UVX Installation (Python servers)\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-8]()\n\n#### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/\"]\n }\n }\n}\n```\n\n资料来源：[src/everything/README.md:1-10]()\n\n### Windows Configuration\n\nWindows environments require `cmd /c` wrapper for NPX commands:\n\n```json\n{\n \"servers\": {\n \"server-name\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-\"]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:1-20]()\n\nWindows users running Python servers via UVX may need to set environment variables to avoid timeout issues:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-15]()\n\n## Build and Development\n\n### Building Docker Images\n\nEach server can be containerized for deployment:\n\n```bash\ndocker build -t mcp/ -f src//Dockerfile .\n```\n\n资料来源：[src/filesystem/README.md:1-5]()\n\nFor the everything server:\n\n```bash\ndocker build -t mcp/everything -f src/everything/Dockerfile .\n```\n\n### Running from Source\n\n#### TypeScript Servers\n\n```bash\ncd src/\nnpm install\nnpm run start:streamableHttp # Streamable HTTP transport\nnpm run start:sse # SSE transport (deprecated)\n```\n\n资料来源：[src/everything/README.md:1-15]()\n\n#### Python Servers\n\n```bash\ncd src/\nuv sync --frozen --all-extras --dev\nuv run mcp-server-\n```\n\n### Debugging\n\nThe MCP Inspector tool can be used to debug servers:\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-\n```\n\n资料来源：[src/fetch/README.md:1-5]()\n\nFor local development:\n\n```bash\ncd path/to/servers/src/\nnpx @modelcontextprotocol/inspector uv run mcp-server-\n```\n\n## Contributing Patterns\n\n### Adding New Servers\n\nThe repository provides clear guidelines for extending the project:\n\n1. Create a new directory under `src//`\n2. Follow the established patterns for your implementation language\n3. Implement server capability registration functions\n4. Add comprehensive documentation\n\n### Key Contributing Guidelines\n\n| Aspect | Requirement |\n|--------|-------------|\n| Tool naming | Verb-first (e.g., `get-file-info`) |\n| Annotations | Set `readOnlyHint`, `idempotentHint`, `destructiveHint` per MCP spec |\n| Transport support | stdio (default), SSE (deprecated), Streamable HTTP |\n| Testing | Add tests using vitest (TS) or pytest (Python) |\n| Documentation | Include README.md with configuration examples |\n\n资料来源：[CLAUDE.md:41-46]()\n\n### Everything Server as Reference\n\nThe `src/everything` server demonstrates all MCP features and is an excellent reference for implementing new servers:\n\n- **Modular structure**: Separate modules for tools, resources, and prompts\n- **Registration pattern**: `registerX(server)` functions following SDK conventions\n- **Schema accuracy**: JSON Schema with descriptions and examples\n- **Extensibility**: Easy to add new modules following existing patterns\n\n资料来源：[src/everything/AGENTS.md:1-8]()\n\n## Transport Protocols\n\nThe repository supports multiple transport mechanisms for client-server communication:\n\n| Transport | Status | Description |\n|-----------|--------|-------------|\n| stdio | Default | Standard input/output communication |\n| Streamable HTTP | Current | Modern HTTP-based transport |\n| SSE | Deprecated | Server-Sent Events (deprecated 2025-03-26) |\n\n资料来源：[src/everything/README.md:1-20]()\n\nThe streamable HTTP transport is the recommended modern approach:\n\n```bash\nnpx @modelcontextprotocol/server- streamableHttp\n```\n\n## Tool Annotation System\n\nTypeScript servers use a standardized annotation system for tools to indicate their behavior to clients:\n\n| Annotation | Description | Values |\n|------------|-------------|--------|\n| `readOnlyHint` | Indicates if tool modifies state | `true`/`false` |\n| `idempotentHint` | Indicates if repeated calls produce same result | `true`/`false` |\n| `destructiveHint` | Indicates if tool deletes data | `true`/`false` |\n\n资料来源：[src/filesystem/README.md:1-30]()\n\nExample from the filesystem server:\n\n```typescript\nserver.registerTool(\n \"write_file\",\n {\n title: \"Write File\",\n inputSchema: {\n path: z.string(),\n content: z.string()\n },\n annotations: { readOnlyHint: false, idempotentHint: true, destructiveHint: true }\n },\n async (args) => { /* ... */ }\n);\n```\n\n资料来源：[src/filesystem/index.ts:1-25]()\n\n## Summary\n\nThe modelcontextprotocol/servers repository is organized as a well-structured monorepo that:\n\n- Contains multiple independent MCP server implementations under `src/`\n- Supports both TypeScript (Node.js 22) and Python (>=3.10) implementations\n- Follows consistent patterns for tool, resource, and prompt registration\n- Provides flexible deployment options (NPX, UVX, Docker)\n- Includes comprehensive documentation and debugging tools\n- Enforces type safety and testing through CI/CD\n\nThe `everything` server serves as the primary reference implementation, while other servers demonstrate specialized use cases like filesystem operations, web fetching, time utilities, and knowledge graph storage.\n\n---\n\n\n\n## Quick Start Guide\n\n### 相关页面\n\n相关主题：[Home](#home), [Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n- [src/sequentialthinking/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n \n\n# Quick Start Guide\n\nThis guide provides a comprehensive introduction to getting started with Model Context Protocol (MCP) servers. MCP servers are tools that extend the capabilities of AI assistants like Claude by providing access to external resources, file systems, databases, and more.\n\n## Overview\n\nThe MCP servers repository contains a collection of standalone servers that implement the Model Context Protocol. Each server provides specific functionality that can be integrated into MCP-compatible clients such as Claude Desktop, VS Code, and Zed.\n\n```mermaid\ngraph TD\n A[MCP Client] --> B[MCP Server]\n B --> C[Git Server]\n B --> D[Memory Server]\n B --> E[Filesystem Server]\n B --> F[Fetch Server]\n B --> G[Time Server]\n B --> H[Everything Server]\n B --> I[Sequential Thinking Server]\n```\n\n## Prerequisites\n\nBefore getting started with MCP servers, ensure your environment meets the following requirements.\n\n### System Requirements\n\n| Component | Requirement |\n|-----------|-------------|\n| Node.js | Version 22+ (for TypeScript servers) |\n| Python | Version 3.10+ (for Python servers) |\n| Docker | Latest stable version (optional) |\n| Package Manager | `uv` (recommended), `pip`, or `npm` |\n\n### Required Tools\n\nBased on the project guidelines, the following tools are required:\n\n- **For Python servers**: `uv` is the primary package manager 资料来源：[CLAUDE.md]()\n- **For Node.js servers**: `npm` or `npx` 资料来源：[README.md]()\n- **For containerized deployment**: Docker\n\n## Installation Methods\n\nMCP servers support multiple installation methods. Choose the one that best fits your environment.\n\n### Method 1: Using uvx (Recommended)\n\n`uvx` is the recommended installation method for Python-based servers. It provides easy setup and automatic dependency management 资料来源：[README.md]()\n\n```bash\n# Install a single server\nuvx mcp-server-git\n\n# Or install via npm for quick testing\nnpx @modelcontextprotocol/server-memory\n```\n\n### Method 2: Using pip\n\nFor Python servers, you can also use pip directly:\n\n```bash\n# Install the server package\npip install mcp-server-git\n\n# Run the server\npython -m mcp_server_git\n```\n\n### Method 3: Using Docker\n\nDocker provides isolation and consistency across different environments:\n\n```bash\n# Pull and run a pre-built image\ndocker run -i --rm mcp/filesystem\n\n# Build your own image\ndocker build -t mcp/filesystem -f src/filesystem/Dockerfile .\n```\n\n### Method 4: Using npx (Node.js)\n\nFor TypeScript/JavaScript servers:\n\n```bash\n# Run directly with npx\nnpx -y @modelcontextprotocol/server-memory\n```\n\n## Quick Start by Server Type\n\n### Git Server\n\nThe Git server provides tools for interacting with Git repositories.\n\n**Installation:**\n\n```bash\nuvx mcp-server-git\n```\n\n**Alternative with pip:**\n\n```bash\npip install mcp-server-git\npython -m mcp_server_git\n```\n\n资料来源：[README.md]()\n\n### Memory Server\n\nThe Memory server provides a knowledge graph storage system for maintaining persistent context across conversations 资料来源：[src/memory/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-memory\n```\n\n**Custom Configuration:**\n\n| Parameter | Description | Default |\n|-----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to the memory storage JSONL file | `memory.jsonl` |\n\n**Example Configuration:**\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-memory\"],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n### Filesystem Server\n\nThe Filesystem server provides secure file system access within allowed directories 资料来源：[src/filesystem/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir\n```\n\n**Available Tools:**\n\n| Tool | Read Only | Idempotent | Destructive | Notes |\n|------|-----------|------------|-------------|-------|\n| `read_file` | ✓ | – | – | Pure read |\n| `read_media_file` | ✓ | – | – | Pure read |\n| `read_multiple_files` | ✓ | – | – | Pure read |\n| `list_directory` | ✓ | – | – | Pure read |\n| `search_files` | ✓ | – | – | Pure read |\n| `write_file` | ✗ | ✓ | ✓ | Overwrites existing files |\n| `edit_file` | ✗ | ✗ | ✓ | May double-apply edits |\n| `move_file` | ✗ | ✗ | ✓ | Deletes source file |\n| `create_directory` | ✗ | ✓ | ✗ | Re-creating same dir is no-op |\n\n### Fetch Server\n\nThe Fetch server enables web content retrieval with proper robots.txt compliance 资料来源：[src/fetch/README.md]()\n\n**Installation:**\n\n```bash\nuvx mcp-server-fetch\n```\n\n**Customization Options:**\n\n| Argument | Description |\n|----------|-------------|\n| `--ignore-robots-txt` | Disable robots.txt compliance |\n| `--user-agent=` | Custom user-agent string |\n| `--proxy-url=` | Configure proxy server |\n\n**Default User-Agents:**\n\n```\nModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)\nModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)\n```\n\n### Time Server\n\nThe Time server provides timezone-aware time operations 资料来源：[src/time/README.md]()\n\n**Installation:**\n\n```bash\nuvx mcp-server-time\n```\n\n**Available Tools:**\n\n| Tool | Description |\n|------|-------------|\n| `get_current_time` | Get current time in a specified timezone |\n| `convert_time` | Convert time between timezones |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"get_current_time\",\n \"arguments\": {\n \"timezone\": \"Europe/Warsaw\"\n }\n}\n```\n\n### Sequential Thinking Server\n\nThe Sequential Thinking server provides structured reasoning capabilities 资料来源：[src/sequentialthinking/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-sequential-thinking\n```\n\n**Building from Source:**\n\n```bash\ndocker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .\n```\n\n### Everything Server\n\nThe Everything server aggregates multiple MCP server capabilities into a single endpoint 资料来源：[src/everything/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-everything\n```\n\n**Available Transport Options:**\n\n| Transport | Command |\n|-----------|---------|\n| stdio | `npx @modelcontextprotocol/server-everything stdio` |\n| SSE (deprecated) | `npx @modelcontextprotocol/server-everything sse` |\n| Streamable HTTP | `npx @modelcontextprotocol/server-everything streamableHttp` |\n\n## Client Configuration\n\n### Claude Desktop Configuration\n\nAdd server configurations to your Claude Desktop settings file 资料来源：[README.md]():\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-memory\"]\n },\n \"filesystem\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-filesystem\", \"${workspaceFolder}\"]\n }\n }\n}\n```\n\n### Windows Configuration\n\nOn Windows, wrap commands with `cmd /c`:\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-memory\"]\n }\n }\n}\n```\n\n### VS Code Configuration\n\nQuick installation buttons are available for VS Code and VS Code Insiders. Simply click the badge to install:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n### Zed Configuration\n\n```json\n\"context_servers\": {\n \"mcp-server-time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n}\n```\n\n## Development Setup\n\n### Setting Up Python Server Development\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\n\n# Run tests\nuv run pytest\n\n# Type checking\nuv run pyright\n\n# Linting\nuv run ruff check .\n```\n\n资料来源：[CLAUDE.md]()\n\n### Setting Up Node.js Server Development\n\n```bash\ncd src/\nnpm install\nnpm run build\n```\n\n**Testing:**\n\n```bash\nnpm test\n```\n\n## Troubleshooting\n\n### Common Issues\n\n#### Timeout Issues on Windows\n\nIf experiencing timeout issues on Windows, set the `PYTHONIOENCODING` environment variable:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n#### Character Encoding Issues\n\nFor servers that handle text content, ensure proper encoding by adding environment variables or command-line arguments as shown above.\n\n### Debugging with MCP Inspector\n\nUse the MCP inspector to debug server functionality:\n\n```bash\n# For uvx installations\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n\n# For local development\ncd path/to/servers/src/fetch\nnpx @modelcontextprotocol/inspector uv run mcp-server-fetch\n```\n\n## Architecture Overview\n\n```mermaid\ngraph LR\n A[Client Application] -->|MCP Protocol| B[Transport Layer]\n B -->|stdio/sse/http| C[Server Implementation]\n C -->|Tool Execution| D[External Resources]\n D -->|Results| C\n C -->|Formatted Response| B\n B -->|MCP Response| A\n```\n\n### Transport Methods\n\n| Transport | Use Case | Persistent Connection |\n|-----------|----------|----------------------|\n| stdio | CLI tools, Desktop apps | ✗ |\n| SSE | Real-time updates | ✓ |\n| Streamable HTTP | Web applications | ✓ |\n\n## Next Steps\n\n- Explore individual server documentation for advanced features\n- Review the [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md) for contribution guidelines\n- Check the main [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md) for the complete server list\n- Join the community to share your implementations and extensions\n\n---\n\n\n\n## Everything Server\n\n### 相关页面\n\n相关主题：[Filesystem Server](#filesystem-server), [Memory Server](#memory-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/everything/server/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/server/index.ts)\n- [src/everything/tools/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/tools/index.ts)\n- [src/everything/resources/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/resources/index.ts)\n- [src/everything/resources/session.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/resources/session.ts)\n- [src/everything/docs/features.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/features.md)\n- [src/everything/docs/architecture.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/architecture.md)\n- [src/everything/docs/extension.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/extension.md)\n \n\n# Everything Server\n\n## Overview\n\nThe Everything Server is a comprehensive Model Context Protocol (MCP) server implementation that provides a wide range of tools, resources, and prompts for AI-assisted interactions. It serves as a reference implementation demonstrating the full capabilities of the MCP specification. 资料来源：[src/everything/README.md]()\n\n### Purpose and Scope\n\nThe Everything Server is designed to:\n\n- Provide a complete example of MCP server implementation patterns\n- Offer practical tools for file system operations, memory management, and more\n- Demonstrate resource and prompt template capabilities\n- Support multiple transport mechanisms for different use cases\n- Serve as a foundation for building custom MCP servers 资料来源：[src/everything/AGENTS.md]()\n\n## Architecture\n\n### High-Level Architecture\n\n```mermaid\ngraph TD\n A[Client] -->|MCP Protocol| B[Transport Layer]\n B --> C[stdio]\n B --> D[SSE]\n B --> E[Streamable HTTP]\n C --> F[Server Core]\n D --> F\n E --> F\n F --> G[Tools Handler]\n F --> H[Resources Handler]\n F --> I[Prompts Handler]\n G --> J[File System Tools]\n G --> K[Memory Tools]\n G --> L[Utility Tools]\n H --> M[Static Resources]\n H --> N[Dynamic Resources]\n I --> O[Prompt Templates]\n```\n\n### Module Structure\n\nThe server is organized into distinct modules following a clear separation of concerns: 资料来源：[src/everything/docs/architecture.md]()\n\n| Module | Purpose | Key Files |\n|--------|---------|-----------|\n| **server** | Core server implementation and transport handling | `server/index.ts` |\n| **tools** | Tool definitions and handlers | `tools/index.ts`, `tools/*.ts` |\n| **resources** | Resource registration and management | `resources/index.ts`, `resources/session.ts` |\n| **prompts** | Prompt templates | `prompts/index.ts` |\n\n### Component Hierarchy\n\n```mermaid\ngraph TD\n A[McpServer Instance] --> B[Tools Registry]\n A --> C[Resources Registry]\n A --> D[Prompts Registry]\n B --> E[Tool Handlers]\n C --> F[Resource Providers]\n D --> G[Prompt Definitions]\n E --> H[File Operations]\n E --> I[Memory Operations]\n E --> J[Utility Operations]\n```\n\n## Installation\n\n### Prerequisites\n\n- Node.js version 22 or higher\n- npm or npx for package management 资料来源：[CLAUDE.md]()\n\n### Installation Methods\n\n#### Global npm Installation\n\n```bash\nnpm install -g @modelcontextprotocol/server-everything@latest\n```\n\n#### Using npx (No Installation Required)\n\n```bash\nnpx @modelcontextprotocol/server-everything\n```\n\n#### Docker\n\n```bash\ndocker run -i --rm mcp/everything\n```\n\n#### Running from Source\n\n```bash\ncd src/everything\nnpm install\nnpm run start:streamableHttp\n```\n\n资料来源：[src/everything/README.md]()\n\n### Claude Desktop Configuration\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-everything\"]\n }\n }\n}\n```\n\n#### Windows Configuration\n\nOn Windows, use `cmd /c` for proper process handling:\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-everything\"]\n }\n }\n}\n```\n\n## Transport Options\n\nThe Everything Server supports multiple transport mechanisms for communication with MCP clients.\n\n### Supported Transports\n\n| Transport | Status | Description |\n|-----------|--------|-------------|\n| **stdio** | Default | Standard input/output transport for CLI integration |\n| **Streamable HTTP** | Recommended | Modern transport supporting streaming responses (recommended as of 2025-03-26) |\n| **SSE** | Deprecated | Server-Sent Events transport (deprecated as of 2025-03-26) |\n\n### Running with Different Transports\n\n```bash\n# Default (stdio)\nnpx @modelcontextprotocol/server-everything\n\n# Explicitly stdio\nnpx @modelcontextprotocol/server-everything stdio\n\n# SSE (deprecated)\nnpx @modelcontextprotocol/server-everything sse\n\n# Streamable HTTP (recommended)\nnpx @modelcontextprotocol/server-everything streamableHttp\n```\n\n资料来源：[src/everything/README.md]()\n\n## Features\n\n### Core Capabilities\n\nThe Everything Server provides a comprehensive set of features: 资料来源：[src/everything/docs/features.md]()\n\n- **Tool Orchestration**: Extensive set of tools for various operations\n- **Resource Management**: Static and dynamic resource provision\n- **Prompt Templates**: Reusable prompt definitions\n- **Session Resources**: Dynamic session-based resource creation\n- **Multi-Transport Support**: stdio, HTTP+SSE, and Streamable HTTP\n\n### Tool Categories\n\n| Category | Tools | Description |\n|----------|-------|-------------|\n| **File System** | read_file, write_file, edit_file, move_file, list_directory, etc. | Full file system operations within allowed directories |\n| **Memory** | create_entities, create_relations, add_observations, etc. | Knowledge graph operations for persistent memory |\n| **Time** | get_current_time, convert_timezone | Time and timezone utilities |\n| **Utility** | Echo, random, etc. | General purpose utilities |\n\n## Tools Reference\n\n### Tool Registration Pattern\n\nTools are registered using the MCP SDK with Zod schemas for input validation: 资料来源：[src/everything/tools/index.ts]()\n\n```typescript\nserver.registerTool(\n \"tool_name\",\n {\n title: \"Tool Title\",\n description: \"Tool description\",\n inputSchema: { /* Zod schema */ },\n outputSchema: { /* output schema */ },\n annotations: {\n readOnlyHint: boolean,\n idempotentHint: boolean,\n destructiveHint: boolean\n }\n },\n async (args) => {\n // Handler implementation\n }\n);\n```\n\n### Tool Annotations\n\nEach tool includes annotations describing its behavior: 资料来源：[src/filesystem/README.md]()\n\n| Annotation | Values | Description |\n|------------|--------|-------------|\n| `readOnlyHint` | `true/false` | Whether the tool only reads data |\n| `idempotentHint` | `true/false` | Whether repeated calls produce the same result |\n| `destructiveHint` | `true/false` | Whether the tool modifies or deletes data |\n\n## Resources\n\n### Resource Types\n\nThe Everything Server implements resources following the MCP specification: 资料来源：[src/everything/resources/index.ts]()\n\n```mermaid\ngraph LR\n A[Resources] --> B[Static Resources]\n A --> C[Dynamic Resources]\n A --> D[Session Resources]\n B --> E[Pre-registered at startup]\n C --> F[Generated on-demand]\n D --> G[Created per session]\n```\n\n### Session Resources\n\nSession resources are dynamically created and managed: 资料来源：[src/everything/resources/session.ts:1-65]()\n\n```typescript\nexport const registerSessionResource = (\n server: McpServer,\n resource: Resource,\n type: \"text\" | \"blob\",\n payload: string\n): ResourceLink => {\n // Prepare resource content based on type\n const resourceContent = type === \"text\"\n ? { uri: uri.toString(), mimeType, text: payload }\n : { uri: uri.toString(), mimeType, blob: payload };\n\n // Remove existing resource with same URI if present\n const existingResource = registeredResources.get(uri);\n if (existingResource) {\n existingResource.remove();\n registeredResources.delete(uri);\n }\n\n // Register the resource with the server\n const registeredResource = server.registerResource(\n name, uri,\n { mimeType, description, title, annotations, icons, _meta },\n async () => ({ contents: [resourceContent] })\n );\n\n registeredResources.set(uri, registeredResource);\n return { type: \"resource_link\", ...resource };\n};\n```\n\n## Extension Guide\n\n### Adding New Tools\n\nTo extend the Everything Server with new tools: 资料来源：[src/everything/docs/extension.md]()\n\n1. Create a new file in the `tools/` folder (naming, exports, and registration function)\n2. Export a `registerX(server)` function that registers new items with the MCP SDK\n3. Wire your new module into the central index (`tools/index.ts`)\n4. Ensure schemas are accurate JSON Schema with helpful descriptions and examples\n\n### Extension Pattern\n\n```typescript\n// tools/example-tool.ts\nimport { McpServer } from \"@modelcontextprotocol/sdk/server/mcp.js\";\n\nexport function registerExampleTool(server: McpServer): void {\n server.registerTool(\n \"example_tool\",\n {\n title: \"Example Tool\",\n description: \"An example tool demonstrating the extension pattern\",\n inputSchema: {\n param: z.string().describe(\"Example parameter\")\n },\n outputSchema: { result: z.string() }\n },\n async (args) => {\n // Implementation\n return { content: [{ type: \"text\", text: result }] };\n }\n );\n}\n```\n\n### Updating Documentation\n\nKeep the documentation in `src/everything/docs/` up to date when adding or modifying features. 资料来源：[src/everything/AGENTS.md]()\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Description | Default |\n|----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to memory storage JSONL file | `memory.jsonl` in server directory |\n\n### Claude Desktop Configuration Example\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-everything\"],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n## Development\n\n### Project Structure\n\n```\nsrc/everything/\n├── index.ts # Main entry point\n├── server/\n│ └── index.ts # Server configuration\n├── tools/\n│ ├── index.ts # Tool registry\n│ └── *.ts # Individual tool implementations\n├── resources/\n│ ├── index.ts # Resource registry\n│ └── session.ts # Session resource management\n├── prompts/\n│ └── index.ts # Prompt templates\n└── docs/\n ├── features.md # Feature documentation\n ├── architecture.md # Architecture details\n └── extension.md # Extension guide\n```\n\n### Build Requirements\n\n- **Runtime**: Node.js 22\n- **Target**: ES2022\n- **Module**: Node16\n- **Type Checking**: Strict TypeScript mode\n- **Testing**: vitest with @vitest/coverage-v8 资料来源：[CLAUDE.md]()\n\n### Code Style Guidelines\n\n#### TypeScript Standards\n\n- ES modules with `.js` extension in import paths\n- Strict TypeScript typing for all functions and variables\n- Zod schemas for tool input validation\n- 2-space indentation with trailing commas\n- camelCase for variables/functions, PascalCase for types/classes\n- kebab-case for file names and registered tools/prompts/resources\n- Verb-first tool names (e.g., `get-file-info`, not `file-info`) 资料来源：[CLAUDE.md]()\n\n## Troubleshooting\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| Transport timeout | Ensure proper transport configuration; use Streamable HTTP for better reliability |\n| Resource not found | Check resource URI and registration status |\n| Windows process handling | Use `cmd /c` wrapper for npx commands |\n\n### Debugging\n\nUse the MCP inspector for debugging:\n\n```bash\ncd src/everything\nnpx @modelcontextprotocol/inspector\n```\n\n## License\n\nThe Everything Server is licensed under the MIT License. You are free to use, modify, and distribute the software subject to the terms and conditions of the MIT License. 资料来源：[src/everything/README.md]()\n\n## See Also\n\n- [MCP Specification](https://modelcontextprotocol.io/specification)\n- [MCP Servers Repository](https://github.com/modelcontextprotocol/servers)\n- [MCP SDK Documentation](https://github.com/modelcontextprotocol/sdk)\n\n---\n\n\n\n## Filesystem Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server), [Git Server](#git-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/filesystem/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/package.json)\n- [src/filesystem/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/index.ts)\n- [src/filesystem/lib.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/lib.ts)\n- [src/filesystem/path-validation.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/path-validation.ts)\n- [src/filesystem/roots-utils.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/roots-utils.ts)\n- [src/filesystem/path-utils.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/path-utils.ts)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n \n\n# Filesystem Server\n\nThe Filesystem Server is an MCP (Model Context Protocol) server implementation that provides secure file system access capabilities to AI models and clients. It enables reading, writing, and managing files and directories within configurable sandboxed environments, with comprehensive security controls through path validation and access restrictions.\n\n## Overview\n\nThe Filesystem Server bridges AI assistants with the local file system by exposing a standardized set of tools that perform file operations. All operations are scoped to user-defined allowed directories, preventing unauthorized access to system files or sensitive locations.\n\n**Key Characteristics:**\n\n| Attribute | Value |\n|-----------|-------|\n| Transport | stdio (default), Streamable HTTP |\n| Language | TypeScript (Node.js) |\n| SDK | @modelcontextprotocol/sdk |\n| License | MIT |\n| Mount Point | `/projects` (Docker default) |\n\n资料来源：[src/filesystem/README.md:1-10]()\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Client] -->|MCP Protocol| B[Filesystem Server]\n B --> C[Tool Handlers]\n C --> D[Path Validation Layer]\n D --> E[Allowed Directories]\n D --> F[File System Operations]\n F --> G[read_text_file]\n F --> H[write_file]\n F --> I[create_directory]\n F --> J[move_file]\n F --> K[list_directory]\n F --> L[search_files]\n E --> M[Security Boundaries]\n```\n\n### Core Components\n\n| Component | File | Responsibility |\n|-----------|------|-----------------|\n| Server Entry | `index.ts` | MCP server initialization, tool registration |\n| Path Validation | `path-validation.ts` | Security checks, allowed directory enforcement |\n| File Operations | `lib.ts` | Core read/write operations implementation |\n| Path Utilities | `path-utils.ts` | Path manipulation and normalization |\n| Roots Utilities | `roots-utils.ts` | MCP roots protocol integration |\n\n资料来源：[src/filesystem/index.ts:1-50]()\n\n## Tool Specifications\n\n### Read Operations\n\nAll read tools have `readOnlyHint: true` annotation, indicating they do not modify system state.\n\n| Tool | Description | Input | Output |\n|------|-------------|-------|--------|\n| `read_text_file` | Read complete file contents as UTF-8 text | `path: string`, optional `head?: number`, `tail?: number` | `content: string` |\n| `read_media_file` | Read image/audio as base64 | `path: string` | `blob: string`, `mimeType: string` |\n| `read_multiple_files` | Read multiple files simultaneously | `paths: string[]` | Combined content with separators |\n| `get_file_info` | Retrieve file metadata | `path: string` | Size, timestamps, type |\n| `list_directory` | List directory contents | `path: string` | Files and subdirectories with [FILE]/[DIR] prefixes |\n| `list_directory_with_sizes` | List with file sizes | `path: string`, optional `sortBy: \"name\" \\| \"size\"` | Detailed listing with sizes |\n| `directory_tree` | Recursive directory structure | `path: string` | Hierarchical tree view |\n| `search_files` | Find files by pattern | `path: string`, `pattern: string` | Matching file paths |\n| `list_allowed_directories` | Show permitted paths | none | List of allowed directories |\n\n资料来源：[src/filesystem/README.md:15-30]()\n\n### Write Operations\n\n| Tool | readOnlyHint | idempotentHint | destructiveHint | Description |\n|------|--------------|----------------|-----------------|-------------|\n| `write_file` | false | true | true | Create or overwrite files |\n| `edit_file` | false | false | false | Selective edits with diff preview |\n| `create_directory` | false | true | false | Create directories (idempotent) |\n| `move_file` | false | false | true | Move/rename files |\n\n资料来源：[src/filesystem/README.md:32-40]()\n\n### Annotation Semantics\n\n```mermaid\ngraph LR\n A[readOnlyHint] --> B{true?}\n B -->|Yes| C[Read operations
No state changes]\n B -->|No| D[destructiveHint & idempotentHint
become meaningful]\n D --> E[idempotentHint: true
Re-running safe]\n D --> F[idempotentHint: false
May fail on retry]\n D --> G[destructiveHint: true
Cannot undo]\n```\n\n> **Note:** `idempotentHint` and `destructiveHint` are meaningful only when `readOnlyHint` is `false`, as defined by the MCP specification.\n\n资料来源：[src/filesystem/README.md:42-44]()\n\n## Security Model\n\nThe Filesystem Server implements multiple security layers to prevent unauthorized file system access.\n\n### Path Validation\n\n```mermaid\ngraph TD\n A[Incoming Path] --> B{Normalize Path}\n B --> C{Relative to allowed directory?}\n C -->|No| D[Reject with error]\n C -->|Yes| E{Symlink traversal safe?}\n E -->|No| D\n E -->|Yes| F[Allow operation]\n```\n\n**Validation Rules:**\n\n1. All paths are normalized before comparison\n2. Symbolic links are resolved and checked against allowed directories\n3. Attempting to escape allowed directories via `..` or symlinks is blocked\n4. Operations are rejected if the resolved path falls outside permitted boundaries\n\n资料来源：[src/filesystem/path-validation.ts:1-30]()\n\n### Allowed Directories Configuration\n\n| Deployment Method | Configuration |\n|-------------------|---------------|\n| Docker | Mount directories to `/projects` |\n| NPX | Pass directories as arguments |\n| Programmatic | Set allowed directories at initialization |\n\n**Docker Example:**\n```bash\ndocker run -i --rm \\\n --mount type=bind,src=/host/path,dst=/projects/path \\\n mcp/filesystem /projects\n```\n\n**NPX Example:**\n```bash\nnpx -y @modelcontextprotocol/server-filesystem \\\n /Users/username/Desktop \\\n /path/to/allowed/dir\n```\n\n资料来源：[src/filesystem/README.md:55-75]()\n\n## Installation Methods\n\n### Docker\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"--mount\", \"type=bind,src=${workspaceFolder},dst=/projects/workspace\",\n \"mcp/filesystem\",\n \"/projects\"\n ]\n }\n }\n}\n```\n\n### NPX (Unix/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-filesystem\",\n \"${workspaceFolder}\"\n ]\n }\n }\n}\n```\n\n### NPX (Windows)\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"cmd\",\n \"args\": [\n \"/c\",\n \"npx\",\n \"-y\",\n \"@modelcontextprotocol/server-filesystem\",\n \"${workspaceFolder}\"\n ]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:55-95]()\n\n## Tool Detailed Reference\n\n### read_text_file\n\nReads complete file contents as UTF-8 text regardless of file extension.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Absolute or relative path to file |\n| `head` | number | No | Return only first N lines |\n| `tail` | number | No | Return only last N lines |\n\n**Constraints:** Cannot specify both `head` and `tail` simultaneously.\n\n资料来源：[src/filesystem/README.md:98-110]()\n\n### read_media_file\n\nReads image or audio files and returns base64-encoded data with MIME type.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Path to media file |\n\n**Returns:**\n- `blob`: Base64-encoded file content\n- `mimeType`: Corresponding MIME type (e.g., `image/png`, `audio/mpeg`)\n\n资料来源：[src/filesystem/README.md:112-120]()\n\n### edit_file\n\nPerforms selective edits using pattern matching with indentation preservation.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | File to edit |\n| `edits` | array | Yes | List of edit operations |\n| `dryRun` | boolean | No | Preview without applying (default: false) |\n\n**Edit Operation Schema:**\n```typescript\n{\n oldText: string; // Text to search for (can be substring)\n newText: string; // Replacement text\n}\n```\n\n**Features:**\n- Line-based and multi-line content matching\n- Whitespace normalization with indentation preservation\n- Git-style diff output with context\n- Preview changes with dry run mode\n\n**Best Practice:** Always use `dryRun: true` first to preview changes before applying them.\n\n资料来源：[src/filesystem/README.md:132-150]()\n\n### move_file\n\nMoves or renames files and directories.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `source` | string | Yes | Source file path |\n| `destination` | string | Yes | Destination path |\n\n**Behavior:**\n- Fails if destination already exists\n- Deletes source file after successful move\n- `destructiveHint: true` - operation cannot be automatically undone\n\n资料来源：[src/filesystem/README.md:165-175]()\n\n### list_directory_with_sizes\n\nLists directory contents with detailed file size information.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Directory path to list |\n| `sortBy` | string | No | Sort by `\"name\"` or `\"size\"` (default: `\"name\"`) |\n\n**Returns:** Detailed listing including file sizes and summary statistics (total files, directories, combined size).\n\n资料来源：[src/filesystem/README.md:155-163]()\n\n## Building from Source\n\n### Prerequisites\n\n- Node.js 22+\n- npm or docker\n\n### Docker Build\n\n```bash\ndocker build -t mcp/filesystem -f src/filesystem/Dockerfile .\n```\n\n### Local Development\n\n```bash\ncd src/filesystem\nnpm install\nnpm run build\n```\n\n资料来源：[src/filesystem/README.md:45-50]()\n\n## MCP Protocol Integration\n\n### Resources\n\nThe server may expose allowed directories as MCP Resources with the `roots://` URI scheme.\n\n```mermaid\nsequenceDiagram\n participant Client\n participant Server\n participant FileSystem\n Client->>Server: List Roots\n Server->>Server: Check roots-utils\n Server-->>Client: Allowed directory list\n Client->>Server: Tool call (e.g., read_file)\n Server->>FileSystem: Operation\n FileSystem-->>Server: Result\n Server-->>Client: Tool response\n```\n\n资料来源：[src/filesystem/roots-utils.ts:1-25]()\n\n## License\n\nThe Filesystem Server is licensed under the **MIT License**. This permits free use, modification, and distribution subject to MIT License terms.\n\n资料来源：[src/filesystem/README.md:51-54]()\n\n---\n\n\n\n## Memory Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/memory/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/package.json)\n- [src/memory/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/index.ts)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n \n\n# Memory Server\n\nThe Memory Server is an MCP (Model Context Protocol) server implementation that provides persistent knowledge graph capabilities for AI assistants like Claude. It enables AI models to maintain long-term memory across conversations by storing and retrieving structured information about users, entities, relationships, and events.\n\n## Overview\n\nThe Memory Server implements a knowledge graph storage system that allows AI assistants to:\n\n- Store information about users and their characteristics\n- Maintain relationships between entities\n- Retrieve relevant context from previous interactions\n- Update memory dynamically during conversations\n\n资料来源：[src/memory/package.json:3]()\n\n```mermaid\ngraph TD\n A[Claude Conversation] --> B[Memory Server]\n B --> C[Knowledge Graph Storage]\n C --> D[JSONL File Storage]\n \n B --> E[Memory Retrieval]\n E --> F[Return Entities & Relations]\n \n B --> G[Memory Update]\n G --> H[Create/Update Entities]\n G --> I[Create Relations]\n I --> C\n```\n\n## Architecture\n\nThe Memory Server is built using the Model Context Protocol SDK and stores data in a JSONL (JSON Lines) format file. The server provides tools for managing a graph-based knowledge structure with entities and relations.\n\n资料来源：[src/memory/package.json:1-2]()\n\n### Core Components\n\n| Component | Description |\n|-----------|-------------|\n| Knowledge Graph | Graph-based storage for entities and relationships |\n| JSONL Storage | Persistent file storage in JSON Lines format |\n| MCP SDK Integration | Uses `@modelcontextprotocol/sdk` for MCP protocol support |\n| Memory API | Tools for CRUD operations on memory entities |\n\n## Installation\n\n### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"-v\",\n \"claude-memory:/app/dist\",\n \"--rm\",\n \"mcp/memory\"\n ]\n }\n }\n}\n```\n\n资料来源：[src/memory/README.md]()\n\n### NPX Installation (Unix/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n### NPX Installation (Windows)\n\nWindows requires using `cmd` with `/c` flag to launch `npx`:\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"cmd\",\n \"args\": [\n \"/c\",\n \"npx\",\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Description | Default |\n|----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to the memory storage JSONL file | `memory.jsonl` in server directory |\n\n### Custom Storage Path Example\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n资料来源：[src/memory/README.md]()\n\n## Memory Operations\n\nThe Memory Server supports the following core operations:\n\n### User Identification\n\nThe system assumes interaction with a default user and proactively identifies them if not already known:\n\n```\n- Assume interaction with default_user\n- Proactively identify user if not already done\n```\n\n### Memory Retrieval\n\nAt the start of each conversation, the system retrieves relevant information from the knowledge graph:\n\n```\n- Begin chat by saying \"Remembering...\"\n- Retrieve all relevant information from knowledge graph\n- Reference knowledge graph as \"memory\"\n```\n\n### Memory Categories\n\nDuring conversation, the system stores new information in these categories:\n\n| Category | Description | Examples |\n|----------|-------------|----------|\n| Basic Identity | Personal identifiers | Age, gender, location, job title, education |\n| Behaviors | User patterns | Interests, habits, preferences |\n| Preferences | Communication style | Preferred language, communication style |\n| Goals | Aspirations | Goals, targets, objectives |\n| Relationships | Connections | Personal and professional relationships (up to 3 degrees) |\n\n资料来源：[src/memory/README.md]()\n\n### Memory Update Process\n\nWhen new information is gathered during interaction:\n\n```mermaid\ngraph TD\n A[New Information Gathered] --> B{Is it recurring?}\n B -->|Organization| C[Create Entity for Organization]\n B -->|Person| D[Create Entity for Person]\n B -->|Event| E[Create Entity for Event]\n C --> F[Connect to Current Entities]\n D --> F\n E --> F\n F --> G[Create Relations]\n G --> H[Update Knowledge Graph]\n```\n\nThe update process:\n\n1. Creates entities for recurring organizations, people, and significant events\n2. Connects new entities to existing entities using relations\n3. Returns requested entities and their relations\n4. Silently skips non-existent nodes\n\n## Usage with Claude Desktop\n\n### Setup Configuration\n\nAdd the following to your `claude_desktop_config.json`:\n\n#### Docker Configuration\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"-v\", \"claude-memory:/app/dist\", \"--rm\", \"mcp/memory\"]\n }\n }\n}\n```\n\n#### NPX Configuration\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n### System Prompt Configuration\n\nFor optimal memory utilization, configure a custom prompt in the \"Custom Instructions\" field of your Claude.ai Project:\n\n```\nFollow these steps for each interaction:\n\n1. User Identification:\n - Assume interaction with default_user\n - Proactively identify if not already known\n\n2. Memory Retrieval:\n - Begin chat by saying \"Remembering...\"\n - Retrieve all relevant information from knowledge graph\n - Reference knowledge graph as \"memory\"\n\n3. Memory Categories:\n While conversing, be attentive to:\n a) Basic Identity (age, gender, location, job title, etc.)\n b) Behaviors (interests, habits, etc.)\n c) Preferences (communication style, preferred language)\n d) Goals (goals, targets, aspirations)\n e) Relationships (personal/professional up to 3 degrees)\n\n4. Memory Update:\n If new information gathered:\n a) Create entities for recurring organizations, people, events\n b) Connect them to current entities using relations\n```\n\n资料来源：[src/memory/README.md]()\n\n## Technical Specifications\n\n### Package Information\n\n| Property | Value |\n|----------|-------|\n| Package Name | `@modelcontextprotocol/server-memory` |\n| Version | 0.6.3 |\n| License | MIT License |\n| MCP Name | `io.github.modelcontextprotocol/server-memory` |\n| SDK Dependency | `@modelcontextprotocol/sdk: ^1.29.0` |\n\n资料来源：[src/memory/package.json:1-11]()\n\n### Build Configuration\n\n```json\n{\n \"scripts\": {\n \"build\": \"tsc && shx chmod +x dist/*.js\",\n \"prepare\": \"npm run build\",\n \"watch\": \"tsc --watch\",\n \"test\": \"vitest run --coverage\"\n }\n}\n```\n\n资料来源：[src/memory/package.json:18-22]()\n\n## VS Code Installation\n\nQuick installation is available through one-click buttons in the VS Code marketplace:\n\n- **NPX Installation**: For npm-based installations\n- **VS Code Insiders**: Separate button for Insiders version\n\nThese buttons provide streamlined configuration without manual JSON editing.\n\n资料来源：[src/memory/README.md]()\n\n## Data Model\n\n### Entity Structure\n\nEntities in the knowledge graph include:\n\n- **Organizations**: Recurring companies, teams, institutions\n- **People**: Users, contacts, individuals mentioned\n- **Events**: Significant occurrences, meetings, milestones\n\n### Relation Types\n\nRelations connect entities with semantic meaning:\n\n- Personal relationships (family, friends, colleagues)\n- Professional relationships (team members, stakeholders)\n- Temporal relationships (event connections)\n- Hierarchical relationships (org charts, reporting structures)\n\n### Return Values\n\n| Operation | Returns |\n|-----------|---------|\n| Retrieval | Requested entities and their relations |\n| Non-existent nodes | Silently skipped |\n\n## Development\n\n### Running from Source\n\n1. Clone the repository\n2. Navigate to `src/memory`\n3. Install dependencies\n4. Build using `npm run build`\n\n### Testing\n\n```bash\ncd src/memory\nnpm test\n```\n\n## Summary\n\nThe Memory Server provides a flexible, knowledge-graph-based memory system for AI assistants. It enables persistent storage of user information, entity relationships, and conversation context across multiple sessions. By integrating with the Model Context Protocol, it offers standardized MCP tool interfaces for memory operations while maintaining data in a portable JSONL format.\n\nKey benefits include:\n\n- **Persistent Memory**: Information persists across sessions\n- **Graph-based Relationships**: Rich entity connections\n- **Flexible Storage**: JSONL format allows easy backup and inspection\n- **MCP Standard**: Compatible with any MCP-compliant client\n\n---\n\n\n\n## Git Server\n\n### 相关页面\n\n相关主题：[Filesystem Server](#filesystem-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/git/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/git/pyproject.toml)\n- [src/git/src/mcp_server_git/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/git/src/mcp_server_git/server.py)\n- [src/git/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/git/README.md)\n\n**Note:** The Git Server source files (src/git/) are not included in the current repository context provided. The following documentation is based on the general MCP server patterns observed in other servers within this repository (fetch, time, filesystem, memory, etc.) and the CLAUDE.md contributing guidelines.\n\nFor accurate Git Server documentation, please provide the contents of the src/git/ directory files.\n \n\n# Git Server\n\n> **Documentation Status**: The Git Server (`src/git/`) source files were not included in the current repository context. This page provides general information based on MCP server patterns observed in this repository. For accurate implementation details, refer to the actual source files listed above.\n\n## Overview\n\nThe Git Server is a Model Context Protocol (MCP) server implementation that provides Git repository interaction capabilities to AI assistants and other MCP clients. Based on the project's architecture patterns, this server follows the same conventions as other MCP servers in the `modelcontextprotocol/servers` repository.\n\nThe server enables AI models to perform Git operations such as viewing history, examining commits, browsing branches, and analyzing repository state through standardized MCP tool interfaces.\n\n## Architecture\n\nBased on the patterns observed in other servers within this repository, the Git Server follows a modular architecture:\n\n```mermaid\ngraph TD\n A[MCP Client] -->|JSON-RPC| B[Git Server Entry Point]\n B --> C[Tool Handlers]\n C --> D[Git Operations Layer]\n D --> E[Local Git Repository]\n B --> F[Resource Providers]\n F --> G[Repository Resources]\n```\n\n## Server Structure\n\n### Directory Layout\n\nFollowing the repository conventions (per `CLAUDE.md`):\n\n```\nsrc/git/\n├── pyproject.toml # Python package configuration\n├── src/\n│ └── mcp_server_git/\n│ ├── __init__.py\n│ └── server.py # Main server implementation\n├── README.md # Server-specific documentation\n└── tests/ # Test suite\n```\n\n### Package Configuration\n\nThe server uses **hatchling** as its build system, consistent with other Python servers in this repository. Package configuration is defined in `pyproject.toml`.\n\nBased on patterns from other servers:\n- Package manager: **uv** (not pip) - 资料来源：[CLAUDE.md]()\n- Python version: **>= 3.10** (per-server `.python-version` file) - 资料来源：[CLAUDE.md]()\n- Type checking: **pyright** - 资料来源：[CLAUDE.md]()\n- Linting: **ruff** - 资料来源：[CLAUDE.md]()\n\n## Installation Methods\n\nBased on the standard MCP server installation patterns in this repository:\n\n### Using uvx (Recommended)\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-git\"]\n }\n }\n}\n```\n\n### Using pip\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_git\"]\n }\n }\n}\n```\n\n### Using Docker\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/git\"]\n }\n }\n}\n```\n\n## Configuration\n\n### Claude Desktop Configuration\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-git\"]\n }\n }\n}\n```\n\nOn Windows, wrap with `cmd /c`:\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"uvx\", \"mcp-server-git\"]\n }\n }\n}\n```\n\n## Development\n\n### Building\n\nDocker build:\n\n```bash\ndocker build -t mcp/git -f src/git/Dockerfile .\n```\n\n### Testing\n\n```bash\ncd src/git && uv sync --frozen --all-extras --dev\nuv run pytest\n```\n\n### Type Checking\n\n```bash\nuv run pyright\n```\n\n### Linting\n\n```bash\nuv run ruff check .\n```\n\n## Tool Interface\n\nBased on MCP server conventions, the Git Server exposes tools via the MCP protocol. Common Git operations likely include:\n\n| Tool Name | Purpose | Read Only |\n|-----------|---------|-----------|\n| `get-commit` | Retrieve commit details | Yes |\n| `list-branches` | List repository branches | Yes |\n| `get-file-history` | View file change history | Yes |\n| `get-diff` | Show changes between commits | Yes |\n| `list-tags` | List repository tags | Yes |\n| `get-repository-info` | Retrieve repository metadata | Yes |\n\n## Comparison with Other MCP Servers\n\nThe Git Server follows the same architectural patterns as other servers in this repository:\n\n| Aspect | Git Server | Fetch Server | Time Server | Memory Server |\n|--------|------------|--------------|-------------|---------------|\n| Language | Python | Python | Python | TypeScript |\n| Entry Point | `mcp_server_git` | `mcp_server_fetch` | `mcp_server_time` | `@modelcontextprotocol/server-memory` |\n| Transport | stdio | stdio | stdio | stdio |\n| Build System | hatchling | hatchling | hatchling | npm |\n| License | MIT | MIT | MIT | MIT |\n\n## Contributing\n\nContributions to the Git Server follow the general guidelines defined in the repository's `CLAUDE.md`:\n\n- **Accepted**: Bug fixes, usability improvements, enhancements demonstrating MCP protocol features\n- **Code Style**: Python typing with type hints enforced via pyright\n- **Testing**: pytest with proper async patterns\n- **Linting**: ruff for code style enforcement\n\nFor contribution guidelines, see: https://github.com/modelcontextprotocol/servers\n\n## License\n\nThis MCP server is licensed under the **MIT License**, consistent with other servers in the repository. Users are free to use, modify, and distribute the software subject to MIT License terms.\n\n---\n\n\n\n## Time Server\n\n### 相关页面\n\n相关主题：[Fetch Server](#fetch-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [src/time/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/time/pyproject.toml)\n- [src/time/src/mcp_server_time/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/time/src/mcp_server_time/server.py)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n \n\n# Time Server\n\nThe Time Server is a Python-based MCP (Model Context Protocol) server that provides timezone-aware time retrieval and conversion capabilities. It enables AI assistants and MCP clients to query current time in any timezone and perform time conversions between different time zones.\n\n## Overview\n\nThe Time Server exposes two primary tools that allow clients to:\n\n- Retrieve the current time for a specified timezone\n- Convert times between different timezones\n\nThe server automatically detects the system's timezone by default but allows customization through command-line arguments. It follows the MCP specification for tool definitions and responses.\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Client] -->|Tool Request| B[Time Server]\n B -->|Execute| C[get_current_time Tool]\n B -->|Execute| D[convert_time Tool]\n C -->|Query| E[System Timezone]\n C -->|Query| F[Specified Timezone]\n D -->|Calculate| G[Timezone Conversion]\n G --> H[Time Difference]\n B -->|JSON Response| A\n```\n\n## Tools\n\n### get_current_time\n\nRetrieves the current time for a specified timezone.\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `timezone` | string | Yes | IANA timezone identifier (e.g., \"Europe/Warsaw\", \"Asia/Tokyo\") |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"get_current_time\",\n \"arguments\": {\n \"timezone\": \"Europe/Warsaw\"\n }\n}\n```\n\n**Response:**\n\n```json\n{\n \"timezone\": \"Europe/Warsaw\",\n \"datetime\": \"2024-01-01T13:00:00+01:00\",\n \"is_dst\": false\n}\n```\n\n### convert_time\n\nConverts a time from one timezone to another.\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `source_timezone` | string | Yes | Source IANA timezone identifier |\n| `target_timezone` | string | Yes | Target IANA timezone identifier |\n| `time` | string | Yes | Time in HH:MM format |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"convert_time\",\n \"arguments\": {\n \"source_timezone\": \"America/New_York\",\n \"time\": \"16:30\",\n \"target_timezone\": \"Asia/Tokyo\"\n }\n}\n```\n\n**Response:**\n\n```json\n{\n \"source\": {\n \"timezone\": \"America/New_York\",\n \"datetime\": \"2024-01-01T12:30:00-05:00\",\n \"is_dst\": false\n },\n \"target\": {\n \"timezone\": \"Asia/Tokyo\",\n \"datetime\": \"2024-01-01T12:30:00+09:00\",\n \"is_dst\": false\n },\n \"time_difference\": \"+13.0h\"\n}\n```\n\n## Installation\n\nThe Time Server supports multiple installation methods.\n\n### Using uvx (Recommended)\n\n```bash\nuvx mcp-server-time\n```\n\n### Using pip\n\n```bash\npip install mcp-server-time\npython -m mcp_server_time\n```\n\n### Using Docker\n\n```bash\ncd src/time\ndocker build -t mcp/time .\ndocker run -i --rm mcp/time\n```\n\n## Configuration\n\n### Claude Desktop\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n**Using pip:**\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_time\"]\n }\n }\n}\n```\n\n### VS Code\n\nUse the one-click installation buttons available in the README, or configure manually:\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n### Zed Editor\n\n```json\n{\n \"context_servers\": {\n \"mcp-server-time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n### Docker Configuration\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"-e\", \"LOCAL_TIMEZONE\", \"mcp/time\"]\n }\n }\n}\n```\n\n## Customization\n\n### System Timezone Override\n\nBy default, the server automatically detects your system's timezone. Override this using the `--local-timezone` argument:\n\n```json\n{\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_time\", \"--local-timezone=America/New_York\"]\n}\n```\n\n### Environment Variable (Docker)\n\nPass the timezone via the `LOCAL_TIMEZONE` environment variable when using Docker:\n\n```bash\ndocker run -i --rm -e LOCAL_TIMEZONE=Europe/London mcp/time\n```\n\n## Debugging\n\nUse the MCP Inspector for debugging:\n\n**For uvx installations:**\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-time\n```\n\n**For local development:**\n\n```bash\ncd path/to/servers/src/time\nnpx @modelcontextprotocol/inspector uv run mcp-server-time\n```\n\n## Example Interactions\n\n### Query Current Time\n\n| Question | Description |\n|----------|-------------|\n| \"What time is it now?\" | Uses system timezone |\n| \"What time is it in Tokyo?\" | Queries Asia/Tokyo timezone |\n| \"What time is it in Europe/Warsaw?\" | Queries Europe/Warsaw timezone |\n\n### Time Conversion\n\n| Question | Description |\n|----------|-------------|\n| \"When it's 4 PM in New York, what time is it in London?\" | Cross-timezone conversion |\n| \"Convert 9:30 AM Tokyo time to New York time\" | Specific time conversion |\n\n## Data Model\n\n### Time Response Schema\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `timezone` | string | IANA timezone identifier |\n| `datetime` | string | ISO 8601 formatted datetime with timezone offset |\n| `is_dst` | boolean | Whether Daylight Saving Time is active |\n\n### Conversion Response Schema\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `source` | object | Source timezone info with datetime |\n| `target` | object | Target timezone info with datetime |\n| `time_difference` | string | Formatted difference (e.g., \"+13.0h\") |\n\n## License\n\nThe Time Server is licensed under the **MIT License**, allowing free use, modification, and distribution subject to the terms and conditions specified in the LICENSE file.\n\n## See Also\n\n- [Memory Server](src/memory/README.md) - Persistent memory storage\n- [Fetch Server](src/fetch/README.md) - HTTP fetch capabilities\n- [Filesystem Server](src/filesystem/README.md) - File operations\n- [MCP Specification](https://modelcontextprotocol.io/specification) - Protocol documentation\n\n---\n\n\n\n## Fetch Server\n\n### 相关页面\n\n相关主题：[Time Server](#time-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n- [src/fetch/src/mcp_server_fetch/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/src/mcp_server_fetch/server.py)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n \n\n# Fetch Server\n\nThe Fetch Server is a Model Context Protocol (MCP) server that provides web content fetching capabilities. It enables Large Language Models (LLMs) to retrieve and process content from web pages, converting HTML to markdown for easier consumption.\n\n## Overview\n\nThe Fetch Server acts as an intermediary between LLMs and web content, handling the complexities of HTTP requests, HTML parsing, and markdown conversion. This abstraction allows models to access web information without needing direct HTTP implementation capabilities.\n\n```mermaid\ngraph TD\n A[\"LLM / MCP Client\"] --> B[\"Fetch Server\"]\n B --> C[\"HTTP Request\"]\n C --> D[\"Web Server\"]\n D --> E[\"HTML Response\"]\n E --> B\n B --> F[\"Markdown Conversion\"]\n F --> A\n```\n\n### Key Capabilities\n\n| Capability | Description |\n|------------|-------------|\n| URL Fetching | Retrieve content from any publicly accessible URL |\n| Markdown Conversion | Transform HTML into clean, readable markdown |\n| Content Truncation | Limit response size with `max_length` parameter |\n| Chunked Reading | Use `start_index` to read content in portions |\n| Raw Content Access | Bypass markdown conversion when needed |\n\n> [!CAUTION]\n> This server can access local/internal IP addresses and may represent a security risk. Exercise caution when using this MCP server to ensure it does not expose any sensitive data.\n\n## Tools\n\n### fetch\n\nThe primary tool provided by the Fetch Server for retrieving web content.\n\n```typescript\n{\n name: \"fetch\",\n description: \"Fetches a URL from the internet and extracts its contents as markdown.\",\n inputSchema: {\n url: string, // required\n max_length?: number, // optional, default: 5000\n start_index?: number, // optional, default: 0\n raw?: boolean // optional, default: false\n }\n}\n```\n\n#### Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `url` | string | Yes | - | URL to fetch |\n| `max_length` | integer | No | 5000 | Maximum number of characters to return |\n| `start_index` | integer | No | 0 | Start content from this character index |\n| `raw` | boolean | No | false | Get raw content without markdown conversion |\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n#### Usage Example\n\n```json\n{\n \"name\": \"fetch\",\n \"arguments\": {\n \"url\": \"https://example.com/article\",\n \"max_length\": 10000,\n \"start_index\": 0\n }\n}\n```\n\n#### Response Format\n\n```json\n{\n \"content\": [\n {\n \"type\": \"text\",\n \"text\": \"# Article Title\\n\\nConverted markdown content...\"\n }\n ]\n}\n```\n\n### Chunked Reading\n\nThe fetch tool truncates responses by default. By using the `start_index` argument, you can specify where to start the content extraction, enabling models to read a webpage in chunks until they find the information they need.\n\n```mermaid\ngraph LR\n A[\"Initial Request
start_index=0\"] --> B[\"First Chunk\"]\n B --> C{\"Need More?\"}\n C -->|Yes| D[\"Request with
start_index=N\"]\n D --> B\n C -->|No| E[\"Complete\"]\n```\n\n## Installation\n\nThe Fetch Server supports multiple installation methods. Choose the one that best fits your environment.\n\n### Using uv (Recommended)\n\nWhen using [`uv`](https://docs.astral.sh/uv/), no specific installation is needed. Use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run the server:\n\n```bash\nuvx mcp-server-fetch\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n### Using pip\n\nAlternatively, install via pip:\n\n```bash\npip install mcp-server-fetch\n```\n\nAfter installation, run as a script:\n\n```bash\npython -m mcp_server_fetch\n```\n\n### Using Docker\n\n```bash\ndocker run -i --rm mcp/fetch\n```\n\n### Optional Dependency\n\nOptionally, install Node.js for a more robust HTML simplifier:\n\n```bash\n# This will cause the fetch server to use a different HTML simplifier\n# that is more robust for complex web pages\n```\n\n## Configuration\n\n### Claude.app Configuration\n\nAdd the following to your Claude settings:\n\n#### Using uvx\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n#### Using Docker\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/fetch\"]\n }\n }\n}\n```\n\n#### Using pip\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_fetch\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n### VS Code Configuration\n\nFor quick installation, use the one-click install buttons available in the README:\n\n- **Install with UV in VS Code** - Uses `uvx mcp-server-fetch`\n- **Install with UV in VS Code Insiders** - Uses `uvx mcp-server-fetch` (insiders version)\n- **Install with Docker in VS Code** - Uses `docker` command\n\n## Customization Options\n\n### robots.txt\n\nBy default, the server obeys a website's `robots.txt` file if the request came from the model (via a tool), but not if the request was user-initiated (via a prompt). This can be disabled:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--ignore-robots-txt\"]\n }\n }\n}\n```\n\n### User-Agent\n\nThe server uses different user-agents based on request origin:\n\n| Request Origin | User-Agent |\n|---------------|------------|\n| Model (via tool) | `ModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)` |\n| User (via prompt) | `ModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)` |\n\nCustomize the user-agent:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--user-agent=YourUserAgent\"]\n }\n }\n}\n```\n\n### Proxy Support\n\nConfigure the server to use a proxy:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--proxy-url=http://proxy.example.com:8080\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n## Windows Configuration\n\nIf experiencing timeout issues on Windows, set the `PYTHONIOENCODING` environment variable to ensure proper character encoding:\n\n### Windows with uvx\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n### Windows with pip\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n## Debugging\n\nUse the MCP inspector to debug the server:\n\n### For uvx installations\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n```\n\n### For development\n\n```bash\ncd path/to/servers/src/fetch\nnpx @modelcontextprotocol/inspector uv run mcp-server-fetch\n```\n\n## Prompts\n\nThe Fetch Server includes a prompt template:\n\n### fetch\n\n- **Purpose**: Fetch a URL and extract its contents as markdown\n- **Arguments**:\n - `url` (string, required): URL to fetch\n\n## Architecture\n\n```mermaid\ngraph TD\n subgraph \"Client Layer\"\n A[\"MCP Client
(Claude, VS Code, etc.)\"]\n end\n \n subgraph \"Fetch Server\"\n B[\"Request Handler\"]\n C[\"robots.txt Validator\"]\n D[\"User-Agent Manager\"]\n E[\"HTTP Client\"]\n F[\"HTML Parser\"]\n G[\"Markdown Converter\"]\n end\n \n subgraph \"External\"\n H[\"Target Web Server\"]\n end\n \n A --> B\n B --> C\n C --> D\n D --> E\n E --> H\n H --> E\n E --> F\n F --> G\n G --> A\n```\n\n## License\n\nThis MCP server is licensed under the MIT License. You are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License.\n\n## Contributing\n\nContributions are welcome to help expand and improve mcp-server-fetch. Whether you want to add new tools, enhance existing functionality, or improve documentation, your input is valuable.\n\nFor examples of other MCP servers and implementation patterns, see the [main MCP servers repository](https://github.com/modelcontextprotocol/servers).\n\nPull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements.\n\n---\n\n\n\n## Sequential Thinking Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/sequentialthinking/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n- [src/sequentialthinking/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n \n\n# Sequential Thinking Server\n\nThe Sequential Thinking Server is an MCP (Model Context Protocol) server implementation that provides a structured, step-by-step thinking tool for dynamic and reflective problem-solving. It enables AI assistants to break down complex problems into manageable steps, revise thinking as understanding deepens, and branch into alternative reasoning paths.\n\n## Overview\n\nThe server exposes a single powerful tool called `sequential_thinking` that facilitates detailed, iterative reasoning processes. Unlike one-shot responses, this tool allows models to maintain context over multiple thought steps, adjust their approach dynamically, and explore branching reasoning paths when needed.\n\n**Key Characteristics:**\n\n| Attribute | Value |\n|-----------|-------|\n| Package Name | `@modelcontextprotocol/server-sequential-thinking` |\n| Version | 0.6.2 |\n| License | MIT |\n| Transport | stdio (default), HTTP+SSE (deprecated), Streamable HTTP |\n| Runtime | Node.js / TypeScript |\n\n资料来源：[package.json:1-6](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## Features\n\nThe Sequential Thinking Server provides the following capabilities:\n\n- **Step-by-Step Decomposition** — Break complex problems into manageable thought steps\n- **Iterative Refinement** — Revise and refine thoughts as understanding deepens\n- **Branching Reasoning** — Fork into alternative paths of reasoning from any thought\n- **Dynamic Adjustment** — Adjust the total number of thoughts needed on the fly\n- **Hypothesis Verification** — Generate and verify solution hypotheses through structured thinking\n- **Thought Logging** — Optional logging of thought information for debugging and audit\n\n资料来源：[README.md:1-20](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Tool Specification\n\n### sequential_thinking\n\nThe primary tool provided by this server for structured problem-solving.\n\n**Input Schema:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `thought` | string | Yes | The current thinking step content |\n| `nextThoughtNeeded` | boolean | Yes | Whether another thought step is needed |\n| `thoughtNumber` | integer | Yes | Current thought number in the sequence |\n| `totalThoughts` | integer | Yes | Estimated total thoughts needed |\n| `isRevision` | boolean | No | Whether this revises a previous thought |\n| `revisesThought` | integer | No | Which thought number is being reconsidered |\n| `branchFromThought` | integer | No | Branching point thought number |\n| `branchId` | string | No | Unique identifier for this reasoning branch |\n| `needsMoreThoughts` | boolean | No | Indicates if more thoughts are required |\n\n资料来源：[README.md:35-53](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n**Tool Annotations:**\n\n| Annotation | Value | Description |\n|------------|-------|-------------|\n| `readOnlyHint` | false | This tool modifies thought state |\n| `idempotentHint` | false | Repeated calls have cumulative effect |\n| `destructiveHint` | false | Does not destroy external resources |\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Host Application] -->|stdio / HTTP| B[Sequential Thinking Server]\n B --> C[sequential_thinking Tool]\n C --> D[Thought State Management]\n D --> E[Optional Logging]\n \n F[Thought Input] -->|thought| C\n F -->|nextThoughtNeeded| C\n F -->|thoughtNumber| C\n F -->|totalThoughts| C\n \n C -->|revision| G[Revises Previous Thought]\n C -->|branch| H[Alternative Branch Created]\n C -->|continuation| I[Next Thought Prompt]\n```\n\n### Component Overview\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ MCP Host (Claude Desktop, VS Code) │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Sequential Thinking Server │\n│ ┌─────────────────────────────────────────────────────┐ │\n│ │ Tool Handler: sequential_thinking │ │\n│ │ - Validates input schema │ │\n│ │ - Processes thought parameters │ │\n│ │ - Manages thought state │ │\n│ └─────────────────────────────────────────────────────┘ │\n│ │ │\n│ ┌─────────────────────────────────────────────────────┐ │\n│ │ Logging Module (optional) │ │\n│ │ - Controlled by DISABLE_THOUGHT_LOGGING env var │ │\n│ └─────────────────────────────────────────────────────┘ │\n└─────────────────────────────────────────────────────────────┘\n```\n\n## Installation\n\n### Package Requirements\n\nThe server requires Node.js and is distributed as an npm package. It can also be run via Docker.\n\n资料来源：[package.json:18-22](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n### npx (Unix/Linux/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n### npx (Windows)\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n### Docker\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"--rm\", \"-i\", \"mcp/sequentialthinking\"]\n }\n }\n}\n```\n\n资料来源：[README.md:1-50](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Configuration\n\n### Claude Desktop Configuration\n\nAdd the following to `claude_desktop_config.json`:\n\n#### NPX Installation\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n#### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"sequentialthinking\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"--rm\", \"-i\", \"mcp/sequentialthinking\"]\n }\n }\n}\n```\n\n### VS Code Configuration\n\nUse the quick installation buttons in the README, or manually configure with:\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n资料来源：[README.md:90-130](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Environment Variables\n\n| Variable | Type | Default | Description |\n|----------|------|---------|-------------|\n| `DISABLE_THOUGHT_LOGGING` | boolean | `false` | Set to `true` to disable logging of thought information |\n\nWhen `DISABLE_THOUGHT_LOGGING` is set to `true`, the server will not log any thought-related information, providing a more private reasoning process.\n\n资料来源：[README.md:70-72](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Building from Source\n\n### Prerequisites\n\n- Node.js\n- npm\n- TypeScript\n\n### Build Commands\n\n```bash\n# Clone the repository\ngit clone https://github.com/modelcontextprotocol/servers.git\ncd servers/src/sequentialthinking\n\n# Install dependencies\nnpm install\n\n# Build the TypeScript project\nnpm run build\n```\n\nThe build process:\n1. Compiles TypeScript using `tsc`\n2. Sets executable permissions on compiled JavaScript files using `shx chmod +x`\n\n资料来源：[package.json:12-16](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n### Docker Build\n\n```bash\ndocker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .\n```\n\n## Usage Patterns\n\n### When to Use Sequential Thinking\n\nThe `sequential_thinking` tool is designed for:\n\n| Use Case | Description |\n|----------|-------------|\n| Problem Decomposition | Breaking down complex problems into steps |\n| Planning & Design | Creating plans with room for revision |\n| Multi-step Analysis | Analysis that might need course correction |\n| Uncertain Scope | Problems where full scope isn't clear initially |\n| Context Maintenance | Tasks needing to maintain context over multiple steps |\n| Information Filtering | Situations where irrelevant information needs filtering |\n\n资料来源：[README.md:55-68](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n### Verification Workflow\n\n```mermaid\ngraph LR\n A[Install Server] --> B[Restart MCP Host]\n B --> C[Verify Tool Appears]\n C --> D[Ask Complex Question]\n D --> E[Model Invokes Tool Multiple Times]\n E --> F[Observe Step-by-Step Reasoning]\n```\n\n**Manual Verification Steps:**\n\n1. Install the server in your MCP host\n2. Restart or reload the host so it reconnects to the server\n3. Confirm the `sequential_thinking` tool appears in the host's MCP tool list\n4. Ask the host to solve a non-trivial problem step-by-step\n5. Verify the host invokes the tool multiple times instead of returning a one-shot answer\n\n资料来源：[README.md:145-165](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n### Reasoning Branching Example\n\n```mermaid\ngraph TD\n A[Thought 1: Initial Problem] --> B[Thought 2: Approach A]\n B --> C[Thought 3: Explore Branch A1]\n C --> D{Decision Point}\n D -->|Revert| E[Thought 4: Revises Thought 2
branchId: branch-A]\n D -->|Continue| F[Thought 5: Continue on A1]\n E --> G[Thought 5: Alternative Path]\n```\n\nThe tool supports:\n- **Revisions** — Mark thoughts with `isRevision: true` and `revisesThought` to indicate corrections\n- **Branches** — Use `branchFromThought` and `branchId` to create alternative reasoning paths\n- **Dynamic Length** — Adjust `totalThoughts` as the reasoning progresses\n\n## Dependencies\n\n| Dependency | Version | Purpose |\n|------------|---------|---------|\n| `@modelcontextprotocol/sdk` | ^1.29.0 | MCP protocol implementation |\n| `chalk` | ^5.3.0 | Terminal string styling |\n| `yargs` | ^17.7.2 | Command-line argument parsing |\n\n**Dev Dependencies:**\n\n| Dependency | Purpose |\n|------------|---------|\n| `typescript` | TypeScript compiler |\n| `vitest` | Testing framework |\n| `@vitest/coverage-v8` | Code coverage |\n| `shx` | Shell command wrapper |\n| `@types/node`, `@types/yargs` | Type definitions |\n\n资料来源：[package.json:18-40](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## Testing\n\nThe project includes Vitest tests with coverage reporting:\n\n```bash\nnpm test\n```\n\nThis runs tests with coverage using `vitest run --coverage`.\n\n资料来源：[package.json:15](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## License\n\nThis MCP server is licensed under the **MIT License**. Users are free to use, modify, and distribute the software subject to the terms and conditions of the MIT License.\n\n资料来源：[README.md:80-83](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## See Also\n\n- [Model Context Protocol Specification](https://modelcontextprotocol.io)\n- [MCP Servers Repository](https://github.com/modelcontextprotocol/servers)\n- [Bug Tracker](https://github.com/modelcontextprotocol/servers/issues)\n\n---\n\n---\n\n## Doramagic 踩坑日志\n\n项目：modelcontextprotocol/servers\n\n摘要：发现 6 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：能力坑 - 能力判断依赖假设。\n\n## 1. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | README/documentation is current enough for a first validation pass.\n\n## 2. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | last_activity_observed missing\n\n## 3. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 4. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 5. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | issue_or_pr_quality=unknown\n\n## 6. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | release_recency=unknown\n\n\n",
"markdown_key": "servers",
"pages": "draft",
"source_refs": [
{
"evidence_id": "github_repo:890668799",
"kind": "repo",
"supports_claim_ids": [
"claim_identity",
"claim_distribution",
"claim_capability"
],
"url": "https://github.com/modelcontextprotocol/servers"
},
{
"evidence_id": "art_31a669ac5f81463883f2a87cec73c103",
"kind": "docs",
"supports_claim_ids": [
"claim_identity",
"claim_distribution",
"claim_capability"
],
"url": "https://github.com/modelcontextprotocol/servers#readme"
}
],
"summary": "DeepWiki/Human Wiki 完整输出，末尾追加 Discovery Agent 踩坑日志。",
"title": "servers 说明书",
"toc": [
"https://github.com/modelcontextprotocol/servers 项目说明书",
"目录",
"Home",
"Overview",
"Repository Architecture",
"Available MCP Servers",
"Development Standards",
"Contributing",
"Doramagic 踩坑日志"
]
}
},
"quality_gate": {
"blocking_gaps": [],
"category_confidence": "medium",
"compile_status": "ready_for_review",
"five_assets_present": true,
"install_sandbox_verified": true,
"missing_evidence": [],
"next_action": "publish to Doramagic.ai project surfaces",
"prompt_preview_boundary_ok": true,
"publish_status": "publishable",
"quick_start_verified": true,
"repo_clone_verified": true,
"repo_commit": "acedea0c24b3e20d7265f87b8b2afe2e0c6eb2f4",
"repo_inspection_error": null,
"repo_inspection_files": [
"package.json",
"README.md",
"src/time/pyproject.toml",
"src/time/README.md",
"src/memory/vitest.config.ts",
"src/memory/index.ts",
"src/memory/package.json",
"src/memory/README.md",
"src/memory/tsconfig.json",
"src/everything/AGENTS.md",
"src/everything/vitest.config.ts",
"src/everything/index.ts",
"src/everything/package.json",
"src/everything/README.md",
"src/everything/tsconfig.json",
"src/git/pyproject.toml",
"src/git/README.md",
"src/sequentialthinking/vitest.config.ts",
"src/sequentialthinking/index.ts",
"src/sequentialthinking/package.json",
"src/sequentialthinking/README.md",
"src/sequentialthinking/lib.ts",
"src/sequentialthinking/tsconfig.json",
"src/fetch/pyproject.toml",
"src/fetch/README.md",
"src/filesystem/vitest.config.ts",
"src/filesystem/index.ts",
"src/filesystem/path-validation.ts",
"src/filesystem/package.json",
"src/filesystem/README.md",
"src/filesystem/roots-utils.ts",
"src/filesystem/lib.ts",
"src/filesystem/tsconfig.json",
"src/filesystem/path-utils.ts",
"src/time/test/time_server_test.py",
"src/time/src/mcp_server_time/server.py",
"src/time/src/mcp_server_time/__init__.py",
"src/time/src/mcp_server_time/__main__.py",
"src/memory/__tests__/knowledge-graph.test.ts",
"src/memory/__tests__/file-path.test.ts"
],
"repo_inspection_verified": true,
"review_reasons": [],
"tag_count_ok": true,
"unsupported_claims": []
},
"schema_version": "0.1",
"user_assets": {
"ai_context_pack": {
"asset_id": "ai_context_pack",
"filename": "AI_CONTEXT_PACK.md",
"markdown": "# @modelcontextprotocol/servers - Doramagic AI Context Pack\n\n> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。\n\n## 充分原则\n\n- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。\n- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。\n\n## 给宿主 AI 的使用方式\n\n你正在读取 Doramagic 为 @modelcontextprotocol/servers 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。\n\n## Claim 消费规则\n\n- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。\n- **事实最低状态**：`supported`\n- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。\n- `weak`：只能作为低置信度线索，必须要求用户继续核实。\n- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。\n- `unverified`：不得作为事实使用，应明确说证据不足。\n- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。\n\n## 它最适合谁\n\n- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0002` supported 0.86\n\n## 它能做什么\n\n- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`CLAUDE.md`, `README.md` Claim：`clm_0001` supported 0.86\n\n## 怎么开始\n\n- `npx -y @modelcontextprotocol/server-memory` 证据：`README.md` Claim：`clm_0003` supported 0.86\n- `pip install mcp-server-git` 证据：`README.md` Claim：`clm_0004` supported 0.86\n- `npm install && npm run build` 证据：`CLAUDE.md` Claim：`clm_0005` supported 0.86\n\n## 继续前判断卡\n\n- **当前建议**：需要管理员/安全审批\n- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。\n\n### 30 秒判断\n\n- **现在怎么做**：需要管理员/安全审批\n- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装\n- **先别相信**：角色质量和任务匹配不能直接相信。\n- **继续会触碰**：角色选择偏差、命令执行、宿主 AI 配置\n\n### 现在可以相信\n\n- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0002` supported 0.86\n- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`CLAUDE.md`, `README.md` Claim：`clm_0001` supported 0.86\n- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0003` supported 0.86\n\n### 现在还不能相信\n\n- **角色质量和任务匹配不能直接相信。**（unverified）：角色库证明有很多角色，不证明每个角色都适合你的具体任务，也不证明角色能产生高质量结果。\n- **不能把角色文案当成真实执行能力。**（unverified）：安装前只能判断角色描述和任务画像是否匹配，不能证明它能在宿主 AI 里完成任务。\n- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。\n- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。\n- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`CLAUDE.md`\n- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。\n- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。\n- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。\n\n### 继续会触碰什么\n\n- **角色选择偏差**：用户对任务应该由哪个专家角色处理的判断。 原因：选错角色会让 AI 从错误专业视角回答，浪费时间或误导决策。\n- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`CLAUDE.md`, `README.md`\n- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`CLAUDE.md`\n- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`CLAUDE.md`, `README.md`\n- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`README.md`\n- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。\n\n### 最小安全下一步\n\n- **先跑 Prompt Preview**：先用交互式试用验证任务画像和角色匹配，不要先导入整套角色库。（适用：任何项目都适用，尤其是输出质量未知时。）\n- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）\n- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）\n- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）\n- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）\n\n### 退出方式\n\n- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。\n- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。\n- **保留原始角色选择记录**：如果输出偏题，可以回到任务画像阶段重新选择角色，而不是继续沿着错误角色推进。\n- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。\n- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。\n- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。\n\n## 哪些只能预览\n\n- 解释项目适合谁和能做什么\n- 基于项目文档演示典型对话流程\n- 帮助用户判断是否值得安装或继续研究\n\n## 哪些必须安装后验证\n\n- 真实安装 Skill、插件或 CLI\n- 执行脚本、修改本地文件或访问外部服务\n- 验证真实输出质量、性能和兼容性\n\n## 边界与风险判断卡\n\n- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0006` inferred 0.45\n- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`CLAUDE.md`, `README.md` Claim：`clm_0007` supported 0.86\n- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。\n- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。\n- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。\n\n## 开工前工作上下文\n\n### 加载顺序\n\n- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。\n- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。\n- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。\n- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。\n- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。\n\n### 任务路由\n\n- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`CLAUDE.md`, `README.md` Claim：`clm_0001` supported 0.86\n\n### 上下文规模\n\n- 文件总数：136\n- 重要文件覆盖：39/136\n- 证据索引条目：39\n- 角色 / Skill 条目：21\n\n### 证据不足时的处理\n\n- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。\n- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。\n- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。\n- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。\n\n## Prompt Recipes\n\n### 适配判断\n\n- 目标：判断这个项目是否适合用户当前任务。\n- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。\n\n```text\n请基于 @modelcontextprotocol/servers 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。\n```\n\n### 安装前体验\n\n- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。\n- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。\n\n```text\n请把 @modelcontextprotocol/servers 当作安装前体验资产，而不是已安装工具或真实运行环境。\n\n请严格输出四段：\n1. 先问我 3 个必要问题。\n2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。\n3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。\n4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。\n\n硬性边界：\n- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。\n- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。\n- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。\n- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。\n- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。\n- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。\n\n```\n\n### 角色 / Skill 选择\n\n- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。\n- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。\n\n```text\n请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。\n```\n\n### 风险预检\n\n- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。\n- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。\n\n```text\n请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。\n```\n\n### 宿主 AI 开工指令\n\n- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。\n- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。\n\n```text\n请基于 @modelcontextprotocol/servers 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。\n```\n\n\n## 角色 / Skill 索引\n\n- 共索引 21 个角色 / Skill / 项目文档条目。\n\n- **CLAUDE.md**（project_doc）：This file provides guidance to Claude Code when working with code in this repository. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CLAUDE.md`\n- **Model Context Protocol servers**（project_doc）：This repository is a collection of reference implementations for the Model Context Protocol https://modelcontextprotocol.io/ MCP , as well as references to community-built servers and additional resources. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`README.md`\n- **MCP \"Everything\" Server - Development Guidelines**（project_doc）：MCP \"Everything\" Server - Development Guidelines 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/AGENTS.md`\n- **Everything MCP Server**（project_doc）：Everything MCP Server Architecture docs/architecture.md Project Structure docs/structure.md Startup Process docs/startup.md Server Features docs/features.md Extension Points docs/extension.md How It Works docs/how-it-works.md 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/README.md`\n- **Fetch MCP Server**（project_doc）：A Model Context Protocol server that provides web content fetching capabilities. This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/fetch/README.md`\n- **Filesystem MCP Server**（project_doc）：Node.js server implementing Model Context Protocol MCP for filesystem operations. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/filesystem/README.md`\n- **mcp-server-git: A git MCP server**（project_doc）：A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/git/README.md`\n- **Knowledge Graph Memory Server**（project_doc）：A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/memory/README.md`\n- **Sequential Thinking MCP Server**（project_doc）：An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/sequentialthinking/README.md`\n- **Time MCP Server**（project_doc）：A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/time/README.md`\n- **Contributing to MCP Servers**（project_doc）：Thanks for your interest in contributing! Here's how you can help make this repo better. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CONTRIBUTING.md`\n- **Everything Server – Architecture**（project_doc）：Architecture Project Structure structure.md Startup Process startup.md Server Features features.md Extension Points extension.md How It Works how-it-works.md 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/architecture.md`\n- **Everything Server - Extension Points**（project_doc）：Everything Server - Extension Points 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/extension.md`\n- **Everything Server - Features**（project_doc）：Architecture architecture.md Project Structure structure.md Startup Process startup.md Server Features Extension Points extension.md How It Works how-it-works.md 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/features.md`\n- **Everything Server - How It Works**（project_doc）：Architecture architecture.md Project Structure structure.md Startup Process startup.md Server Features features.md Extension Points extension.md How It Works 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/how-it-works.md`\n- **Everything Server – Server Instructions**（project_doc）：Everything Server – Server Instructions 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/instructions.md`\n- **Everything Server - Startup Process**（project_doc）：Everything Server - Startup Process 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/startup.md`\n- **Everything Server - Project Structure**（project_doc）：Everything Server - Project Structure 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`src/everything/docs/structure.md`\n- **Description**（project_doc）：Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry https://github.com/modelcontextprotocol/registry to make it discoverable to the MCP ecosystem. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`.github/pull_request_template.md`\n- **Contributor Covenant Code of Conduct**（project_doc）：Contributor Covenant Code of Conduct 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CODE_OF_CONDUCT.md`\n- **Security Policy**（project_doc）：Thank you for helping keep the Model Context Protocol and its ecosystem secure. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`SECURITY.md`\n\n## 证据索引\n\n- 共索引 39 条证据。\n\n- **CLAUDE.md**（documentation）：This file provides guidance to Claude Code when working with code in this repository. 证据：`CLAUDE.md`\n- **Model Context Protocol servers**（documentation）：This repository is a collection of reference implementations for the Model Context Protocol https://modelcontextprotocol.io/ MCP , as well as references to community-built servers and additional resources. 证据：`README.md`\n- **MCP \"Everything\" Server - Development Guidelines**（documentation）：MCP \"Everything\" Server - Development Guidelines 证据：`src/everything/AGENTS.md`\n- **Everything MCP Server**（documentation）：Everything MCP Server Architecture docs/architecture.md Project Structure docs/structure.md Startup Process docs/startup.md Server Features docs/features.md Extension Points docs/extension.md How It Works docs/how-it-works.md 证据：`src/everything/README.md`\n- **Fetch MCP Server**（documentation）：A Model Context Protocol server that provides web content fetching capabilities. This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption. 证据：`src/fetch/README.md`\n- **Filesystem MCP Server**（documentation）：Node.js server implementing Model Context Protocol MCP for filesystem operations. 证据：`src/filesystem/README.md`\n- **mcp-server-git: A git MCP server**（documentation）：A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models. 证据：`src/git/README.md`\n- **Knowledge Graph Memory Server**（documentation）：A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats. 证据：`src/memory/README.md`\n- **Sequential Thinking MCP Server**（documentation）：An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process. 证据：`src/sequentialthinking/README.md`\n- **Time MCP Server**（documentation）：A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection. 证据：`src/time/README.md`\n- **Package**（package_manifest）：{ \"name\": \"@modelcontextprotocol/servers\", \"private\": true, \"version\": \"0.6.2\", \"description\": \"Model Context Protocol servers\", \"license\": \"SEE LICENSE IN LICENSE\", \"author\": \"Model Context Protocol a Series of LF Projects, LLC.\", \"homepage\": \"https://modelcontextprotocol.io\", \"bugs\": \"https://github.com/modelcontextprotocol/servers/issues\", \"type\": \"module\", \"workspaces\": \"src/ \" , \"files\": , \"scripts\": { \"build\": \"npm run build --workspaces\", \"watch\": \"npm run watch --workspaces\", \"publish-all\": \"npm publish --workspaces --access public\", \"link-all\": \"npm link --workspaces\" }, \"dependencies\": { \"@modelcontextprotocol/server-everything\": \" \", \"@modelcontextprotocol/server-memory\": \" \", \"@… 证据：`package.json`\n- **Contributing to MCP Servers**（documentation）：Thanks for your interest in contributing! Here's how you can help make this repo better. 证据：`CONTRIBUTING.md`\n- **Package**（package_manifest）：{ \"name\": \"@modelcontextprotocol/server-everything\", \"version\": \"2.0.0\", \"description\": \"MCP server that exercises all the features of the MCP protocol\", \"license\": \"SEE LICENSE IN LICENSE\", \"mcpName\": \"io.github.modelcontextprotocol/server-everything\", \"author\": \"Model Context Protocol a Series of LF Projects, LLC.\", \"homepage\": \"https://modelcontextprotocol.io\", \"bugs\": \"https://github.com/modelcontextprotocol/servers/issues\", \"repository\": { \"type\": \"git\", \"url\": \"https://github.com/modelcontextprotocol/servers.git\" }, \"type\": \"module\", \"bin\": { \"mcp-server-everything\": \"dist/index.js\" }, \"files\": \"dist\" , \"scripts\": { \"build\": \"tsc && shx cp -r docs dist/ && shx chmod +x dist/ .js\", \"pr… 证据：`src/everything/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@modelcontextprotocol/server-filesystem\", \"version\": \"0.6.3\", \"description\": \"MCP server for filesystem access\", \"license\": \"SEE LICENSE IN LICENSE\", \"mcpName\": \"io.github.modelcontextprotocol/server-filesystem\", \"author\": \"Model Context Protocol a Series of LF Projects, LLC.\", \"homepage\": \"https://modelcontextprotocol.io\", \"bugs\": \"https://github.com/modelcontextprotocol/servers/issues\", \"repository\": { \"type\": \"git\", \"url\": \"https://github.com/modelcontextprotocol/servers.git\" }, \"type\": \"module\", \"bin\": { \"mcp-server-filesystem\": \"dist/index.js\" }, \"files\": \"dist\" , \"scripts\": { \"build\": \"tsc && shx chmod +x dist/ .js\", \"prepare\": \"npm run build\", \"watch\": \"tsc --watch\", \"test… 证据：`src/filesystem/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@modelcontextprotocol/server-memory\", \"version\": \"0.6.3\", \"description\": \"MCP server for enabling memory for Claude through a knowledge graph\", \"license\": \"SEE LICENSE IN LICENSE\", \"mcpName\": \"io.github.modelcontextprotocol/server-memory\", \"author\": \"Model Context Protocol a Series of LF Projects, LLC.\", \"homepage\": \"https://modelcontextprotocol.io\", \"bugs\": \"https://github.com/modelcontextprotocol/servers/issues\", \"repository\": { \"type\": \"git\", \"url\": \"https://github.com/modelcontextprotocol/servers.git\" }, \"type\": \"module\", \"bin\": { \"mcp-server-memory\": \"dist/index.js\" }, \"files\": \"dist\" , \"scripts\": { \"build\": \"tsc && shx chmod +x dist/ .js\", \"prepare\": \"npm run build\", \"watch… 证据：`src/memory/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@modelcontextprotocol/server-sequential-thinking\", \"version\": \"0.6.2\", \"description\": \"MCP server for sequential thinking and problem solving\", \"license\": \"SEE LICENSE IN LICENSE\", \"mcpName\": \"io.github.modelcontextprotocol/server-sequential-thinking\", \"author\": \"Model Context Protocol a Series of LF Projects, LLC.\", \"homepage\": \"https://modelcontextprotocol.io\", \"bugs\": \"https://github.com/modelcontextprotocol/servers/issues\", \"repository\": { \"type\": \"git\", \"url\": \"https://github.com/modelcontextprotocol/servers.git\" }, \"type\": \"module\", \"bin\": { \"mcp-server-sequential-thinking\": \"dist/index.js\" }, \"files\": \"dist\" , \"scripts\": { \"build\": \"tsc && shx chmod +x dist/ .js\", \"prepare… 证据：`src/sequentialthinking/package.json`\n- **License**（source_file）：The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 \"Apache-2.0\" . All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions excluding specifications are licensed under CC-BY-4.0. 证据：`LICENSE`\n- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the \"Software\" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`src/fetch/LICENSE`\n- **License**（source_file）：Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the \"Software\" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 证据：`src/git/LICENSE`\n- **Everything Server – Architecture**（documentation）：Architecture Project Structure structure.md Startup Process startup.md Server Features features.md Extension Points extension.md How It Works how-it-works.md 证据：`src/everything/docs/architecture.md`\n- **Everything Server - Extension Points**（documentation）：Everything Server - Extension Points 证据：`src/everything/docs/extension.md`\n- **Everything Server - Features**（documentation）：Architecture architecture.md Project Structure structure.md Startup Process startup.md Server Features Extension Points extension.md How It Works how-it-works.md 证据：`src/everything/docs/features.md`\n- **Everything Server - How It Works**（documentation）：Architecture architecture.md Project Structure structure.md Startup Process startup.md Server Features features.md Extension Points extension.md How It Works 证据：`src/everything/docs/how-it-works.md`\n- **Everything Server – Server Instructions**（documentation）：Everything Server – Server Instructions 证据：`src/everything/docs/instructions.md`\n- **Everything Server - Startup Process**（documentation）：Everything Server - Startup Process 证据：`src/everything/docs/startup.md`\n- **Everything Server - Project Structure**（documentation）：Everything Server - Project Structure 证据：`src/everything/docs/structure.md`\n- **Description**（documentation）：Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry https://github.com/modelcontextprotocol/registry to make it discoverable to the MCP ecosystem. 证据：`.github/pull_request_template.md`\n- **Contributor Covenant Code of Conduct**（documentation）：Contributor Covenant Code of Conduct 证据：`CODE_OF_CONDUCT.md`\n- **Security Policy**（documentation）：Thank you for helping keep the Model Context Protocol and its ecosystem secure. 证据：`SECURITY.md`\n- **.Mcp**（structured_config）：{ \"mcpServers\": { \"mcp-docs\": { \"type\": \"http\", \"url\": \"https://modelcontextprotocol.io/mcp\" } } } 证据：`.mcp.json`\n- **Tsconfig**（structured_config）：{ \"compilerOptions\": { \"target\": \"ES2022\", \"module\": \"Node16\", \"moduleResolution\": \"Node16\", \"strict\": true, \"esModuleInterop\": true, \"skipLibCheck\": true, \"forceConsistentCasingInFileNames\": true, \"resolveJsonModule\": true }, \"include\": \"src/ / \" , \"exclude\": \"node modules\" } 证据：`tsconfig.json`\n- **Tsconfig**（structured_config）：{ \"extends\": \"../../tsconfig.json\", \"compilerOptions\": { \"outDir\": \"./dist\", \"rootDir\": \".\" }, \"include\": \"./ / .ts\" } 证据：`src/everything/tsconfig.json`\n- **Tsconfig**（structured_config）：{ \"extends\": \"../../tsconfig.json\", \"compilerOptions\": { \"outDir\": \"./dist\", \"rootDir\": \".\", \"moduleResolution\": \"NodeNext\", \"module\": \"NodeNext\" }, \"include\": \"./ / .ts\" , \"exclude\": \" / tests / \", \" / .test.ts\", \" / .spec.ts\", \"vitest.config.ts\" } 证据：`src/filesystem/tsconfig.json`\n- **Tsconfig**（structured_config）：{ \"extends\": \"../../tsconfig.json\", \"compilerOptions\": { \"outDir\": \"./dist\", \"rootDir\": \".\" }, \"include\": \"./ / .ts\" , \"exclude\": \" / .test.ts\", \"vitest.config.ts\" } 证据：`src/memory/tsconfig.json`\n- **Tsconfig**（structured_config）：{ \"extends\": \"../../tsconfig.json\", \"compilerOptions\": { \"outDir\": \"./dist\", \"rootDir\": \".\" }, \"include\": \"./ / .ts\" , \"exclude\": \" / .test.ts\", \"vitest.config.ts\" } 证据：`src/sequentialthinking/tsconfig.json`\n- **.gitattributes**（source_file）：package-lock.json linguist-generated=true 证据：`.gitattributes`\n- **Logs**（source_file）：Logs logs .log npm-debug.log yarn-debug.log yarn-error.log lerna-debug.log .pnpm-debug.log 证据：`.gitignore`\n- **.npmrc**（source_file）：registry=\"https://registry.npmjs.org/\" @modelcontextprotocol:registry=\"https://registry.npmjs.org/\" 证据：`.npmrc`\n- **!/usr/bin/env uv run --script**（source_file）：!/usr/bin/env uv run --script /// script requires-python = \" =3.12\" dependencies = \"click =8.1.8\", \"tomlkit =0.13.2\" /// import sys import re import click from pathlib import Path import json import tomlkit import datetime import subprocess from dataclasses import dataclass from typing import Any, Iterator, NewType, Protocol 证据：`scripts/release.py`\n\n## 宿主 AI 必须遵守的规则\n\n- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`CLAUDE.md`, `README.md`, `src/everything/AGENTS.md`\n- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`CLAUDE.md`, `README.md`, `src/everything/AGENTS.md`\n\n## 用户开工前应该回答的问题\n\n- 你准备在哪个宿主 AI 或本地环境中使用它？\n- 你只是想先体验工作流，还是准备真实安装？\n- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？\n\n## 验收标准\n\n- 所有能力声明都能回指到 evidence_refs 中的文件路径。\n- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。\n- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。\n\n---\n\n## Doramagic Context Augmentation\n\n下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。\n\n## Human Manual 骨架\n\n使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。\n\n宿主 AI 硬性规则：\n- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。\n- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。\n- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。\n\n- **Home**：importance `high`\n - source_paths: README.md, package.json, CLAUDE.md\n- **Repository Structure**：importance `high`\n - source_paths: package.json, tsconfig.json, CLAUDE.md, src/everything/package.json, src/filesystem/package.json\n- **Quick Start Guide**：importance `high`\n - source_paths: README.md, src/memory/package.json, src/git/pyproject.toml\n- **Everything Server**：importance `high`\n - source_paths: src/everything/package.json, src/everything/README.md, src/everything/index.ts, src/everything/server/index.ts, src/everything/tools/index.ts\n- **Filesystem Server**：importance `high`\n - source_paths: src/filesystem/package.json, src/filesystem/index.ts, src/filesystem/lib.ts, src/filesystem/path-validation.ts, src/filesystem/roots-utils.ts\n- **Memory Server**：importance `high`\n - source_paths: src/memory/package.json, src/memory/index.ts, src/memory/README.md\n- **Git Server**：importance `medium`\n - source_paths: src/git/pyproject.toml, src/git/src/mcp_server_git/server.py, src/git/README.md\n- **Time Server**：importance `medium`\n - source_paths: src/time/pyproject.toml, src/time/src/mcp_server_time/server.py, src/time/README.md\n\n## Repo Inspection Evidence / 源码检查证据\n\n- repo_clone_verified: true\n- repo_inspection_verified: true\n- repo_commit: `acedea0c24b3e20d7265f87b8b2afe2e0c6eb2f4`\n- inspected_files: `package.json`, `README.md`, `src/time/pyproject.toml`, `src/time/README.md`, `src/memory/vitest.config.ts`, `src/memory/index.ts`, `src/memory/package.json`, `src/memory/README.md`, `src/memory/tsconfig.json`, `src/everything/AGENTS.md`, `src/everything/vitest.config.ts`, `src/everything/index.ts`, `src/everything/package.json`, `src/everything/README.md`, `src/everything/tsconfig.json`, `src/git/pyproject.toml`, `src/git/README.md`, `src/sequentialthinking/vitest.config.ts`, `src/sequentialthinking/index.ts`, `src/sequentialthinking/package.json`\n\n宿主 AI 硬性规则：\n- 没有 repo_clone_verified=true 时，不得声称已经读过源码。\n- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。\n- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。\n\n## Doramagic Pitfall Constraints / 踩坑约束\n\n这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。\n\n### Constraint 1: 能力判断依赖假设\n\n- Trigger: README/documentation is current enough for a first validation pass.\n- Host AI rule: 将假设转成下游验证清单。\n- Why it matters: 假设不成立时，用户拿不到承诺的能力。\n- Evidence: capability.assumptions | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | README/documentation is current enough for a first validation pass.\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 2: 维护活跃度未知\n\n- Trigger: 未记录 last_activity_observed。\n- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- Evidence: evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | last_activity_observed missing\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 3: 下游验证发现风险项\n\n- Trigger: no_demo\n- Host AI rule: 进入安全/权限治理复核队列。\n- Why it matters: 下游已经要求复核，不能在页面中弱化。\n- Evidence: downstream_validation.risk_items | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 4: 存在评分风险\n\n- Trigger: no_demo\n- Host AI rule: 把风险写入边界卡，并确认是否需要人工复核。\n- Why it matters: 风险会影响是否适合普通用户安装。\n- Evidence: risks.scoring_risks | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 5: issue/PR 响应质量未知\n\n- Trigger: issue_or_pr_quality=unknown。\n- Host AI rule: 抽样最近 issue/PR，判断是否长期无人处理。\n- Why it matters: 用户无法判断遇到问题后是否有人维护。\n- Evidence: evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | issue_or_pr_quality=unknown\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 6: 发布节奏不明确\n\n- Trigger: release_recency=unknown。\n- Host AI rule: 确认最近 release/tag 和 README 安装命令是否一致。\n- Why it matters: 安装命令和文档可能落后于代码，用户踩坑概率升高。\n- Evidence: evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | release_recency=unknown\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n",
"summary": "给宿主 AI 的上下文和工作边界。",
"title": "AI Context Pack / 带给我的 AI"
},
"boundary_risk_card": {
"asset_id": "boundary_risk_card",
"filename": "BOUNDARY_RISK_CARD.md",
"markdown": "# Boundary & Risk Card / 安装前决策卡\n\n项目：modelcontextprotocol/servers\n\n## Doramagic 试用结论\n\n当前结论：可以进入发布前推荐检查；首次使用仍应从最小权限、临时目录和可回滚配置开始。\n\n## 用户现在可以做\n\n- 可以先阅读 Human Manual，理解项目目的和主要工作流。\n- 可以复制 Prompt Preview 做安装前体验；这只验证交互感，不代表真实运行。\n- 可以把官方 Quick Start 命令放到隔离环境中验证，不要直接进主力环境。\n\n## 现在不要做\n\n- 不要把 Prompt Preview 当成项目实际运行结果。\n- 不要把 metadata-only validation 当成沙箱安装验证。\n- 不要把未验证能力写成“已支持、已跑通、可放心安装”。\n- 不要在首次试用时交出生产数据、私人文件、真实密钥或主力配置目录。\n\n## 安装前检查\n\n- 宿主 AI 是否匹配：local_cli\n- 官方安装入口状态：已发现官方入口\n- 是否在临时目录、临时宿主或容器中验证：必须是\n- 是否能回滚配置改动：必须能\n- 是否需要 API Key、网络访问、读写文件或修改宿主配置：未确认前按高风险处理\n- 是否记录了安装命令、实际输出和失败日志：必须记录\n\n## 当前阻塞项\n\n- 无阻塞项。\n\n## 项目专属踩坑\n\n- 能力判断依赖假设（medium）：假设不成立时，用户拿不到承诺的能力。 建议检查：将假设转成下游验证清单。\n- 维护活跃度未知（medium）：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 下游验证发现风险项（medium）：下游已经要求复核，不能在页面中弱化。 建议检查：进入安全/权限治理复核队列。\n- 存在评分风险（medium）：风险会影响是否适合普通用户安装。 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- issue/PR 响应质量未知（low）：用户无法判断遇到问题后是否有人维护。 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n\n## 风险与权限提示\n\n- no_demo: medium\n\n## 证据缺口\n\n- 暂未发现结构化证据缺口。\n",
"summary": "安装、权限、验证和推荐前风险。",
"title": "Boundary & Risk Card / 边界与风险卡"
},
"human_manual": {
"asset_id": "human_manual",
"filename": "HUMAN_MANUAL.md",
"markdown": "# https://github.com/modelcontextprotocol/servers 项目说明书\n\n生成时间：2026-05-15 19:59:58 UTC\n\n## 目录\n\n- [Home](#home)\n- [Repository Structure](#repository-structure)\n- [Quick Start Guide](#quick-start)\n- [Everything Server](#everything-server)\n- [Filesystem Server](#filesystem-server)\n- [Memory Server](#memory-server)\n- [Git Server](#git-server)\n- [Time Server](#time-server)\n- [Fetch Server](#fetch-server)\n- [Sequential Thinking Server](#sequential-thinking-server)\n\n\n\n## Home\n\n### 相关页面\n\n相关主题：[Repository Structure](#repository-structure), [Quick Start Guide](#quick-start)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n \n\n# Home\n\n## Overview\n\nThe **Model Context Protocol (MCP) Servers** repository is the official collection of reference implementations for MCP servers. MCP is a protocol that enables AI models to interact with external tools, resources, and data sources through a standardized interface.\n\nThis repository serves as a central hub for developing, documenting, and distributing MCP server implementations that can be integrated with AI assistants and development tools.\n\n资料来源：[CLAUDE.md:1]()\n\n## Repository Architecture\n\nThe repository follows a monorepo structure where each MCP server resides in its own directory under `src/`.\n\n```mermaid\ngraph TD\n A[Model Context Protocol Servers] --> B[fetch]\n A --> C[sequential-thinking]\n A --> D[everything]\n A --> E[filesystem]\n A --> F[time]\n A --> G[memory]\n \n H[Shared Infrastructure] --> A\n H --> I[CLAUDE.md Guidelines]\n H --> J[Contributing Standards]\n```\n\n## Available MCP Servers\n\n### Server Comparison Table\n\n| Server | Language | Primary Use Case | Transport |\n|--------|----------|------------------|-----------|\n| `fetch` | Python | HTTP content fetching | stdio |\n| `sequential-thinking` | Node.js | Chain-of-thought reasoning | stdio, SSE, HTTP |\n| `everything` | Node.js | Comprehensive tool suite | stdio, SSE, HTTP |\n| `filesystem` | Node.js | File system operations | stdio |\n| `time` | Python | Time/timezone utilities | stdio |\n| `memory` | Node.js | Knowledge graph storage | stdio |\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md), [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n\n### Fetch Server\n\nThe `fetch` server provides HTTP content retrieval capabilities with support for:\n\n- Web content fetching via tools\n- User-initiated requests\n- robots.txt compliance (configurable)\n- Custom user-agent headers\n- Proxy support\n\n**Installation Methods:**\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-50]()\n\n### Filesystem Server\n\nThe filesystem server exposes file system operations with security boundaries:\n\n- Read operations: read_file, read_media_file, read_multiple_files\n- Directory operations: list_directory, directory_tree, search_files\n- Write operations: create_directory, write_file, edit_file, move_file\n- All paths validated against allowed directories\n\n**File Operation Annotations:**\n\n| Tool | readOnlyHint | idempotentHint | destructiveHint |\n|------|--------------|----------------|-----------------|\n| `write_file` | false | true | true |\n| `edit_file` | false | false | true |\n| `move_file` | false | false | true |\n| `create_directory` | false | true | false |\n\n资料来源：[src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n\n### Memory Server\n\nThe memory server implements a knowledge graph for persistent entity storage:\n\n- **create_entities**: Create new entities with type classification\n- **create_relations**: Establish relationships between entities\n- **add_observations**: Append observations to existing entities\n- **delete_entities**: Remove entities and cascading relations\n- **delete_observations**: Remove specific observations\n\nStorage backend: JSONL file format (configurable via `MEMORY_FILE_PATH`)\n\n资料来源：[src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n\n### Time Server\n\nThe time server provides timezone-aware time utilities:\n\n- Get current time in any timezone\n- Convert times between timezones\n- Automatic system timezone detection\n- Configurable via `--local-timezone` argument\n\n资料来源：[src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n\n### Everything Server\n\nThe everything server aggregates multiple MCP capabilities into a single server. Supports multiple transport protocols:\n\n- stdio (default)\n- SSE (deprecated as of 2025-03-26)\n- Streamable HTTP\n\n资料来源：[src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n\n## Development Standards\n\n### TypeScript Servers\n\n| Aspect | Standard |\n|--------|----------|\n| Target | ES2022 |\n| Module | Node16 |\n| Type System | Strict mode |\n| Testing | vitest with @vitest/coverage-v8 |\n| Node Version | 22 |\n\n**Code Style Guidelines:**\n\n- ES modules with `.js` extension in import paths\n- Zod schemas for tool input validation\n- 2-space indentation, trailing commas in multi-line objects\n- camelCase for variables/functions, PascalCase for types/classes\n- kebab-case for file names and registered tools/prompts/resources\n- Verb-first tool names (e.g., `get-file-info`)\n\n资料来源：[CLAUDE.md:5-15]()\n\n### Python Servers\n\n| Aspect | Standard |\n|--------|----------|\n| Build System | hatchling (uv build) |\n| Package Manager | uv (not pip) |\n| Python Version | >= 3.10 |\n| Type Checking | pyright |\n| Linting | ruff |\n\n**Development Commands:**\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\nuv run pytest\nuv run pyright\nuv run ruff check .\n```\n\n资料来源：[CLAUDE.md:16-26]()\n\n## Contributing\n\n### Accepted Contributions\n\n- Bug fixes\n- Usability improvements\n- Enhancements demonstrating MCP protocol features (Resources, Prompts, Roots)\n\n### Testing Requirements\n\nAll new functionality requires corresponding tests under `tests/` or `test/` directories.\n\n### Code Review\n\n- Pull requests welcome\n- CI enforces type checking and linting standards\n\n资料来源：[CLAUDE.md:27-35]()\n\n## Client Integration\n\n### Claude Desktop\n\nAdd server configurations to `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-something\"]\n }\n }\n}\n```\n\n### VS Code\n\nOne-click installation buttons available in each server's README for quick setup.\n\n### Zed\n\nConfiguration via `settings.json` using the `context_servers` array format.\n\n### Docker Installation\n\nAll servers support Docker deployment:\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/server-name\"]\n }\n }\n}\n```\n\n## Debugging\n\nUse the MCP Inspector for debugging:\n\n```bash\n# For uvx installations\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n\n# For local development\ncd path/to/servers/src/\nnpx @modelcontextprotocol/inspector uv run mcp-server-\n```\n\n资料来源：[src/fetch/README.md:1]()\n\n## License\n\nAll MCP servers in this repository are licensed under the MIT License, permitting free use, modification, and distribution subject to MIT License terms.\n\n---\n\n\n\n## Repository Structure\n\n### 相关页面\n\n相关主题：[Home](#home), [Quick Start Guide](#quick-start)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [package.json](https://github.com/modelcontextprotocol/servers/blob/main/package.json)\n- [tsconfig.json](https://github.com/modelcontextprotocol/servers/blob/main/tsconfig.json)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [src/everything/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/package.json)\n- [src/filesystem/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/package.json)\n- [src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n \n\n# Repository Structure\n\n## Overview\n\nThe [modelcontextprotocol/servers](https://github.com/modelcontextprotocol/servers) repository is a monorepo containing implementations of Model Context Protocol (MCP) servers. MCP is a protocol that enables AI models to interact with external tools, resources, and data sources. The repository houses multiple independent server implementations, each providing different capabilities such as filesystem access, web fetching, time utilities, and more.\n\nThe repository supports two primary implementation languages: **TypeScript/Node.js** and **Python**. This dual-language approach allows developers to choose their preferred runtime environment while maintaining feature parity across servers.\n\n## Directory Layout\n\nThe repository follows a modular structure where each MCP server lives in its own directory under the `src/` prefix.\n\n```\nservers/\n├── package.json # Root workspace configuration\n├── tsconfig.json # TypeScript configuration\n├── CLAUDE.md # Developer guidelines\n├── .github/ # GitHub workflows and PR templates\n├── src/\n│ ├── everything/ # Multi-feature demonstration server (TypeScript)\n│ ├── filesystem/ # File operations server (TypeScript)\n│ ├── fetch/ # Web content fetching server (Python)\n│ ├── memory/ # Knowledge graph memory server (TypeScript)\n│ ├── sequentialthinking/ # Chain-of-thought reasoning server (TypeScript)\n│ └── time/ # Time utilities server (Python)\n```\n\nEach server directory is self-contained with its own dependencies, build configuration, and documentation. The `src/everything` server serves as a reference implementation demonstrating all MCP capabilities including tools, resources, and prompts.\n\n## Technology Stack\n\n### TypeScript Servers\n\nTypeScript-based servers use the following technology stack:\n\n| Component | Technology | Version |\n|-----------|------------|---------|\n| Runtime | Node.js | 22 |\n| Language | TypeScript | ES2022 target |\n| Module System | Node16 | ES modules |\n| Type Checking | TypeScript strict mode | - |\n| Testing | Vitest | With @vitest/coverage-v8 |\n| SDK | @modelcontextprotocol/sdk | Latest |\n\n资料来源：[CLAUDE.md:2-8]()\n\nThe TypeScript servers share common patterns:\n\n- **ES Modules** with `.js` extension in import paths\n- **Strict TypeScript typing** for all functions and variables\n- **Zod schemas** for tool input validation\n- **2-space indentation** with trailing commas\n- Naming conventions: `camelCase` for variables/functions, `PascalCase` for types/classes, `kebab-case` for file names and registered tools/prompts/resources\n\n资料来源：[CLAUDE.md:24-30]()\n\n### Python Servers\n\nPython servers follow these specifications:\n\n| Component | Technology | Version |\n|-----------|------------|---------|\n| Runtime | Python | >= 3.10 |\n| Package Manager | uv | - |\n| Build System | hatchling | - |\n| Type Checking | pyright | Enforced in CI |\n| Linting | ruff | - |\n| Async | pytest-asyncio | For testing |\n\n资料来源：[CLAUDE.md:10-17]()\n\nPython server development commands follow a consistent pattern:\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\nuv run pytest # Run tests\nuv run pyright # Type checking\nuv run ruff check . # Linting\n```\n\n资料来源：[CLAUDE.md:12-16]()\n\n## Server Organization\n\n### Server Categories\n\nThe servers in this repository can be categorized by their implementation language and primary function:\n\n```mermaid\ngraph TD\n A[modelcontextprotocol/servers] --> B[TypeScript Servers]\n A --> C[Python Servers]\n \n B --> B1[everything]\n B --> B2[filesystem]\n B --> B3[memory]\n B --> B4[sequentialthinking]\n \n C --> C1[fetch]\n C --> C2[time]\n \n B1 --> B1a[Tools, Resources, Prompts]\n B2 --> B2a[File Operations]\n B3 --> B3a[Knowledge Graph]\n B4 --> B4a[Chain-of-Thought]\n C1 --> C1a[HTTP Fetching]\n C2 --> C2a[Timezone Operations]\n```\n\n### TypeScript Server Structure\n\nEach TypeScript server follows a consistent internal structure:\n\n```\nsrc//\n├── package.json\n├── tsconfig.json\n├── src/\n│ ├── index.ts # Main entry point\n│ ├── tools/ # Tool definitions\n│ ├── resources/ # Resource definitions\n│ ├── prompts/ # Prompt templates\n│ └── types/ # TypeScript type definitions\n├── docs/ # Server documentation\n└── tests/ # Test files\n```\n\n资料来源：[CLAUDE.md:35-37]()\n\nThe modular structure allows each server to register its capabilities through standardized functions:\n\n- `registerTools(server)` - Register MCP tools\n- `registerResources(server)` - Register MCP resources\n- `registerPrompts(server)` - Register MCP prompts\n\n资料来源：[CLAUDE.md:41-43]()\n\n### Python Server Structure\n\nPython servers use `pyproject.toml` for configuration and follow this pattern:\n\n```\nsrc//\n├── pyproject.toml # Project metadata and dependencies\n├── src/\n│ └── mcp_server_/ # Package directory\n│ ├── __init__.py\n│ └── server.py # Main server implementation\n└── tests/ # Test files\n```\n\n资料来源：[src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n\n## Configuration Patterns\n\n### Claude Desktop Integration\n\nServers can be integrated with Claude Desktop through JSON configuration. Each server provides installation instructions for different deployment methods.\n\n#### NPX Installation (Node.js servers)\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-\"]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:1-10]()\n\n#### UVX Installation (Python servers)\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-8]()\n\n#### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"server-name\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/\"]\n }\n }\n}\n```\n\n资料来源：[src/everything/README.md:1-10]()\n\n### Windows Configuration\n\nWindows environments require `cmd /c` wrapper for NPX commands:\n\n```json\n{\n \"servers\": {\n \"server-name\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-\"]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:1-20]()\n\nWindows users running Python servers via UVX may need to set environment variables to avoid timeout issues:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md:1-15]()\n\n## Build and Development\n\n### Building Docker Images\n\nEach server can be containerized for deployment:\n\n```bash\ndocker build -t mcp/ -f src//Dockerfile .\n```\n\n资料来源：[src/filesystem/README.md:1-5]()\n\nFor the everything server:\n\n```bash\ndocker build -t mcp/everything -f src/everything/Dockerfile .\n```\n\n### Running from Source\n\n#### TypeScript Servers\n\n```bash\ncd src/\nnpm install\nnpm run start:streamableHttp # Streamable HTTP transport\nnpm run start:sse # SSE transport (deprecated)\n```\n\n资料来源：[src/everything/README.md:1-15]()\n\n#### Python Servers\n\n```bash\ncd src/\nuv sync --frozen --all-extras --dev\nuv run mcp-server-\n```\n\n### Debugging\n\nThe MCP Inspector tool can be used to debug servers:\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-\n```\n\n资料来源：[src/fetch/README.md:1-5]()\n\nFor local development:\n\n```bash\ncd path/to/servers/src/\nnpx @modelcontextprotocol/inspector uv run mcp-server-\n```\n\n## Contributing Patterns\n\n### Adding New Servers\n\nThe repository provides clear guidelines for extending the project:\n\n1. Create a new directory under `src//`\n2. Follow the established patterns for your implementation language\n3. Implement server capability registration functions\n4. Add comprehensive documentation\n\n### Key Contributing Guidelines\n\n| Aspect | Requirement |\n|--------|-------------|\n| Tool naming | Verb-first (e.g., `get-file-info`) |\n| Annotations | Set `readOnlyHint`, `idempotentHint`, `destructiveHint` per MCP spec |\n| Transport support | stdio (default), SSE (deprecated), Streamable HTTP |\n| Testing | Add tests using vitest (TS) or pytest (Python) |\n| Documentation | Include README.md with configuration examples |\n\n资料来源：[CLAUDE.md:41-46]()\n\n### Everything Server as Reference\n\nThe `src/everything` server demonstrates all MCP features and is an excellent reference for implementing new servers:\n\n- **Modular structure**: Separate modules for tools, resources, and prompts\n- **Registration pattern**: `registerX(server)` functions following SDK conventions\n- **Schema accuracy**: JSON Schema with descriptions and examples\n- **Extensibility**: Easy to add new modules following existing patterns\n\n资料来源：[src/everything/AGENTS.md:1-8]()\n\n## Transport Protocols\n\nThe repository supports multiple transport mechanisms for client-server communication:\n\n| Transport | Status | Description |\n|-----------|--------|-------------|\n| stdio | Default | Standard input/output communication |\n| Streamable HTTP | Current | Modern HTTP-based transport |\n| SSE | Deprecated | Server-Sent Events (deprecated 2025-03-26) |\n\n资料来源：[src/everything/README.md:1-20]()\n\nThe streamable HTTP transport is the recommended modern approach:\n\n```bash\nnpx @modelcontextprotocol/server- streamableHttp\n```\n\n## Tool Annotation System\n\nTypeScript servers use a standardized annotation system for tools to indicate their behavior to clients:\n\n| Annotation | Description | Values |\n|------------|-------------|--------|\n| `readOnlyHint` | Indicates if tool modifies state | `true`/`false` |\n| `idempotentHint` | Indicates if repeated calls produce same result | `true`/`false` |\n| `destructiveHint` | Indicates if tool deletes data | `true`/`false` |\n\n资料来源：[src/filesystem/README.md:1-30]()\n\nExample from the filesystem server:\n\n```typescript\nserver.registerTool(\n \"write_file\",\n {\n title: \"Write File\",\n inputSchema: {\n path: z.string(),\n content: z.string()\n },\n annotations: { readOnlyHint: false, idempotentHint: true, destructiveHint: true }\n },\n async (args) => { /* ... */ }\n);\n```\n\n资料来源：[src/filesystem/index.ts:1-25]()\n\n## Summary\n\nThe modelcontextprotocol/servers repository is organized as a well-structured monorepo that:\n\n- Contains multiple independent MCP server implementations under `src/`\n- Supports both TypeScript (Node.js 22) and Python (>=3.10) implementations\n- Follows consistent patterns for tool, resource, and prompt registration\n- Provides flexible deployment options (NPX, UVX, Docker)\n- Includes comprehensive documentation and debugging tools\n- Enforces type safety and testing through CI/CD\n\nThe `everything` server serves as the primary reference implementation, while other servers demonstrate specialized use cases like filesystem operations, web fetching, time utilities, and knowledge graph storage.\n\n---\n\n\n\n## Quick Start Guide\n\n### 相关页面\n\n相关主题：[Home](#home), [Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n- [src/sequentialthinking/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n \n\n# Quick Start Guide\n\nThis guide provides a comprehensive introduction to getting started with Model Context Protocol (MCP) servers. MCP servers are tools that extend the capabilities of AI assistants like Claude by providing access to external resources, file systems, databases, and more.\n\n## Overview\n\nThe MCP servers repository contains a collection of standalone servers that implement the Model Context Protocol. Each server provides specific functionality that can be integrated into MCP-compatible clients such as Claude Desktop, VS Code, and Zed.\n\n```mermaid\ngraph TD\n A[MCP Client] --> B[MCP Server]\n B --> C[Git Server]\n B --> D[Memory Server]\n B --> E[Filesystem Server]\n B --> F[Fetch Server]\n B --> G[Time Server]\n B --> H[Everything Server]\n B --> I[Sequential Thinking Server]\n```\n\n## Prerequisites\n\nBefore getting started with MCP servers, ensure your environment meets the following requirements.\n\n### System Requirements\n\n| Component | Requirement |\n|-----------|-------------|\n| Node.js | Version 22+ (for TypeScript servers) |\n| Python | Version 3.10+ (for Python servers) |\n| Docker | Latest stable version (optional) |\n| Package Manager | `uv` (recommended), `pip`, or `npm` |\n\n### Required Tools\n\nBased on the project guidelines, the following tools are required:\n\n- **For Python servers**: `uv` is the primary package manager 资料来源：[CLAUDE.md]()\n- **For Node.js servers**: `npm` or `npx` 资料来源：[README.md]()\n- **For containerized deployment**: Docker\n\n## Installation Methods\n\nMCP servers support multiple installation methods. Choose the one that best fits your environment.\n\n### Method 1: Using uvx (Recommended)\n\n`uvx` is the recommended installation method for Python-based servers. It provides easy setup and automatic dependency management 资料来源：[README.md]()\n\n```bash\n# Install a single server\nuvx mcp-server-git\n\n# Or install via npm for quick testing\nnpx @modelcontextprotocol/server-memory\n```\n\n### Method 2: Using pip\n\nFor Python servers, you can also use pip directly:\n\n```bash\n# Install the server package\npip install mcp-server-git\n\n# Run the server\npython -m mcp_server_git\n```\n\n### Method 3: Using Docker\n\nDocker provides isolation and consistency across different environments:\n\n```bash\n# Pull and run a pre-built image\ndocker run -i --rm mcp/filesystem\n\n# Build your own image\ndocker build -t mcp/filesystem -f src/filesystem/Dockerfile .\n```\n\n### Method 4: Using npx (Node.js)\n\nFor TypeScript/JavaScript servers:\n\n```bash\n# Run directly with npx\nnpx -y @modelcontextprotocol/server-memory\n```\n\n## Quick Start by Server Type\n\n### Git Server\n\nThe Git server provides tools for interacting with Git repositories.\n\n**Installation:**\n\n```bash\nuvx mcp-server-git\n```\n\n**Alternative with pip:**\n\n```bash\npip install mcp-server-git\npython -m mcp_server_git\n```\n\n资料来源：[README.md]()\n\n### Memory Server\n\nThe Memory server provides a knowledge graph storage system for maintaining persistent context across conversations 资料来源：[src/memory/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-memory\n```\n\n**Custom Configuration:**\n\n| Parameter | Description | Default |\n|-----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to the memory storage JSONL file | `memory.jsonl` |\n\n**Example Configuration:**\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-memory\"],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n### Filesystem Server\n\nThe Filesystem server provides secure file system access within allowed directories 资料来源：[src/filesystem/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-filesystem /path/to/allowed/dir\n```\n\n**Available Tools:**\n\n| Tool | Read Only | Idempotent | Destructive | Notes |\n|------|-----------|------------|-------------|-------|\n| `read_file` | ✓ | – | – | Pure read |\n| `read_media_file` | ✓ | – | – | Pure read |\n| `read_multiple_files` | ✓ | – | – | Pure read |\n| `list_directory` | ✓ | – | – | Pure read |\n| `search_files` | ✓ | – | – | Pure read |\n| `write_file` | ✗ | ✓ | ✓ | Overwrites existing files |\n| `edit_file` | ✗ | ✗ | ✓ | May double-apply edits |\n| `move_file` | ✗ | ✗ | ✓ | Deletes source file |\n| `create_directory` | ✗ | ✓ | ✗ | Re-creating same dir is no-op |\n\n### Fetch Server\n\nThe Fetch server enables web content retrieval with proper robots.txt compliance 资料来源：[src/fetch/README.md]()\n\n**Installation:**\n\n```bash\nuvx mcp-server-fetch\n```\n\n**Customization Options:**\n\n| Argument | Description |\n|----------|-------------|\n| `--ignore-robots-txt` | Disable robots.txt compliance |\n| `--user-agent=` | Custom user-agent string |\n| `--proxy-url=` | Configure proxy server |\n\n**Default User-Agents:**\n\n```\nModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)\nModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)\n```\n\n### Time Server\n\nThe Time server provides timezone-aware time operations 资料来源：[src/time/README.md]()\n\n**Installation:**\n\n```bash\nuvx mcp-server-time\n```\n\n**Available Tools:**\n\n| Tool | Description |\n|------|-------------|\n| `get_current_time` | Get current time in a specified timezone |\n| `convert_time` | Convert time between timezones |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"get_current_time\",\n \"arguments\": {\n \"timezone\": \"Europe/Warsaw\"\n }\n}\n```\n\n### Sequential Thinking Server\n\nThe Sequential Thinking server provides structured reasoning capabilities 资料来源：[src/sequentialthinking/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-sequential-thinking\n```\n\n**Building from Source:**\n\n```bash\ndocker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .\n```\n\n### Everything Server\n\nThe Everything server aggregates multiple MCP server capabilities into a single endpoint 资料来源：[src/everything/README.md]()\n\n**Installation:**\n\n```bash\nnpx -y @modelcontextprotocol/server-everything\n```\n\n**Available Transport Options:**\n\n| Transport | Command |\n|-----------|---------|\n| stdio | `npx @modelcontextprotocol/server-everything stdio` |\n| SSE (deprecated) | `npx @modelcontextprotocol/server-everything sse` |\n| Streamable HTTP | `npx @modelcontextprotocol/server-everything streamableHttp` |\n\n## Client Configuration\n\n### Claude Desktop Configuration\n\nAdd server configurations to your Claude Desktop settings file 资料来源：[README.md]():\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-memory\"]\n },\n \"filesystem\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-filesystem\", \"${workspaceFolder}\"]\n }\n }\n}\n```\n\n### Windows Configuration\n\nOn Windows, wrap commands with `cmd /c`:\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-memory\"]\n }\n }\n}\n```\n\n### VS Code Configuration\n\nQuick installation buttons are available for VS Code and VS Code Insiders. Simply click the badge to install:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n### Zed Configuration\n\n```json\n\"context_servers\": {\n \"mcp-server-time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n}\n```\n\n## Development Setup\n\n### Setting Up Python Server Development\n\n```bash\ncd src/ && uv sync --frozen --all-extras --dev\n\n# Run tests\nuv run pytest\n\n# Type checking\nuv run pyright\n\n# Linting\nuv run ruff check .\n```\n\n资料来源：[CLAUDE.md]()\n\n### Setting Up Node.js Server Development\n\n```bash\ncd src/\nnpm install\nnpm run build\n```\n\n**Testing:**\n\n```bash\nnpm test\n```\n\n## Troubleshooting\n\n### Common Issues\n\n#### Timeout Issues on Windows\n\nIf experiencing timeout issues on Windows, set the `PYTHONIOENCODING` environment variable:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n#### Character Encoding Issues\n\nFor servers that handle text content, ensure proper encoding by adding environment variables or command-line arguments as shown above.\n\n### Debugging with MCP Inspector\n\nUse the MCP inspector to debug server functionality:\n\n```bash\n# For uvx installations\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n\n# For local development\ncd path/to/servers/src/fetch\nnpx @modelcontextprotocol/inspector uv run mcp-server-fetch\n```\n\n## Architecture Overview\n\n```mermaid\ngraph LR\n A[Client Application] -->|MCP Protocol| B[Transport Layer]\n B -->|stdio/sse/http| C[Server Implementation]\n C -->|Tool Execution| D[External Resources]\n D -->|Results| C\n C -->|Formatted Response| B\n B -->|MCP Response| A\n```\n\n### Transport Methods\n\n| Transport | Use Case | Persistent Connection |\n|-----------|----------|----------------------|\n| stdio | CLI tools, Desktop apps | ✗ |\n| SSE | Real-time updates | ✓ |\n| Streamable HTTP | Web applications | ✓ |\n\n## Next Steps\n\n- Explore individual server documentation for advanced features\n- Review the [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md) for contribution guidelines\n- Check the main [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md) for the complete server list\n- Join the community to share your implementations and extensions\n\n---\n\n\n\n## Everything Server\n\n### 相关页面\n\n相关主题：[Filesystem Server](#filesystem-server), [Memory Server](#memory-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/everything/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/README.md)\n- [src/everything/server/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/server/index.ts)\n- [src/everything/tools/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/tools/index.ts)\n- [src/everything/resources/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/resources/index.ts)\n- [src/everything/resources/session.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/resources/session.ts)\n- [src/everything/docs/features.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/features.md)\n- [src/everything/docs/architecture.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/architecture.md)\n- [src/everything/docs/extension.md](https://github.com/modelcontextprotocol/servers/blob/main/src/everything/docs/extension.md)\n \n\n# Everything Server\n\n## Overview\n\nThe Everything Server is a comprehensive Model Context Protocol (MCP) server implementation that provides a wide range of tools, resources, and prompts for AI-assisted interactions. It serves as a reference implementation demonstrating the full capabilities of the MCP specification. 资料来源：[src/everything/README.md]()\n\n### Purpose and Scope\n\nThe Everything Server is designed to:\n\n- Provide a complete example of MCP server implementation patterns\n- Offer practical tools for file system operations, memory management, and more\n- Demonstrate resource and prompt template capabilities\n- Support multiple transport mechanisms for different use cases\n- Serve as a foundation for building custom MCP servers 资料来源：[src/everything/AGENTS.md]()\n\n## Architecture\n\n### High-Level Architecture\n\n```mermaid\ngraph TD\n A[Client] -->|MCP Protocol| B[Transport Layer]\n B --> C[stdio]\n B --> D[SSE]\n B --> E[Streamable HTTP]\n C --> F[Server Core]\n D --> F\n E --> F\n F --> G[Tools Handler]\n F --> H[Resources Handler]\n F --> I[Prompts Handler]\n G --> J[File System Tools]\n G --> K[Memory Tools]\n G --> L[Utility Tools]\n H --> M[Static Resources]\n H --> N[Dynamic Resources]\n I --> O[Prompt Templates]\n```\n\n### Module Structure\n\nThe server is organized into distinct modules following a clear separation of concerns: 资料来源：[src/everything/docs/architecture.md]()\n\n| Module | Purpose | Key Files |\n|--------|---------|-----------|\n| **server** | Core server implementation and transport handling | `server/index.ts` |\n| **tools** | Tool definitions and handlers | `tools/index.ts`, `tools/*.ts` |\n| **resources** | Resource registration and management | `resources/index.ts`, `resources/session.ts` |\n| **prompts** | Prompt templates | `prompts/index.ts` |\n\n### Component Hierarchy\n\n```mermaid\ngraph TD\n A[McpServer Instance] --> B[Tools Registry]\n A --> C[Resources Registry]\n A --> D[Prompts Registry]\n B --> E[Tool Handlers]\n C --> F[Resource Providers]\n D --> G[Prompt Definitions]\n E --> H[File Operations]\n E --> I[Memory Operations]\n E --> J[Utility Operations]\n```\n\n## Installation\n\n### Prerequisites\n\n- Node.js version 22 or higher\n- npm or npx for package management 资料来源：[CLAUDE.md]()\n\n### Installation Methods\n\n#### Global npm Installation\n\n```bash\nnpm install -g @modelcontextprotocol/server-everything@latest\n```\n\n#### Using npx (No Installation Required)\n\n```bash\nnpx @modelcontextprotocol/server-everything\n```\n\n#### Docker\n\n```bash\ndocker run -i --rm mcp/everything\n```\n\n#### Running from Source\n\n```bash\ncd src/everything\nnpm install\nnpm run start:streamableHttp\n```\n\n资料来源：[src/everything/README.md]()\n\n### Claude Desktop Configuration\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-everything\"]\n }\n }\n}\n```\n\n#### Windows Configuration\n\nOn Windows, use `cmd /c` for proper process handling:\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-everything\"]\n }\n }\n}\n```\n\n## Transport Options\n\nThe Everything Server supports multiple transport mechanisms for communication with MCP clients.\n\n### Supported Transports\n\n| Transport | Status | Description |\n|-----------|--------|-------------|\n| **stdio** | Default | Standard input/output transport for CLI integration |\n| **Streamable HTTP** | Recommended | Modern transport supporting streaming responses (recommended as of 2025-03-26) |\n| **SSE** | Deprecated | Server-Sent Events transport (deprecated as of 2025-03-26) |\n\n### Running with Different Transports\n\n```bash\n# Default (stdio)\nnpx @modelcontextprotocol/server-everything\n\n# Explicitly stdio\nnpx @modelcontextprotocol/server-everything stdio\n\n# SSE (deprecated)\nnpx @modelcontextprotocol/server-everything sse\n\n# Streamable HTTP (recommended)\nnpx @modelcontextprotocol/server-everything streamableHttp\n```\n\n资料来源：[src/everything/README.md]()\n\n## Features\n\n### Core Capabilities\n\nThe Everything Server provides a comprehensive set of features: 资料来源：[src/everything/docs/features.md]()\n\n- **Tool Orchestration**: Extensive set of tools for various operations\n- **Resource Management**: Static and dynamic resource provision\n- **Prompt Templates**: Reusable prompt definitions\n- **Session Resources**: Dynamic session-based resource creation\n- **Multi-Transport Support**: stdio, HTTP+SSE, and Streamable HTTP\n\n### Tool Categories\n\n| Category | Tools | Description |\n|----------|-------|-------------|\n| **File System** | read_file, write_file, edit_file, move_file, list_directory, etc. | Full file system operations within allowed directories |\n| **Memory** | create_entities, create_relations, add_observations, etc. | Knowledge graph operations for persistent memory |\n| **Time** | get_current_time, convert_timezone | Time and timezone utilities |\n| **Utility** | Echo, random, etc. | General purpose utilities |\n\n## Tools Reference\n\n### Tool Registration Pattern\n\nTools are registered using the MCP SDK with Zod schemas for input validation: 资料来源：[src/everything/tools/index.ts]()\n\n```typescript\nserver.registerTool(\n \"tool_name\",\n {\n title: \"Tool Title\",\n description: \"Tool description\",\n inputSchema: { /* Zod schema */ },\n outputSchema: { /* output schema */ },\n annotations: {\n readOnlyHint: boolean,\n idempotentHint: boolean,\n destructiveHint: boolean\n }\n },\n async (args) => {\n // Handler implementation\n }\n);\n```\n\n### Tool Annotations\n\nEach tool includes annotations describing its behavior: 资料来源：[src/filesystem/README.md]()\n\n| Annotation | Values | Description |\n|------------|--------|-------------|\n| `readOnlyHint` | `true/false` | Whether the tool only reads data |\n| `idempotentHint` | `true/false` | Whether repeated calls produce the same result |\n| `destructiveHint` | `true/false` | Whether the tool modifies or deletes data |\n\n## Resources\n\n### Resource Types\n\nThe Everything Server implements resources following the MCP specification: 资料来源：[src/everything/resources/index.ts]()\n\n```mermaid\ngraph LR\n A[Resources] --> B[Static Resources]\n A --> C[Dynamic Resources]\n A --> D[Session Resources]\n B --> E[Pre-registered at startup]\n C --> F[Generated on-demand]\n D --> G[Created per session]\n```\n\n### Session Resources\n\nSession resources are dynamically created and managed: 资料来源：[src/everything/resources/session.ts:1-65]()\n\n```typescript\nexport const registerSessionResource = (\n server: McpServer,\n resource: Resource,\n type: \"text\" | \"blob\",\n payload: string\n): ResourceLink => {\n // Prepare resource content based on type\n const resourceContent = type === \"text\"\n ? { uri: uri.toString(), mimeType, text: payload }\n : { uri: uri.toString(), mimeType, blob: payload };\n\n // Remove existing resource with same URI if present\n const existingResource = registeredResources.get(uri);\n if (existingResource) {\n existingResource.remove();\n registeredResources.delete(uri);\n }\n\n // Register the resource with the server\n const registeredResource = server.registerResource(\n name, uri,\n { mimeType, description, title, annotations, icons, _meta },\n async () => ({ contents: [resourceContent] })\n );\n\n registeredResources.set(uri, registeredResource);\n return { type: \"resource_link\", ...resource };\n};\n```\n\n## Extension Guide\n\n### Adding New Tools\n\nTo extend the Everything Server with new tools: 资料来源：[src/everything/docs/extension.md]()\n\n1. Create a new file in the `tools/` folder (naming, exports, and registration function)\n2. Export a `registerX(server)` function that registers new items with the MCP SDK\n3. Wire your new module into the central index (`tools/index.ts`)\n4. Ensure schemas are accurate JSON Schema with helpful descriptions and examples\n\n### Extension Pattern\n\n```typescript\n// tools/example-tool.ts\nimport { McpServer } from \"@modelcontextprotocol/sdk/server/mcp.js\";\n\nexport function registerExampleTool(server: McpServer): void {\n server.registerTool(\n \"example_tool\",\n {\n title: \"Example Tool\",\n description: \"An example tool demonstrating the extension pattern\",\n inputSchema: {\n param: z.string().describe(\"Example parameter\")\n },\n outputSchema: { result: z.string() }\n },\n async (args) => {\n // Implementation\n return { content: [{ type: \"text\", text: result }] };\n }\n );\n}\n```\n\n### Updating Documentation\n\nKeep the documentation in `src/everything/docs/` up to date when adding or modifying features. 资料来源：[src/everything/AGENTS.md]()\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Description | Default |\n|----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to memory storage JSONL file | `memory.jsonl` in server directory |\n\n### Claude Desktop Configuration Example\n\n```json\n{\n \"mcpServers\": {\n \"everything\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-everything\"],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n## Development\n\n### Project Structure\n\n```\nsrc/everything/\n├── index.ts # Main entry point\n├── server/\n│ └── index.ts # Server configuration\n├── tools/\n│ ├── index.ts # Tool registry\n│ └── *.ts # Individual tool implementations\n├── resources/\n│ ├── index.ts # Resource registry\n│ └── session.ts # Session resource management\n├── prompts/\n│ └── index.ts # Prompt templates\n└── docs/\n ├── features.md # Feature documentation\n ├── architecture.md # Architecture details\n └── extension.md # Extension guide\n```\n\n### Build Requirements\n\n- **Runtime**: Node.js 22\n- **Target**: ES2022\n- **Module**: Node16\n- **Type Checking**: Strict TypeScript mode\n- **Testing**: vitest with @vitest/coverage-v8 资料来源：[CLAUDE.md]()\n\n### Code Style Guidelines\n\n#### TypeScript Standards\n\n- ES modules with `.js` extension in import paths\n- Strict TypeScript typing for all functions and variables\n- Zod schemas for tool input validation\n- 2-space indentation with trailing commas\n- camelCase for variables/functions, PascalCase for types/classes\n- kebab-case for file names and registered tools/prompts/resources\n- Verb-first tool names (e.g., `get-file-info`, not `file-info`) 资料来源：[CLAUDE.md]()\n\n## Troubleshooting\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| Transport timeout | Ensure proper transport configuration; use Streamable HTTP for better reliability |\n| Resource not found | Check resource URI and registration status |\n| Windows process handling | Use `cmd /c` wrapper for npx commands |\n\n### Debugging\n\nUse the MCP inspector for debugging:\n\n```bash\ncd src/everything\nnpx @modelcontextprotocol/inspector\n```\n\n## License\n\nThe Everything Server is licensed under the MIT License. You are free to use, modify, and distribute the software subject to the terms and conditions of the MIT License. 资料来源：[src/everything/README.md]()\n\n## See Also\n\n- [MCP Specification](https://modelcontextprotocol.io/specification)\n- [MCP Servers Repository](https://github.com/modelcontextprotocol/servers)\n- [MCP SDK Documentation](https://github.com/modelcontextprotocol/sdk)\n\n---\n\n\n\n## Filesystem Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server), [Git Server](#git-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/filesystem/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/package.json)\n- [src/filesystem/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/index.ts)\n- [src/filesystem/lib.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/lib.ts)\n- [src/filesystem/path-validation.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/path-validation.ts)\n- [src/filesystem/roots-utils.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/roots-utils.ts)\n- [src/filesystem/path-utils.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/path-utils.ts)\n- [src/filesystem/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/filesystem/README.md)\n \n\n# Filesystem Server\n\nThe Filesystem Server is an MCP (Model Context Protocol) server implementation that provides secure file system access capabilities to AI models and clients. It enables reading, writing, and managing files and directories within configurable sandboxed environments, with comprehensive security controls through path validation and access restrictions.\n\n## Overview\n\nThe Filesystem Server bridges AI assistants with the local file system by exposing a standardized set of tools that perform file operations. All operations are scoped to user-defined allowed directories, preventing unauthorized access to system files or sensitive locations.\n\n**Key Characteristics:**\n\n| Attribute | Value |\n|-----------|-------|\n| Transport | stdio (default), Streamable HTTP |\n| Language | TypeScript (Node.js) |\n| SDK | @modelcontextprotocol/sdk |\n| License | MIT |\n| Mount Point | `/projects` (Docker default) |\n\n资料来源：[src/filesystem/README.md:1-10]()\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Client] -->|MCP Protocol| B[Filesystem Server]\n B --> C[Tool Handlers]\n C --> D[Path Validation Layer]\n D --> E[Allowed Directories]\n D --> F[File System Operations]\n F --> G[read_text_file]\n F --> H[write_file]\n F --> I[create_directory]\n F --> J[move_file]\n F --> K[list_directory]\n F --> L[search_files]\n E --> M[Security Boundaries]\n```\n\n### Core Components\n\n| Component | File | Responsibility |\n|-----------|------|-----------------|\n| Server Entry | `index.ts` | MCP server initialization, tool registration |\n| Path Validation | `path-validation.ts` | Security checks, allowed directory enforcement |\n| File Operations | `lib.ts` | Core read/write operations implementation |\n| Path Utilities | `path-utils.ts` | Path manipulation and normalization |\n| Roots Utilities | `roots-utils.ts` | MCP roots protocol integration |\n\n资料来源：[src/filesystem/index.ts:1-50]()\n\n## Tool Specifications\n\n### Read Operations\n\nAll read tools have `readOnlyHint: true` annotation, indicating they do not modify system state.\n\n| Tool | Description | Input | Output |\n|------|-------------|-------|--------|\n| `read_text_file` | Read complete file contents as UTF-8 text | `path: string`, optional `head?: number`, `tail?: number` | `content: string` |\n| `read_media_file` | Read image/audio as base64 | `path: string` | `blob: string`, `mimeType: string` |\n| `read_multiple_files` | Read multiple files simultaneously | `paths: string[]` | Combined content with separators |\n| `get_file_info` | Retrieve file metadata | `path: string` | Size, timestamps, type |\n| `list_directory` | List directory contents | `path: string` | Files and subdirectories with [FILE]/[DIR] prefixes |\n| `list_directory_with_sizes` | List with file sizes | `path: string`, optional `sortBy: \"name\" \\| \"size\"` | Detailed listing with sizes |\n| `directory_tree` | Recursive directory structure | `path: string` | Hierarchical tree view |\n| `search_files` | Find files by pattern | `path: string`, `pattern: string` | Matching file paths |\n| `list_allowed_directories` | Show permitted paths | none | List of allowed directories |\n\n资料来源：[src/filesystem/README.md:15-30]()\n\n### Write Operations\n\n| Tool | readOnlyHint | idempotentHint | destructiveHint | Description |\n|------|--------------|----------------|-----------------|-------------|\n| `write_file` | false | true | true | Create or overwrite files |\n| `edit_file` | false | false | false | Selective edits with diff preview |\n| `create_directory` | false | true | false | Create directories (idempotent) |\n| `move_file` | false | false | true | Move/rename files |\n\n资料来源：[src/filesystem/README.md:32-40]()\n\n### Annotation Semantics\n\n```mermaid\ngraph LR\n A[readOnlyHint] --> B{true?}\n B -->|Yes| C[Read operations
No state changes]\n B -->|No| D[destructiveHint & idempotentHint
become meaningful]\n D --> E[idempotentHint: true
Re-running safe]\n D --> F[idempotentHint: false
May fail on retry]\n D --> G[destructiveHint: true
Cannot undo]\n```\n\n> **Note:** `idempotentHint` and `destructiveHint` are meaningful only when `readOnlyHint` is `false`, as defined by the MCP specification.\n\n资料来源：[src/filesystem/README.md:42-44]()\n\n## Security Model\n\nThe Filesystem Server implements multiple security layers to prevent unauthorized file system access.\n\n### Path Validation\n\n```mermaid\ngraph TD\n A[Incoming Path] --> B{Normalize Path}\n B --> C{Relative to allowed directory?}\n C -->|No| D[Reject with error]\n C -->|Yes| E{Symlink traversal safe?}\n E -->|No| D\n E -->|Yes| F[Allow operation]\n```\n\n**Validation Rules:**\n\n1. All paths are normalized before comparison\n2. Symbolic links are resolved and checked against allowed directories\n3. Attempting to escape allowed directories via `..` or symlinks is blocked\n4. Operations are rejected if the resolved path falls outside permitted boundaries\n\n资料来源：[src/filesystem/path-validation.ts:1-30]()\n\n### Allowed Directories Configuration\n\n| Deployment Method | Configuration |\n|-------------------|---------------|\n| Docker | Mount directories to `/projects` |\n| NPX | Pass directories as arguments |\n| Programmatic | Set allowed directories at initialization |\n\n**Docker Example:**\n```bash\ndocker run -i --rm \\\n --mount type=bind,src=/host/path,dst=/projects/path \\\n mcp/filesystem /projects\n```\n\n**NPX Example:**\n```bash\nnpx -y @modelcontextprotocol/server-filesystem \\\n /Users/username/Desktop \\\n /path/to/allowed/dir\n```\n\n资料来源：[src/filesystem/README.md:55-75]()\n\n## Installation Methods\n\n### Docker\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"--mount\", \"type=bind,src=${workspaceFolder},dst=/projects/workspace\",\n \"mcp/filesystem\",\n \"/projects\"\n ]\n }\n }\n}\n```\n\n### NPX (Unix/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-filesystem\",\n \"${workspaceFolder}\"\n ]\n }\n }\n}\n```\n\n### NPX (Windows)\n\n```json\n{\n \"mcpServers\": {\n \"filesystem\": {\n \"command\": \"cmd\",\n \"args\": [\n \"/c\",\n \"npx\",\n \"-y\",\n \"@modelcontextprotocol/server-filesystem\",\n \"${workspaceFolder}\"\n ]\n }\n }\n}\n```\n\n资料来源：[src/filesystem/README.md:55-95]()\n\n## Tool Detailed Reference\n\n### read_text_file\n\nReads complete file contents as UTF-8 text regardless of file extension.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Absolute or relative path to file |\n| `head` | number | No | Return only first N lines |\n| `tail` | number | No | Return only last N lines |\n\n**Constraints:** Cannot specify both `head` and `tail` simultaneously.\n\n资料来源：[src/filesystem/README.md:98-110]()\n\n### read_media_file\n\nReads image or audio files and returns base64-encoded data with MIME type.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Path to media file |\n\n**Returns:**\n- `blob`: Base64-encoded file content\n- `mimeType`: Corresponding MIME type (e.g., `image/png`, `audio/mpeg`)\n\n资料来源：[src/filesystem/README.md:112-120]()\n\n### edit_file\n\nPerforms selective edits using pattern matching with indentation preservation.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | File to edit |\n| `edits` | array | Yes | List of edit operations |\n| `dryRun` | boolean | No | Preview without applying (default: false) |\n\n**Edit Operation Schema:**\n```typescript\n{\n oldText: string; // Text to search for (can be substring)\n newText: string; // Replacement text\n}\n```\n\n**Features:**\n- Line-based and multi-line content matching\n- Whitespace normalization with indentation preservation\n- Git-style diff output with context\n- Preview changes with dry run mode\n\n**Best Practice:** Always use `dryRun: true` first to preview changes before applying them.\n\n资料来源：[src/filesystem/README.md:132-150]()\n\n### move_file\n\nMoves or renames files and directories.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `source` | string | Yes | Source file path |\n| `destination` | string | Yes | Destination path |\n\n**Behavior:**\n- Fails if destination already exists\n- Deletes source file after successful move\n- `destructiveHint: true` - operation cannot be automatically undone\n\n资料来源：[src/filesystem/README.md:165-175]()\n\n### list_directory_with_sizes\n\nLists directory contents with detailed file size information.\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `path` | string | Yes | Directory path to list |\n| `sortBy` | string | No | Sort by `\"name\"` or `\"size\"` (default: `\"name\"`) |\n\n**Returns:** Detailed listing including file sizes and summary statistics (total files, directories, combined size).\n\n资料来源：[src/filesystem/README.md:155-163]()\n\n## Building from Source\n\n### Prerequisites\n\n- Node.js 22+\n- npm or docker\n\n### Docker Build\n\n```bash\ndocker build -t mcp/filesystem -f src/filesystem/Dockerfile .\n```\n\n### Local Development\n\n```bash\ncd src/filesystem\nnpm install\nnpm run build\n```\n\n资料来源：[src/filesystem/README.md:45-50]()\n\n## MCP Protocol Integration\n\n### Resources\n\nThe server may expose allowed directories as MCP Resources with the `roots://` URI scheme.\n\n```mermaid\nsequenceDiagram\n participant Client\n participant Server\n participant FileSystem\n Client->>Server: List Roots\n Server->>Server: Check roots-utils\n Server-->>Client: Allowed directory list\n Client->>Server: Tool call (e.g., read_file)\n Server->>FileSystem: Operation\n FileSystem-->>Server: Result\n Server-->>Client: Tool response\n```\n\n资料来源：[src/filesystem/roots-utils.ts:1-25]()\n\n## License\n\nThe Filesystem Server is licensed under the **MIT License**. This permits free use, modification, and distribution subject to MIT License terms.\n\n资料来源：[src/filesystem/README.md:51-54]()\n\n---\n\n\n\n## Memory Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/memory/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/package.json)\n- [src/memory/index.ts](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/index.ts)\n- [src/memory/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md)\n \n\n# Memory Server\n\nThe Memory Server is an MCP (Model Context Protocol) server implementation that provides persistent knowledge graph capabilities for AI assistants like Claude. It enables AI models to maintain long-term memory across conversations by storing and retrieving structured information about users, entities, relationships, and events.\n\n## Overview\n\nThe Memory Server implements a knowledge graph storage system that allows AI assistants to:\n\n- Store information about users and their characteristics\n- Maintain relationships between entities\n- Retrieve relevant context from previous interactions\n- Update memory dynamically during conversations\n\n资料来源：[src/memory/package.json:3]()\n\n```mermaid\ngraph TD\n A[Claude Conversation] --> B[Memory Server]\n B --> C[Knowledge Graph Storage]\n C --> D[JSONL File Storage]\n \n B --> E[Memory Retrieval]\n E --> F[Return Entities & Relations]\n \n B --> G[Memory Update]\n G --> H[Create/Update Entities]\n G --> I[Create Relations]\n I --> C\n```\n\n## Architecture\n\nThe Memory Server is built using the Model Context Protocol SDK and stores data in a JSONL (JSON Lines) format file. The server provides tools for managing a graph-based knowledge structure with entities and relations.\n\n资料来源：[src/memory/package.json:1-2]()\n\n### Core Components\n\n| Component | Description |\n|-----------|-------------|\n| Knowledge Graph | Graph-based storage for entities and relationships |\n| JSONL Storage | Persistent file storage in JSON Lines format |\n| MCP SDK Integration | Uses `@modelcontextprotocol/sdk` for MCP protocol support |\n| Memory API | Tools for CRUD operations on memory entities |\n\n## Installation\n\n### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"-v\",\n \"claude-memory:/app/dist\",\n \"--rm\",\n \"mcp/memory\"\n ]\n }\n }\n}\n```\n\n资料来源：[src/memory/README.md]()\n\n### NPX Installation (Unix/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n### NPX Installation (Windows)\n\nWindows requires using `cmd` with `/c` flag to launch `npx`:\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"cmd\",\n \"args\": [\n \"/c\",\n \"npx\",\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Description | Default |\n|----------|-------------|---------|\n| `MEMORY_FILE_PATH` | Path to the memory storage JSONL file | `memory.jsonl` in server directory |\n\n### Custom Storage Path Example\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ],\n \"env\": {\n \"MEMORY_FILE_PATH\": \"/path/to/custom/memory.jsonl\"\n }\n }\n }\n}\n```\n\n资料来源：[src/memory/README.md]()\n\n## Memory Operations\n\nThe Memory Server supports the following core operations:\n\n### User Identification\n\nThe system assumes interaction with a default user and proactively identifies them if not already known:\n\n```\n- Assume interaction with default_user\n- Proactively identify user if not already done\n```\n\n### Memory Retrieval\n\nAt the start of each conversation, the system retrieves relevant information from the knowledge graph:\n\n```\n- Begin chat by saying \"Remembering...\"\n- Retrieve all relevant information from knowledge graph\n- Reference knowledge graph as \"memory\"\n```\n\n### Memory Categories\n\nDuring conversation, the system stores new information in these categories:\n\n| Category | Description | Examples |\n|----------|-------------|----------|\n| Basic Identity | Personal identifiers | Age, gender, location, job title, education |\n| Behaviors | User patterns | Interests, habits, preferences |\n| Preferences | Communication style | Preferred language, communication style |\n| Goals | Aspirations | Goals, targets, objectives |\n| Relationships | Connections | Personal and professional relationships (up to 3 degrees) |\n\n资料来源：[src/memory/README.md]()\n\n### Memory Update Process\n\nWhen new information is gathered during interaction:\n\n```mermaid\ngraph TD\n A[New Information Gathered] --> B{Is it recurring?}\n B -->|Organization| C[Create Entity for Organization]\n B -->|Person| D[Create Entity for Person]\n B -->|Event| E[Create Entity for Event]\n C --> F[Connect to Current Entities]\n D --> F\n E --> F\n F --> G[Create Relations]\n G --> H[Update Knowledge Graph]\n```\n\nThe update process:\n\n1. Creates entities for recurring organizations, people, and significant events\n2. Connects new entities to existing entities using relations\n3. Returns requested entities and their relations\n4. Silently skips non-existent nodes\n\n## Usage with Claude Desktop\n\n### Setup Configuration\n\nAdd the following to your `claude_desktop_config.json`:\n\n#### Docker Configuration\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"-v\", \"claude-memory:/app/dist\", \"--rm\", \"mcp/memory\"]\n }\n }\n}\n```\n\n#### NPX Configuration\n\n```json\n{\n \"mcpServers\": {\n \"memory\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@modelcontextprotocol/server-memory\"\n ]\n }\n }\n}\n```\n\n### System Prompt Configuration\n\nFor optimal memory utilization, configure a custom prompt in the \"Custom Instructions\" field of your Claude.ai Project:\n\n```\nFollow these steps for each interaction:\n\n1. User Identification:\n - Assume interaction with default_user\n - Proactively identify if not already known\n\n2. Memory Retrieval:\n - Begin chat by saying \"Remembering...\"\n - Retrieve all relevant information from knowledge graph\n - Reference knowledge graph as \"memory\"\n\n3. Memory Categories:\n While conversing, be attentive to:\n a) Basic Identity (age, gender, location, job title, etc.)\n b) Behaviors (interests, habits, etc.)\n c) Preferences (communication style, preferred language)\n d) Goals (goals, targets, aspirations)\n e) Relationships (personal/professional up to 3 degrees)\n\n4. Memory Update:\n If new information gathered:\n a) Create entities for recurring organizations, people, events\n b) Connect them to current entities using relations\n```\n\n资料来源：[src/memory/README.md]()\n\n## Technical Specifications\n\n### Package Information\n\n| Property | Value |\n|----------|-------|\n| Package Name | `@modelcontextprotocol/server-memory` |\n| Version | 0.6.3 |\n| License | MIT License |\n| MCP Name | `io.github.modelcontextprotocol/server-memory` |\n| SDK Dependency | `@modelcontextprotocol/sdk: ^1.29.0` |\n\n资料来源：[src/memory/package.json:1-11]()\n\n### Build Configuration\n\n```json\n{\n \"scripts\": {\n \"build\": \"tsc && shx chmod +x dist/*.js\",\n \"prepare\": \"npm run build\",\n \"watch\": \"tsc --watch\",\n \"test\": \"vitest run --coverage\"\n }\n}\n```\n\n资料来源：[src/memory/package.json:18-22]()\n\n## VS Code Installation\n\nQuick installation is available through one-click buttons in the VS Code marketplace:\n\n- **NPX Installation**: For npm-based installations\n- **VS Code Insiders**: Separate button for Insiders version\n\nThese buttons provide streamlined configuration without manual JSON editing.\n\n资料来源：[src/memory/README.md]()\n\n## Data Model\n\n### Entity Structure\n\nEntities in the knowledge graph include:\n\n- **Organizations**: Recurring companies, teams, institutions\n- **People**: Users, contacts, individuals mentioned\n- **Events**: Significant occurrences, meetings, milestones\n\n### Relation Types\n\nRelations connect entities with semantic meaning:\n\n- Personal relationships (family, friends, colleagues)\n- Professional relationships (team members, stakeholders)\n- Temporal relationships (event connections)\n- Hierarchical relationships (org charts, reporting structures)\n\n### Return Values\n\n| Operation | Returns |\n|-----------|---------|\n| Retrieval | Requested entities and their relations |\n| Non-existent nodes | Silently skipped |\n\n## Development\n\n### Running from Source\n\n1. Clone the repository\n2. Navigate to `src/memory`\n3. Install dependencies\n4. Build using `npm run build`\n\n### Testing\n\n```bash\ncd src/memory\nnpm test\n```\n\n## Summary\n\nThe Memory Server provides a flexible, knowledge-graph-based memory system for AI assistants. It enables persistent storage of user information, entity relationships, and conversation context across multiple sessions. By integrating with the Model Context Protocol, it offers standardized MCP tool interfaces for memory operations while maintaining data in a portable JSONL format.\n\nKey benefits include:\n\n- **Persistent Memory**: Information persists across sessions\n- **Graph-based Relationships**: Rich entity connections\n- **Flexible Storage**: JSONL format allows easy backup and inspection\n- **MCP Standard**: Compatible with any MCP-compliant client\n\n---\n\n\n\n## Git Server\n\n### 相关页面\n\n相关主题：[Filesystem Server](#filesystem-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/git/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/git/pyproject.toml)\n- [src/git/src/mcp_server_git/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/git/src/mcp_server_git/server.py)\n- [src/git/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/git/README.md)\n\n**Note:** The Git Server source files (src/git/) are not included in the current repository context provided. The following documentation is based on the general MCP server patterns observed in other servers within this repository (fetch, time, filesystem, memory, etc.) and the CLAUDE.md contributing guidelines.\n\nFor accurate Git Server documentation, please provide the contents of the src/git/ directory files.\n \n\n# Git Server\n\n> **Documentation Status**: The Git Server (`src/git/`) source files were not included in the current repository context. This page provides general information based on MCP server patterns observed in this repository. For accurate implementation details, refer to the actual source files listed above.\n\n## Overview\n\nThe Git Server is a Model Context Protocol (MCP) server implementation that provides Git repository interaction capabilities to AI assistants and other MCP clients. Based on the project's architecture patterns, this server follows the same conventions as other MCP servers in the `modelcontextprotocol/servers` repository.\n\nThe server enables AI models to perform Git operations such as viewing history, examining commits, browsing branches, and analyzing repository state through standardized MCP tool interfaces.\n\n## Architecture\n\nBased on the patterns observed in other servers within this repository, the Git Server follows a modular architecture:\n\n```mermaid\ngraph TD\n A[MCP Client] -->|JSON-RPC| B[Git Server Entry Point]\n B --> C[Tool Handlers]\n C --> D[Git Operations Layer]\n D --> E[Local Git Repository]\n B --> F[Resource Providers]\n F --> G[Repository Resources]\n```\n\n## Server Structure\n\n### Directory Layout\n\nFollowing the repository conventions (per `CLAUDE.md`):\n\n```\nsrc/git/\n├── pyproject.toml # Python package configuration\n├── src/\n│ └── mcp_server_git/\n│ ├── __init__.py\n│ └── server.py # Main server implementation\n├── README.md # Server-specific documentation\n└── tests/ # Test suite\n```\n\n### Package Configuration\n\nThe server uses **hatchling** as its build system, consistent with other Python servers in this repository. Package configuration is defined in `pyproject.toml`.\n\nBased on patterns from other servers:\n- Package manager: **uv** (not pip) - 资料来源：[CLAUDE.md]()\n- Python version: **>= 3.10** (per-server `.python-version` file) - 资料来源：[CLAUDE.md]()\n- Type checking: **pyright** - 资料来源：[CLAUDE.md]()\n- Linting: **ruff** - 资料来源：[CLAUDE.md]()\n\n## Installation Methods\n\nBased on the standard MCP server installation patterns in this repository:\n\n### Using uvx (Recommended)\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-git\"]\n }\n }\n}\n```\n\n### Using pip\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_git\"]\n }\n }\n}\n```\n\n### Using Docker\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/git\"]\n }\n }\n}\n```\n\n## Configuration\n\n### Claude Desktop Configuration\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-git\"]\n }\n }\n}\n```\n\nOn Windows, wrap with `cmd /c`:\n\n```json\n{\n \"mcpServers\": {\n \"git\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"uvx\", \"mcp-server-git\"]\n }\n }\n}\n```\n\n## Development\n\n### Building\n\nDocker build:\n\n```bash\ndocker build -t mcp/git -f src/git/Dockerfile .\n```\n\n### Testing\n\n```bash\ncd src/git && uv sync --frozen --all-extras --dev\nuv run pytest\n```\n\n### Type Checking\n\n```bash\nuv run pyright\n```\n\n### Linting\n\n```bash\nuv run ruff check .\n```\n\n## Tool Interface\n\nBased on MCP server conventions, the Git Server exposes tools via the MCP protocol. Common Git operations likely include:\n\n| Tool Name | Purpose | Read Only |\n|-----------|---------|-----------|\n| `get-commit` | Retrieve commit details | Yes |\n| `list-branches` | List repository branches | Yes |\n| `get-file-history` | View file change history | Yes |\n| `get-diff` | Show changes between commits | Yes |\n| `list-tags` | List repository tags | Yes |\n| `get-repository-info` | Retrieve repository metadata | Yes |\n\n## Comparison with Other MCP Servers\n\nThe Git Server follows the same architectural patterns as other servers in this repository:\n\n| Aspect | Git Server | Fetch Server | Time Server | Memory Server |\n|--------|------------|--------------|-------------|---------------|\n| Language | Python | Python | Python | TypeScript |\n| Entry Point | `mcp_server_git` | `mcp_server_fetch` | `mcp_server_time` | `@modelcontextprotocol/server-memory` |\n| Transport | stdio | stdio | stdio | stdio |\n| Build System | hatchling | hatchling | hatchling | npm |\n| License | MIT | MIT | MIT | MIT |\n\n## Contributing\n\nContributions to the Git Server follow the general guidelines defined in the repository's `CLAUDE.md`:\n\n- **Accepted**: Bug fixes, usability improvements, enhancements demonstrating MCP protocol features\n- **Code Style**: Python typing with type hints enforced via pyright\n- **Testing**: pytest with proper async patterns\n- **Linting**: ruff for code style enforcement\n\nFor contribution guidelines, see: https://github.com/modelcontextprotocol/servers\n\n## License\n\nThis MCP server is licensed under the **MIT License**, consistent with other servers in the repository. Users are free to use, modify, and distribute the software subject to MIT License terms.\n\n---\n\n\n\n## Time Server\n\n### 相关页面\n\n相关主题：[Fetch Server](#fetch-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/time/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md)\n- [src/time/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/time/pyproject.toml)\n- [src/time/src/mcp_server_time/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/time/src/mcp_server_time/server.py)\n- [CLAUDE.md](https://github.com/modelcontextprotocol/servers/blob/main/CLAUDE.md)\n- [README.md](https://github.com/modelcontextprotocol/servers/blob/main/README.md)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n \n\n# Time Server\n\nThe Time Server is a Python-based MCP (Model Context Protocol) server that provides timezone-aware time retrieval and conversion capabilities. It enables AI assistants and MCP clients to query current time in any timezone and perform time conversions between different time zones.\n\n## Overview\n\nThe Time Server exposes two primary tools that allow clients to:\n\n- Retrieve the current time for a specified timezone\n- Convert times between different timezones\n\nThe server automatically detects the system's timezone by default but allows customization through command-line arguments. It follows the MCP specification for tool definitions and responses.\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Client] -->|Tool Request| B[Time Server]\n B -->|Execute| C[get_current_time Tool]\n B -->|Execute| D[convert_time Tool]\n C -->|Query| E[System Timezone]\n C -->|Query| F[Specified Timezone]\n D -->|Calculate| G[Timezone Conversion]\n G --> H[Time Difference]\n B -->|JSON Response| A\n```\n\n## Tools\n\n### get_current_time\n\nRetrieves the current time for a specified timezone.\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `timezone` | string | Yes | IANA timezone identifier (e.g., \"Europe/Warsaw\", \"Asia/Tokyo\") |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"get_current_time\",\n \"arguments\": {\n \"timezone\": \"Europe/Warsaw\"\n }\n}\n```\n\n**Response:**\n\n```json\n{\n \"timezone\": \"Europe/Warsaw\",\n \"datetime\": \"2024-01-01T13:00:00+01:00\",\n \"is_dst\": false\n}\n```\n\n### convert_time\n\nConverts a time from one timezone to another.\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `source_timezone` | string | Yes | Source IANA timezone identifier |\n| `target_timezone` | string | Yes | Target IANA timezone identifier |\n| `time` | string | Yes | Time in HH:MM format |\n\n**Example Request:**\n\n```json\n{\n \"name\": \"convert_time\",\n \"arguments\": {\n \"source_timezone\": \"America/New_York\",\n \"time\": \"16:30\",\n \"target_timezone\": \"Asia/Tokyo\"\n }\n}\n```\n\n**Response:**\n\n```json\n{\n \"source\": {\n \"timezone\": \"America/New_York\",\n \"datetime\": \"2024-01-01T12:30:00-05:00\",\n \"is_dst\": false\n },\n \"target\": {\n \"timezone\": \"Asia/Tokyo\",\n \"datetime\": \"2024-01-01T12:30:00+09:00\",\n \"is_dst\": false\n },\n \"time_difference\": \"+13.0h\"\n}\n```\n\n## Installation\n\nThe Time Server supports multiple installation methods.\n\n### Using uvx (Recommended)\n\n```bash\nuvx mcp-server-time\n```\n\n### Using pip\n\n```bash\npip install mcp-server-time\npython -m mcp_server_time\n```\n\n### Using Docker\n\n```bash\ncd src/time\ndocker build -t mcp/time .\ndocker run -i --rm mcp/time\n```\n\n## Configuration\n\n### Claude Desktop\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n**Using pip:**\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_time\"]\n }\n }\n}\n```\n\n### VS Code\n\nUse the one-click installation buttons available in the README, or configure manually:\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n### Zed Editor\n\n```json\n{\n \"context_servers\": {\n \"mcp-server-time\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-time\"]\n }\n }\n}\n```\n\n### Docker Configuration\n\n```json\n{\n \"mcpServers\": {\n \"time\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"-e\", \"LOCAL_TIMEZONE\", \"mcp/time\"]\n }\n }\n}\n```\n\n## Customization\n\n### System Timezone Override\n\nBy default, the server automatically detects your system's timezone. Override this using the `--local-timezone` argument:\n\n```json\n{\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_time\", \"--local-timezone=America/New_York\"]\n}\n```\n\n### Environment Variable (Docker)\n\nPass the timezone via the `LOCAL_TIMEZONE` environment variable when using Docker:\n\n```bash\ndocker run -i --rm -e LOCAL_TIMEZONE=Europe/London mcp/time\n```\n\n## Debugging\n\nUse the MCP Inspector for debugging:\n\n**For uvx installations:**\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-time\n```\n\n**For local development:**\n\n```bash\ncd path/to/servers/src/time\nnpx @modelcontextprotocol/inspector uv run mcp-server-time\n```\n\n## Example Interactions\n\n### Query Current Time\n\n| Question | Description |\n|----------|-------------|\n| \"What time is it now?\" | Uses system timezone |\n| \"What time is it in Tokyo?\" | Queries Asia/Tokyo timezone |\n| \"What time is it in Europe/Warsaw?\" | Queries Europe/Warsaw timezone |\n\n### Time Conversion\n\n| Question | Description |\n|----------|-------------|\n| \"When it's 4 PM in New York, what time is it in London?\" | Cross-timezone conversion |\n| \"Convert 9:30 AM Tokyo time to New York time\" | Specific time conversion |\n\n## Data Model\n\n### Time Response Schema\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `timezone` | string | IANA timezone identifier |\n| `datetime` | string | ISO 8601 formatted datetime with timezone offset |\n| `is_dst` | boolean | Whether Daylight Saving Time is active |\n\n### Conversion Response Schema\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `source` | object | Source timezone info with datetime |\n| `target` | object | Target timezone info with datetime |\n| `time_difference` | string | Formatted difference (e.g., \"+13.0h\") |\n\n## License\n\nThe Time Server is licensed under the **MIT License**, allowing free use, modification, and distribution subject to the terms and conditions specified in the LICENSE file.\n\n## See Also\n\n- [Memory Server](src/memory/README.md) - Persistent memory storage\n- [Fetch Server](src/fetch/README.md) - HTTP fetch capabilities\n- [Filesystem Server](src/filesystem/README.md) - File operations\n- [MCP Specification](https://modelcontextprotocol.io/specification) - Protocol documentation\n\n---\n\n\n\n## Fetch Server\n\n### 相关页面\n\n相关主题：[Time Server](#time-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/fetch/pyproject.toml](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/pyproject.toml)\n- [src/fetch/src/mcp_server_fetch/server.py](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/src/mcp_server_fetch/server.py)\n- [src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n \n\n# Fetch Server\n\nThe Fetch Server is a Model Context Protocol (MCP) server that provides web content fetching capabilities. It enables Large Language Models (LLMs) to retrieve and process content from web pages, converting HTML to markdown for easier consumption.\n\n## Overview\n\nThe Fetch Server acts as an intermediary between LLMs and web content, handling the complexities of HTTP requests, HTML parsing, and markdown conversion. This abstraction allows models to access web information without needing direct HTTP implementation capabilities.\n\n```mermaid\ngraph TD\n A[\"LLM / MCP Client\"] --> B[\"Fetch Server\"]\n B --> C[\"HTTP Request\"]\n C --> D[\"Web Server\"]\n D --> E[\"HTML Response\"]\n E --> B\n B --> F[\"Markdown Conversion\"]\n F --> A\n```\n\n### Key Capabilities\n\n| Capability | Description |\n|------------|-------------|\n| URL Fetching | Retrieve content from any publicly accessible URL |\n| Markdown Conversion | Transform HTML into clean, readable markdown |\n| Content Truncation | Limit response size with `max_length` parameter |\n| Chunked Reading | Use `start_index` to read content in portions |\n| Raw Content Access | Bypass markdown conversion when needed |\n\n> [!CAUTION]\n> This server can access local/internal IP addresses and may represent a security risk. Exercise caution when using this MCP server to ensure it does not expose any sensitive data.\n\n## Tools\n\n### fetch\n\nThe primary tool provided by the Fetch Server for retrieving web content.\n\n```typescript\n{\n name: \"fetch\",\n description: \"Fetches a URL from the internet and extracts its contents as markdown.\",\n inputSchema: {\n url: string, // required\n max_length?: number, // optional, default: 5000\n start_index?: number, // optional, default: 0\n raw?: boolean // optional, default: false\n }\n}\n```\n\n#### Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `url` | string | Yes | - | URL to fetch |\n| `max_length` | integer | No | 5000 | Maximum number of characters to return |\n| `start_index` | integer | No | 0 | Start content from this character index |\n| `raw` | boolean | No | false | Get raw content without markdown conversion |\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n#### Usage Example\n\n```json\n{\n \"name\": \"fetch\",\n \"arguments\": {\n \"url\": \"https://example.com/article\",\n \"max_length\": 10000,\n \"start_index\": 0\n }\n}\n```\n\n#### Response Format\n\n```json\n{\n \"content\": [\n {\n \"type\": \"text\",\n \"text\": \"# Article Title\\n\\nConverted markdown content...\"\n }\n ]\n}\n```\n\n### Chunked Reading\n\nThe fetch tool truncates responses by default. By using the `start_index` argument, you can specify where to start the content extraction, enabling models to read a webpage in chunks until they find the information they need.\n\n```mermaid\ngraph LR\n A[\"Initial Request
start_index=0\"] --> B[\"First Chunk\"]\n B --> C{\"Need More?\"}\n C -->|Yes| D[\"Request with
start_index=N\"]\n D --> B\n C -->|No| E[\"Complete\"]\n```\n\n## Installation\n\nThe Fetch Server supports multiple installation methods. Choose the one that best fits your environment.\n\n### Using uv (Recommended)\n\nWhen using [`uv`](https://docs.astral.sh/uv/), no specific installation is needed. Use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run the server:\n\n```bash\nuvx mcp-server-fetch\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n### Using pip\n\nAlternatively, install via pip:\n\n```bash\npip install mcp-server-fetch\n```\n\nAfter installation, run as a script:\n\n```bash\npython -m mcp_server_fetch\n```\n\n### Using Docker\n\n```bash\ndocker run -i --rm mcp/fetch\n```\n\n### Optional Dependency\n\nOptionally, install Node.js for a more robust HTML simplifier:\n\n```bash\n# This will cause the fetch server to use a different HTML simplifier\n# that is more robust for complex web pages\n```\n\n## Configuration\n\n### Claude.app Configuration\n\nAdd the following to your Claude settings:\n\n#### Using uvx\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"]\n }\n }\n}\n```\n\n#### Using Docker\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"mcp/fetch\"]\n }\n }\n}\n```\n\n#### Using pip\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_fetch\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n### VS Code Configuration\n\nFor quick installation, use the one-click install buttons available in the README:\n\n- **Install with UV in VS Code** - Uses `uvx mcp-server-fetch`\n- **Install with UV in VS Code Insiders** - Uses `uvx mcp-server-fetch` (insiders version)\n- **Install with Docker in VS Code** - Uses `docker` command\n\n## Customization Options\n\n### robots.txt\n\nBy default, the server obeys a website's `robots.txt` file if the request came from the model (via a tool), but not if the request was user-initiated (via a prompt). This can be disabled:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--ignore-robots-txt\"]\n }\n }\n}\n```\n\n### User-Agent\n\nThe server uses different user-agents based on request origin:\n\n| Request Origin | User-Agent |\n|---------------|------------|\n| Model (via tool) | `ModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)` |\n| User (via prompt) | `ModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)` |\n\nCustomize the user-agent:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--user-agent=YourUserAgent\"]\n }\n }\n}\n```\n\n### Proxy Support\n\nConfigure the server to use a proxy:\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\", \"--proxy-url=http://proxy.example.com:8080\"]\n }\n }\n}\n```\n\n资料来源：[src/fetch/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md)\n\n## Windows Configuration\n\nIf experiencing timeout issues on Windows, set the `PYTHONIOENCODING` environment variable to ensure proper character encoding:\n\n### Windows with uvx\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n### Windows with pip\n\n```json\n{\n \"mcpServers\": {\n \"fetch\": {\n \"command\": \"python\",\n \"args\": [\"-m\", \"mcp_server_fetch\"],\n \"env\": {\n \"PYTHONIOENCODING\": \"utf-8\"\n }\n }\n }\n}\n```\n\n## Debugging\n\nUse the MCP inspector to debug the server:\n\n### For uvx installations\n\n```bash\nnpx @modelcontextprotocol/inspector uvx mcp-server-fetch\n```\n\n### For development\n\n```bash\ncd path/to/servers/src/fetch\nnpx @modelcontextprotocol/inspector uv run mcp-server-fetch\n```\n\n## Prompts\n\nThe Fetch Server includes a prompt template:\n\n### fetch\n\n- **Purpose**: Fetch a URL and extract its contents as markdown\n- **Arguments**:\n - `url` (string, required): URL to fetch\n\n## Architecture\n\n```mermaid\ngraph TD\n subgraph \"Client Layer\"\n A[\"MCP Client
(Claude, VS Code, etc.)\"]\n end\n \n subgraph \"Fetch Server\"\n B[\"Request Handler\"]\n C[\"robots.txt Validator\"]\n D[\"User-Agent Manager\"]\n E[\"HTTP Client\"]\n F[\"HTML Parser\"]\n G[\"Markdown Converter\"]\n end\n \n subgraph \"External\"\n H[\"Target Web Server\"]\n end\n \n A --> B\n B --> C\n C --> D\n D --> E\n E --> H\n H --> E\n E --> F\n F --> G\n G --> A\n```\n\n## License\n\nThis MCP server is licensed under the MIT License. You are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License.\n\n## Contributing\n\nContributions are welcome to help expand and improve mcp-server-fetch. Whether you want to add new tools, enhance existing functionality, or improve documentation, your input is valuable.\n\nFor examples of other MCP servers and implementation patterns, see the [main MCP servers repository](https://github.com/modelcontextprotocol/servers).\n\nPull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements.\n\n---\n\n\n\n## Sequential Thinking Server\n\n### 相关页面\n\n相关主题：[Everything Server](#everything-server)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [src/sequentialthinking/package.json](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n- [src/sequentialthinking/README.md](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n \n\n# Sequential Thinking Server\n\nThe Sequential Thinking Server is an MCP (Model Context Protocol) server implementation that provides a structured, step-by-step thinking tool for dynamic and reflective problem-solving. It enables AI assistants to break down complex problems into manageable steps, revise thinking as understanding deepens, and branch into alternative reasoning paths.\n\n## Overview\n\nThe server exposes a single powerful tool called `sequential_thinking` that facilitates detailed, iterative reasoning processes. Unlike one-shot responses, this tool allows models to maintain context over multiple thought steps, adjust their approach dynamically, and explore branching reasoning paths when needed.\n\n**Key Characteristics:**\n\n| Attribute | Value |\n|-----------|-------|\n| Package Name | `@modelcontextprotocol/server-sequential-thinking` |\n| Version | 0.6.2 |\n| License | MIT |\n| Transport | stdio (default), HTTP+SSE (deprecated), Streamable HTTP |\n| Runtime | Node.js / TypeScript |\n\n资料来源：[package.json:1-6](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## Features\n\nThe Sequential Thinking Server provides the following capabilities:\n\n- **Step-by-Step Decomposition** — Break complex problems into manageable thought steps\n- **Iterative Refinement** — Revise and refine thoughts as understanding deepens\n- **Branching Reasoning** — Fork into alternative paths of reasoning from any thought\n- **Dynamic Adjustment** — Adjust the total number of thoughts needed on the fly\n- **Hypothesis Verification** — Generate and verify solution hypotheses through structured thinking\n- **Thought Logging** — Optional logging of thought information for debugging and audit\n\n资料来源：[README.md:1-20](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Tool Specification\n\n### sequential_thinking\n\nThe primary tool provided by this server for structured problem-solving.\n\n**Input Schema:**\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `thought` | string | Yes | The current thinking step content |\n| `nextThoughtNeeded` | boolean | Yes | Whether another thought step is needed |\n| `thoughtNumber` | integer | Yes | Current thought number in the sequence |\n| `totalThoughts` | integer | Yes | Estimated total thoughts needed |\n| `isRevision` | boolean | No | Whether this revises a previous thought |\n| `revisesThought` | integer | No | Which thought number is being reconsidered |\n| `branchFromThought` | integer | No | Branching point thought number |\n| `branchId` | string | No | Unique identifier for this reasoning branch |\n| `needsMoreThoughts` | boolean | No | Indicates if more thoughts are required |\n\n资料来源：[README.md:35-53](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n**Tool Annotations:**\n\n| Annotation | Value | Description |\n|------------|-------|-------------|\n| `readOnlyHint` | false | This tool modifies thought state |\n| `idempotentHint` | false | Repeated calls have cumulative effect |\n| `destructiveHint` | false | Does not destroy external resources |\n\n## Architecture\n\n```mermaid\ngraph TD\n A[MCP Host Application] -->|stdio / HTTP| B[Sequential Thinking Server]\n B --> C[sequential_thinking Tool]\n C --> D[Thought State Management]\n D --> E[Optional Logging]\n \n F[Thought Input] -->|thought| C\n F -->|nextThoughtNeeded| C\n F -->|thoughtNumber| C\n F -->|totalThoughts| C\n \n C -->|revision| G[Revises Previous Thought]\n C -->|branch| H[Alternative Branch Created]\n C -->|continuation| I[Next Thought Prompt]\n```\n\n### Component Overview\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ MCP Host (Claude Desktop, VS Code) │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Sequential Thinking Server │\n│ ┌─────────────────────────────────────────────────────┐ │\n│ │ Tool Handler: sequential_thinking │ │\n│ │ - Validates input schema │ │\n│ │ - Processes thought parameters │ │\n│ │ - Manages thought state │ │\n│ └─────────────────────────────────────────────────────┘ │\n│ │ │\n│ ┌─────────────────────────────────────────────────────┐ │\n│ │ Logging Module (optional) │ │\n│ │ - Controlled by DISABLE_THOUGHT_LOGGING env var │ │\n│ └─────────────────────────────────────────────────────┘ │\n└─────────────────────────────────────────────────────────────┘\n```\n\n## Installation\n\n### Package Requirements\n\nThe server requires Node.js and is distributed as an npm package. It can also be run via Docker.\n\n资料来源：[package.json:18-22](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n### npx (Unix/Linux/macOS)\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n### npx (Windows)\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"cmd\",\n \"args\": [\"/c\", \"npx\", \"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n### Docker\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"--rm\", \"-i\", \"mcp/sequentialthinking\"]\n }\n }\n}\n```\n\n资料来源：[README.md:1-50](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Configuration\n\n### Claude Desktop Configuration\n\nAdd the following to `claude_desktop_config.json`:\n\n#### NPX Installation\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n#### Docker Installation\n\n```json\n{\n \"mcpServers\": {\n \"sequentialthinking\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"--rm\", \"-i\", \"mcp/sequentialthinking\"]\n }\n }\n}\n```\n\n### VS Code Configuration\n\nUse the quick installation buttons in the README, or manually configure with:\n\n```json\n{\n \"mcpServers\": {\n \"sequential-thinking\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@modelcontextprotocol/server-sequential-thinking\"]\n }\n }\n}\n```\n\n资料来源：[README.md:90-130](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Environment Variables\n\n| Variable | Type | Default | Description |\n|----------|------|---------|-------------|\n| `DISABLE_THOUGHT_LOGGING` | boolean | `false` | Set to `true` to disable logging of thought information |\n\nWhen `DISABLE_THOUGHT_LOGGING` is set to `true`, the server will not log any thought-related information, providing a more private reasoning process.\n\n资料来源：[README.md:70-72](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## Building from Source\n\n### Prerequisites\n\n- Node.js\n- npm\n- TypeScript\n\n### Build Commands\n\n```bash\n# Clone the repository\ngit clone https://github.com/modelcontextprotocol/servers.git\ncd servers/src/sequentialthinking\n\n# Install dependencies\nnpm install\n\n# Build the TypeScript project\nnpm run build\n```\n\nThe build process:\n1. Compiles TypeScript using `tsc`\n2. Sets executable permissions on compiled JavaScript files using `shx chmod +x`\n\n资料来源：[package.json:12-16](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n### Docker Build\n\n```bash\ndocker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .\n```\n\n## Usage Patterns\n\n### When to Use Sequential Thinking\n\nThe `sequential_thinking` tool is designed for:\n\n| Use Case | Description |\n|----------|-------------|\n| Problem Decomposition | Breaking down complex problems into steps |\n| Planning & Design | Creating plans with room for revision |\n| Multi-step Analysis | Analysis that might need course correction |\n| Uncertain Scope | Problems where full scope isn't clear initially |\n| Context Maintenance | Tasks needing to maintain context over multiple steps |\n| Information Filtering | Situations where irrelevant information needs filtering |\n\n资料来源：[README.md:55-68](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n### Verification Workflow\n\n```mermaid\ngraph LR\n A[Install Server] --> B[Restart MCP Host]\n B --> C[Verify Tool Appears]\n C --> D[Ask Complex Question]\n D --> E[Model Invokes Tool Multiple Times]\n E --> F[Observe Step-by-Step Reasoning]\n```\n\n**Manual Verification Steps:**\n\n1. Install the server in your MCP host\n2. Restart or reload the host so it reconnects to the server\n3. Confirm the `sequential_thinking` tool appears in the host's MCP tool list\n4. Ask the host to solve a non-trivial problem step-by-step\n5. Verify the host invokes the tool multiple times instead of returning a one-shot answer\n\n资料来源：[README.md:145-165](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n### Reasoning Branching Example\n\n```mermaid\ngraph TD\n A[Thought 1: Initial Problem] --> B[Thought 2: Approach A]\n B --> C[Thought 3: Explore Branch A1]\n C --> D{Decision Point}\n D -->|Revert| E[Thought 4: Revises Thought 2
branchId: branch-A]\n D -->|Continue| F[Thought 5: Continue on A1]\n E --> G[Thought 5: Alternative Path]\n```\n\nThe tool supports:\n- **Revisions** — Mark thoughts with `isRevision: true` and `revisesThought` to indicate corrections\n- **Branches** — Use `branchFromThought` and `branchId` to create alternative reasoning paths\n- **Dynamic Length** — Adjust `totalThoughts` as the reasoning progresses\n\n## Dependencies\n\n| Dependency | Version | Purpose |\n|------------|---------|---------|\n| `@modelcontextprotocol/sdk` | ^1.29.0 | MCP protocol implementation |\n| `chalk` | ^5.3.0 | Terminal string styling |\n| `yargs` | ^17.7.2 | Command-line argument parsing |\n\n**Dev Dependencies:**\n\n| Dependency | Purpose |\n|------------|---------|\n| `typescript` | TypeScript compiler |\n| `vitest` | Testing framework |\n| `@vitest/coverage-v8` | Code coverage |\n| `shx` | Shell command wrapper |\n| `@types/node`, `@types/yargs` | Type definitions |\n\n资料来源：[package.json:18-40](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## Testing\n\nThe project includes Vitest tests with coverage reporting:\n\n```bash\nnpm test\n```\n\nThis runs tests with coverage using `vitest run --coverage`.\n\n资料来源：[package.json:15](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/package.json)\n\n## License\n\nThis MCP server is licensed under the **MIT License**. Users are free to use, modify, and distribute the software subject to the terms and conditions of the MIT License.\n\n资料来源：[README.md:80-83](https://github.com/modelcontextprotocol/servers/blob/main/src/sequentialthinking/README.md)\n\n## See Also\n\n- [Model Context Protocol Specification](https://modelcontextprotocol.io)\n- [MCP Servers Repository](https://github.com/modelcontextprotocol/servers)\n- [Bug Tracker](https://github.com/modelcontextprotocol/servers/issues)\n\n---\n\n---\n\n## Doramagic 踩坑日志\n\n项目：modelcontextprotocol/servers\n\n摘要：发现 6 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：能力坑 - 能力判断依赖假设。\n\n## 1. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | README/documentation is current enough for a first validation pass.\n\n## 2. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | last_activity_observed missing\n\n## 3. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 4. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 5. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | issue_or_pr_quality=unknown\n\n## 6. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | release_recency=unknown\n\n\n",
"summary": "DeepWiki/Human Wiki 完整输出，末尾追加 Discovery Agent 踩坑日志。",
"title": "Human Manual / 人类版说明书"
},
"pitfall_log": {
"asset_id": "pitfall_log",
"filename": "PITFALL_LOG.md",
"markdown": "# Pitfall Log / 踩坑日志\n\n项目：modelcontextprotocol/servers\n\n摘要：发现 6 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：能力坑 - 能力判断依赖假设。\n\n## 1. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | README/documentation is current enough for a first validation pass.\n\n## 2. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | last_activity_observed missing\n\n## 3. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 4. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | no_demo; severity=medium\n\n## 5. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | issue_or_pr_quality=unknown\n\n## 6. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:890668799 | https://github.com/modelcontextprotocol/servers | release_recency=unknown\n",
"summary": "用户实践前最可能遇到的身份、安装、配置、运行和安全坑。",
"title": "Pitfall Log / 踩坑日志"
},
"prompt_preview": {
"asset_id": "prompt_preview",
"filename": "PROMPT_PREVIEW.md",
"markdown": "# servers - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for modelcontextprotocol/servers.\n\nProject:\n- Name: servers\n- Repository: https://github.com/modelcontextprotocol/servers\n- Summary: Model Context Protocol Servers\n- Host target: local_cli\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: Model Context Protocol Servers\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Model Context Protocol Servers\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. repository-structure: Repository Structure. Produce one small intermediate artifact and wait for confirmation.\n2. quick-start: Quick Start Guide. Produce one small intermediate artifact and wait for confirmation.\n3. everything-server: Everything Server. Produce one small intermediate artifact and wait for confirmation.\n4. filesystem-server: Filesystem Server. Produce one small intermediate artifact and wait for confirmation.\n5. memory-server: Memory Server. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/modelcontextprotocol/servers\n- https://github.com/modelcontextprotocol/servers#readme\n- package.json\n- tsconfig.json\n- CLAUDE.md\n- src/everything/package.json\n- src/filesystem/package.json\n- src/fetch/pyproject.toml\n- README.md\n- src/memory/package.json\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n",
"summary": "不安装项目也能感受能力节奏的安全试用 Prompt。",
"title": "Prompt Preview / 安装前试用 Prompt"
},
"quick_start": {
"asset_id": "quick_start",
"filename": "QUICK_START.md",
"markdown": "# Quick Start / 官方入口\n\n项目：modelcontextprotocol/servers\n\n## 官方安装入口\n\n### Node.js / npx · 官方安装入口\n\n```bash\nnpx -y @modelcontextprotocol/server-memory\n```\n\n来源：https://github.com/modelcontextprotocol/servers#readme\n\n## 来源\n\n- repo: https://github.com/modelcontextprotocol/servers\n- docs: https://github.com/modelcontextprotocol/servers#readme\n",
"summary": "从项目官方 README 或安装文档提取的开工入口。",
"title": "Quick Start / 官方入口"
}
},
"validation_id": "dval_e719397ea4654b7d9aa9c05ded209583"
}