为自然搜索排名提供站点审计、内容撰写与竞品分析。
设计与多媒体
mcp-builder
试用按四阶段流程搭建 MCP 服务器,让 LLM 通过设计良好的工具调用外部 API。
它能做什么
这份指南把 MCP 服务器开发拆成四个阶段:调研与规划、实现、审查与测试、编写评测。规划阶段讨论 API 全覆盖与工作流工具之间的取舍、工具命名、上下文管理、可操作的错误信息,并指向 MCP 规范、SDK README 以及 TypeScript(SDK v2,旧项目另有 v1 说明)和 Python/FastMCP 的语言指南。实现部分涉及 Zod 或 Pydantic 输入 schema、outputSchema 与 structuredContent、工具注解、分页和错误处理。最后要求写出 10 道可验证的评测题并保存为 XML 文件。
什么时候用它
- 把外部 REST API 封装成 MCP 服务器
- 在 API 全覆盖和高层工作流工具之间做取舍
- 把已有的 TypeScript MCP 服务器从 SDK v1 迁移到 v2
- 编写评测题,检验 LLM 是否真的能用起来你的服务器
技能文档
MCP Server Development Guide
Overview
Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
Process
🚀 High-Level Workflow
Creating a high-quality MCP server involves four main phases:
Phase 1: Deep Research and Planning
1.1 Understand Modern MCP Design
API Coverage vs. Workflow Tools: Balance comprehensive API endpoint coverage with specialized workflow tools. Workflow tools can be more convenient for specific tasks, while comprehensive coverage gives agents flexibility to compose operations. Performance varies by client—some clients benefit from code execution that combines basic tools, while others work better with higher-level workflows. When uncertain, prioritize comprehensive API coverage.
Tool Naming and Discoverability:
Clear, descriptive tool names help agents find the right tools quickly. Use consistent prefixes (e.g., github_create_issue, github_list_repos) and action-oriented naming.
Context Management: Agents benefit from concise tool descriptions and the ability to filter/paginate results. Design tools that return focused, relevant data. Some clients support code execution which can help agents filter and process data efficiently.
Actionable Error Messages: Error messages should guide agents toward solutions with specific suggestions and next steps.
1.2 Study MCP Protocol Documentation
Navigate the MCP specification:
Start with the sitemap to find relevant pages: https://modelcontextprotocol.io/sitemap.xml
Then fetch specific pages with .md suffix for markdown format (e.g., https://modelcontextprotocol.io/specification/draft.md).
Key pages to review:
- Specification overview and architecture
- Transport mechanisms (streamable HTTP, stdio)
- Tool, resource, and prompt definitions
1.3 Study Framework Documentation
Recommended stack:
- Language: TypeScript (high-quality SDK support and good compatibility in many execution environments e.g. MCPB. Plus AI models are good at generating TypeScript code, benefiting from its broad usage, static typing and good linting tools)
- Transport: Streamable HTTP for remote servers, using stateless JSON (simpler to scale and maintain, as opposed to stateful sessions and streaming responses). stdio for local servers.
Load framework documentation:
- MCP Best Practices: 📋 View Best Practices - Core guidelines
For TypeScript (recommended):
The TypeScript SDK has two major versions. Pick one before writing code:
- v2 (
@modelcontextprotocol/server): the current stable release. Use it for new servers. - v1 (
@modelcontextprotocol/sdk): receives bug and security fixes only. Use it only when the project'spackage.jsonalready depends on@modelcontextprotocol/sdk, or migrate that project withnpx @modelcontextprotocol/codemod@latest v1-to-v2 .
If the project already uses v1, tell the user once, in a sentence or two, that v2 (@modelcontextprotocol/server) is the current stable release, that v1 receives only bug and security fixes, and that npx @modelcontextprotocol/codemod@latest v1-to-v2 . migrates the project. Then continue with v1 unless the user asks to migrate.
Don't mix the two in one project: v1 code samples (imports from @modelcontextprotocol/sdk/...) don't apply to v2.
- TypeScript SDK (v2): Use WebFetch to load
https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md; the full docs index ishttps://ts.sdk.modelcontextprotocol.io/v2/llms.txt - ⚡ TypeScript Guide (v2) - TypeScript patterns and examples
- For v1 projects only:
https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/v1.x/README.mdand the TypeScript Guide (v1)
For Python:
- Python SDK: Use WebFetch to load
https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md - 🐍 Python Guide - Python patterns and examples
1.4 Plan Your Implementation
Understand the API: Review the service's API documentation to identify key endpoints, authentication requirements, and data models. Use web search and WebFetch as needed.
Tool Selection: Prioritize comprehensive API coverage. List endpoints to implement, starting with the most common operations.
Phase 2: Implementation
2.1 Set Up Project Structure
See language-specific guides for project setup:
- ⚡ TypeScript Guide (v2) - Project structure, package.json, tsconfig.json (v1 for existing v1 projects)
- 🐍 Python Guide - Module organization, dependencies
2.2 Implement Core Infrastructure
Create shared utilities:
- API client with authentication
- Error handling helpers
- Response formatting (JSON/Markdown)
- Pagination support
2.3 Implement Tools
For each tool:
Input Schema:
- Use Zod (TypeScript) or Pydantic (Python)
- Include constraints and clear descriptions
- Add examples in field descriptions
Output Schema:
- Define
outputSchemawhere possible for structured data - Use
structuredContentin tool responses (TypeScript SDK feature) - Helps clients understand and process tool outputs
Tool Description:
- Concise summary of functionality
- Parameter descriptions
- Return type schema
Implementation:
- Async/await for I/O operations
- Proper error handling with actionable messages
- Support pagination where applicable
- Return both text content and structured data when using modern SDKs
Annotations:
readOnlyHint: true/falsedestructiveHint: true/falseidempotentHint: true/falseopenWorldHint: true/false
Phase 3: Review and Test
3.1 Code Quality
Review for:
- No duplicated code (DRY principle)
- Consistent error handling
- Full type coverage
- Clear tool descriptions
3.2 Build and Test
TypeScript:
- Run
npm run buildto verify compilation - v2 projects: run the self-check script from the v2 guide against the built server
- Test with MCP Inspector:
npx @modelcontextprotocol/inspector
Python:
- Verify syntax:
python -m py_compile your_server.py - Test with MCP Inspector
See language-specific guides for detailed testing approaches and quality checklists.
Phase 4: Create Evaluations
After implementing your MCP server, create comprehensive evaluations to test its effectiveness.
Load ✅ Evaluation Guide for complete evaluation guidelines.
4.1 Understand Evaluation Purpose
Use evaluations to test whether LLMs can effectively use your MCP server to answer realistic, complex questions.
4.2 Create 10 Evaluation Questions
To create effective evaluations, follow the process outlined in the evaluation guide:
- Tool Inspection: List available tools and understand their capabilities
- Content Exploration: Use READ-ONLY operations to explore available data
- Question Generation: Create 10 complex, realistic questions
- Answer Verification: Solve each question yourself to verify answers
4.3 Evaluation Requirements
Ensure each question is:
- Independent: Not dependent on other questions
- Read-only: Only non-destructive operations required
- Complex: Requiring multiple tool calls and deep exploration
- Realistic: Based on real use cases humans would care about
- Verifiable: Single, clear answer that can be verified by string comparison
- Stable: Answer won't change over time
4.4 Output Format
Create an XML file with this structure:
Find discussions about AI model launches with animal codenames. One model needed a specific safety designation that uses the format ASL-X. What number X was being determined for the model named after a spotted wild cat?
3
<!-- More qa_pairs... -->
Reference Files
📚 Documentation Library
Load these resources as needed during development:
Core MCP Documentation (Load First)
- MCP Protocol: Start with sitemap at
https://modelcontextprotocol.io/sitemap.xml, then fetch specific pages with.mdsuffix - 📋 MCP Best Practices - Universal MCP guidelines including:
- Server and tool naming conventions
- Response format guidelines (JSON vs Markdown)
- Pagination best practices
- Transport selection (streamable HTTP vs stdio)
- Security and error handling standards
SDK Documentation (Load During Phase 1/2)
- Python SDK: Fetch from
https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md - TypeScript SDK (v2): Fetch from
https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md; full docs index athttps://ts.sdk.modelcontextprotocol.io/v2/llms.txt - TypeScript SDK (v1, existing v1 projects only): Fetch from
https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/v1.x/README.md
Language-Specific Implementation Guides (Load During Phase 2)
-
🐍 Python Implementation Guide - Complete Python/FastMCP guide with:
- Server initialization patterns
- Pydantic model examples
- Tool registration with
@mcp.tool - Complete working examples
- Quality checklist
-
⚡ TypeScript Implementation Guide (SDK v2) - Complete TypeScript guide for
@modelcontextprotocol/serverwith:- Project setup and the server factory
- Tool design: Zod 4 schemas, output formats, pagination, errors
- A complete example serving stdio and Streamable HTTP, plus bearer auth
- Resources, prompts, and notifications
- A self-check script to verify the built server
- Links to SDK examples for advanced features
- A v1 → v2 translation table, migration steps, and a quality checklist
-
⚡ TypeScript Implementation Guide (SDK v1) - The equivalent guide for existing
@modelcontextprotocol/sdkprojects
Evaluation Guide (Load During Phase 4)
- ✅ Evaluation Guide - Complete evaluation creation guide with:
- Question creation guidelines
- Answer verification strategies
- XML format specifications
- Example questions and answers
- Running an evaluation with the provided scripts
常见问题
- 推荐用什么语言和传输方式?
- 推荐 TypeScript:远程服务器用 Streamable HTTP 加无状态 JSON,本地服务器用 stdio。文档同时提供了 Python/FastMCP 的实现指南。
- 两个 TypeScript SDK 版本都覆盖了吗?
- 覆盖了。新服务器用 v2(@modelcontextprotocol/server),文档称其为当前稳定版;v1(@modelcontextprotocol/sdk)只接收缺陷和安全修复。已有 v1 项目可用 npx @modelcontextprotocol/codemod@latest v1-to-v2 . 迁移,且不要在同一项目里混用两个版本。
- 怎么验证服务器确实能用?
- 第三阶段用 MCP Inspector(npx @modelcontextprotocol/inspector)测试,v2 TypeScript 项目还有自检脚本,Python 用 py_compile 检查语法。第四阶段再写 10 道独立、只读、可验证的题目存成 XML,用来检验 LLM 能否使用这个服务器。
相关技能
以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。
docx
官方创建、编辑、读取和修订 Word 的 .docx / .dotx 文件,并渲染成图检查实际效果。
用 Python 和命令行工具读取、提取、合并、拆分、旋转、加水印、加密和生成 PDF。
搭建、重构和排查 ChatGPT Apps SDK 应用,把 MCP 服务器与 widget 界面组合起来。
用文件里已发布的设计系统组件、变量和样式,在 Figma 中搭建或更新整页界面,而不是手动画基础图形。
Anthropic 的更多技能
浏览全部技能通过收集上下文、逐节撰写和读者测试,把零散想法变成一份成稿文档。
docx
官方创建、编辑、读取和修订 Word 的 .docx / .dotx 文件,并渲染成图检查实际效果。
用 Python 和命令行工具读取、提取、合并、拆分、旋转、加水印、加密和生成 PDF。
pptx
官方用 pptxgenjs 脚本、XML 编辑和配套脚本创建、修改和读取 .pptx / .potx 文件。
xlsx
官方用真实公式创建和修改 Excel 工作簿,统一数字格式,并在交付前完成重算与错误排查。
把一句艺术需求变成一份生成艺术哲学文档,外加可直接运行的 p5.js 草图与种子控制。