MCP Dev Standards
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub API Token（用于 Git 来源） | |
| STANDARDS_PATH | No | 规范文档路径 | ./standards |
| STANDARDS_CONFIG | No | 配置文件路径 | standards.config.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve-standard-idA | 根据关键词搜索匹配的开发规范文档。在获取具体规范内容前，必须先调用此工具获取规范 ID。 |
| get-standard-docsA | 获取指定规范文档的详细内容。需要先通过 resolve-standard-id 获取规范 ID。 |
| list-standardsA | 列出所有可用的开发规范分类和文档。可按分类过滤。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| API 错误处理规范 | API 错误处理的设计规范和最佳实践 |
| RESTful API 设计规范 | RESTful API 的设计规范和最佳实践 |
| 数据库命名规范 | 数据库表、字段、索引等的命名规范 |
| AI 生成代码注释规范 | AI 生成代码的强制注释要求，确保代码可读性、可维护性和知识传递 |
| 团队开发规范 | 团队内部的自定义开发规范和约定 |
| Vite 开发规范 | Vite 构建工具的配置规范和最佳实践，基于官方文档整理 |
| Webpack 开发规范 | Webpack 构建工具的配置规范和最佳实践，基于官方文档整理 |
| Qiankun 微前端开发规范 | Qiankun 微前端框架的开发规范和最佳实践，基于官方文档整理 |
| React 组件开发规范 | React 函数组件的编写规范和最佳实践 |
| React Hooks 开发规范 | React 自定义 Hooks 的编写规范和最佳实践 |
| 前端代码安全检查规范 | 前端代码安全检查清单、漏洞防护和最佳实践，涵盖 XSS、CSRF、敏感数据保护等 |
| Tailwind CSS 开发规范 | Tailwind CSS 的使用规范和最佳实践 |
| Vue 3 组件开发规范 | Vue 3 组件的编写规范和最佳实践 |
| Vue 3 Composables 开发规范 | Vue 3 组合式函数的编写规范和最佳实践 |
| Vue 2 开发规范 | Vue 2.x 组件开发规范和最佳实践，基于官方文档整理 |
| Vue 3 开发规范 | Vue 3.x 组件开发规范和最佳实践，基于官方文档整理，重点介绍 Composition API |
| Using TypeScript | Source: https://github.com/vercel/next.js/blob/canary/docs/01-app/01-getting-started/01-installation.mdx |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: resolve-standard-id searches by keyword, get-standard-docs retrieves content by ID, and list-standards provides a browsable overview. There is no overlap between searching, fetching, and listing.
All tool names follow the same verb_noun hyphenated pattern: resolve-standard-id, get-standard-docs, list-standards. The verbs and objects are consistent and readable.
Three tools are well-scoped for a read-only standards documentation server. The set covers the essential operations—search, fetch, and list—without unnecessary extras.
The tool surface covers the full lifecycle for a documentation server: discovering standards (list), finding specific ones (resolve), and retrieving details (get). There are no obvious dead ends; the dependency between resolve and get is clearly documented.