Shortcut MCP (Aezizhu)

快捷方式MCP-将长提示保存为简单命令

停止每天复制和粘贴相同的500字提示。

快捷方式MCP允许您将常用的长提示保存为自定义快捷方式。你用于代码审查的复杂提示？另存为 /review.详细的调试说明提示？现在只是 /debug你精心塑造的形象？简单地 /expert.

专为珍惜时间、讨厌重复的开发人员而设计。

🚀 真实示例-查看差异

之前（您以前键入的内容）：

"You are a senior software engineer with 15+ years of experience in building 
production systems. Perform a thorough code review of the following code. 
Your review should cover: 1. Code Quality: Assess readability, maintainability, 
and adherence to best practices and design patterns. 2. Potential Bugs: 
Identify any logic errors, edge cases not handled, or potential runtime 
exceptions. 3. Security: Check for security vulnerabilities including 
injection attacks, data exposure, authentication/authorization issues. 
4. Performance: Analyze algorithmic complexity, database queries, caching 
opportunities, and potential bottlenecks. 5. Testing: Evaluate test coverage 
and suggest additional test cases. 6. Documentation: Assess inline comments, 
function documentation, and clarity. 7. Architecture: Comment on the overall 
design, separation of concerns, and scalability. Provide specific line-by-line 
feedback where appropriate, and conclude with a summary of the most critical 
issues to address. Be constructive but thorough - this code will go to 
production. Code to review: [YOUR CODE HERE]"

之后（您现在键入的内容）：

/coderev [YOUR CODE HERE]

就是这样。从300多个单词到8个字符。

💡 运作原理

1.你经常使用长提示

也许这是一个300字的代码审查清单，一个500字的调试指南，或者是一个你几个月来完善的复杂的角色描述。

2.另存为快捷方式

{
  "command": "/myreview",
  "prompt": "[Your 300-word code review prompt here]"
}

3.立即使用

而不是： *\[粘贴300字\]* +你的代码\ 现在只需键入： /myreview +你的代码

就是这样。你的个人提示库，随时在你的指尖。

📚 完整的定制指南

来自流行提示的真实例子

示例1：“完美代码助手”提示（400+字）

这是开发人员反复使用的最受欢迎的提示之一：

// Step 1: Define your custom shortcut
create_shortcut({
  command: "/assistant",
  name: "Perfect Coding Assistant",
  prompt: `You are an expert programmer with deep knowledge across multiple languages and frameworks. Your approach combines theoretical knowledge with practical experience from production systems.

CORE PRINCIPLES:
1. Write clean, maintainable code that follows SOLID principles
2. Always consider edge cases and error handling
3. Optimize for readability first, performance second (unless specified)
4. Include comprehensive comments for complex logic
5. Follow language-specific best practices and idioms

RESPONSE FORMAT:
- Start with a brief analysis of the problem
- Present the solution with clear explanations
- Include code with detailed comments
- Discuss time/space complexity when relevant
- Suggest alternative approaches if applicable
- Mention potential pitfalls or considerations

CODING STANDARDS:
- Use meaningful variable and function names
- Keep functions small and focused (single responsibility)
- Implement proper error handling and logging
- Add input validation where necessary
- Consider security implications (input sanitization, SQL injection, XSS, etc.)
- Write code that is testable and mockable

DOCUMENTATION:
- Add docstrings/JSDoc comments for all public functions
- Include usage examples in comments
- Document any assumptions or limitations
- Explain complex algorithms or business logic

When reviewing code, check for:
- Logic errors and edge cases
- Security vulnerabilities
- Performance bottlenecks
- Code smells and anti-patterns
- Missing error handling
- Opportunities for refactoring

Always be constructive and educational in your responses. If you see a better way to do something, explain why it's better, not just that it is better.

Task to complete: {input}`
})

// Step 2: Use it with a simple command
// Instead of pasting all 400+ words every time, just type:
// /assistant "implement a rate limiter in Python"

示例2：“思维链”推理提示（350+字）

常见于复杂问题的解决：

create_shortcut({
  command: "/think",
  name: "Chain of Thought Reasoning",
  prompt: `Let's approach this step-by-step using careful reasoning.

THINKING PROCESS:
1. First, I'll break down what's being asked
2. Then identify key components and constraints
3. Consider multiple approaches
4. Evaluate trade-offs
5. Select the best solution
6. Implement with careful consideration

For each step, I will:
- State my current understanding
- Identify assumptions I'm making
- Consider what could go wrong
- Think about edge cases
- Validate my reasoning

PROBLEM ANALYSIS:
Let me start by understanding the core problem. The request is about: {input}

Key aspects to consider:
- What is the desired outcome?
- What constraints exist?
- What resources are available?
- What are the success criteria?

SOLUTION EXPLORATION:
I'll explore multiple solutions:

Option 1: [Describe first approach]
- Pros: 
- Cons:
- Complexity:
- Risks:

Option 2: [Describe alternative approach]
- Pros:
- Cons:
- Complexity:
- Risks:

Option 3: [Describe another alternative if applicable]
- Pros:
- Cons:
- Complexity:
- Risks:

DECISION RATIONALE:
Based on the analysis, I recommend [selected approach] because:
1. [Reason 1]
2. [Reason 2]
3. [Reason 3]

IMPLEMENTATION PLAN:
Step 1: [Detailed first step]
Step 2: [Detailed second step]
Step 3: [Continue with all steps]

VALIDATION:
To ensure this solution works:
- Test case 1: [Description]
- Test case 2: [Description]
- Edge case consideration: [Description]

POTENTIAL IMPROVEMENTS:
Future enhancements could include:
- [Improvement 1]
- [Improvement 2]

Let me now provide the complete solution...`
})

// Usage: /think "design a distributed cache system"

示例3：“代码审阅者”提示（500字以上）

团队用于一致的代码审查：

create_shortcut({
  command: "/review",
  name: "Comprehensive Code Review",
  prompt: `As a senior engineer, I'll review this code across multiple dimensions. My review will be thorough but constructive, focusing on helping you improve the code and learn best practices.

REVIEW CHECKLIST:

1. FUNCTIONALITY & CORRECTNESS
- Does the code do what it's supposed to do?
- Are all requirements met?
- Are there any logic errors or bugs?
- Edge cases handled properly?
- Off-by-one errors?
- Null/undefined handling?

2. CODE QUALITY & READABILITY
- Is the code self-documenting?
- Are variable/function names descriptive?
- Is the code DRY (Don't Repeat Yourself)?
- Appropriate abstraction levels?
- Consistent coding style?
- Proper indentation and formatting?

3. PERFORMANCE & EFFICIENCY
- Time complexity analysis
- Space complexity concerns
- Database query optimization
- Caching opportunities
- Unnecessary loops or operations
- Memory leaks potential
- Resource cleanup

4. SECURITY CONSIDERATIONS
- Input validation and sanitization
- SQL injection vulnerabilities
- XSS attack vectors
- Authentication/authorization issues
- Sensitive data exposure
- Proper encryption usage
- Security headers
- CORS configuration

5. ERROR HANDLING & RESILIENCE
- Proper try-catch blocks
- Meaningful error messages
- Graceful degradation
- Retry logic where appropriate
- Circuit breaker patterns
- Timeout handling
- Rollback mechanisms

6. TESTING & TESTABILITY
- Test coverage adequacy
- Edge cases in tests
- Mock usage appropriateness
- Test isolation
- Test naming clarity
- Integration test scenarios
- Performance test considerations

7. ARCHITECTURE & DESIGN PATTERNS
- SOLID principles adherence
- Design pattern usage
- Coupling and cohesion
- Dependency injection
- Interface segregation
- Modularity
- Scalability considerations

8. DOCUMENTATION & COMMENTS
- Function/class documentation
- Complex logic explanation
- API documentation
- README updates needed
- Inline comment quality
- TODO/FIXME items
- Changelog updates

9. DEPENDENCIES & COMPATIBILITY
- Unnecessary dependencies
- Dependency versions
- License compatibility
- Breaking changes
- Deprecation warnings
- Browser compatibility
- Backward compatibility

10. MAINTAINABILITY & FUTURE-PROOFING
- Code flexibility
- Configuration vs hardcoding
- Feature flags usage
- Database migration strategy
- API versioning
- Monitoring/logging hooks
- Debug capabilities

REVIEW OUTPUT FORMAT:
- Critical Issues: [Must fix before merge]
- Major Concerns: [Should address]
- Minor Suggestions: [Nice to have]
- Positive Feedback: [What was done well]
- Learning Opportunities: [Educational points]

Code to review: {input}`
})

// Usage: /review [paste your code]

如何创建自己的自定义快捷方式

第一步：识别你的重复提示

查找您经常使用的提示：

• 复杂的调试说明
• 详细的代码审查清单
• 具体格式要求
• 角色扮演场景
• 分析框架

步骤2：创建快捷方式

使用MCP工具保存您的提示：

{
  "name": "create_shortcut",
  "arguments": {
    "command": "/your-command",
    "name": "Descriptive Name",
    "description": "What this prompt does",
    "prompt": "Your full prompt text here with {input} for dynamic content",
    "category": "coding|thinking|writing|analysis",
    "tags": ["relevant", "tags", "for", "search"]
  }
}

第三步：整理你的快捷方式

• 使用类别： coding, debugging, review, architecture, testing
• 添加标签以便于查找
• 标记收藏夹以快速访问
• 跟踪使用情况以优化您的库

您可以添加的热门提示

1. “像我5岁一样解释”提示 → /eli5
2. “查找安全漏洞”提示 → /security
3. “转换为TypeScript”提示 → /typescript
4. “写入单元测试”提示 → /unittest
5. “性能优化”提示 → /perf
6. API文档提示 → /apidoc
7. “数据库模式设计”提示 → /schema
8. “React最佳实践”提示 → /react
9. “Python PEP8”提示 → /pep8
10. “系统设计访谈”提示 → /sysdesign

🎯 非常适合

• 开发者 带有详细的调试或审查提示
• 建筑师 使用详细的系统设计模板
• 团队领导 使用标准化的代码审查清单
• 工程师 他们通过反复试验精心制作了完美的提示
• 任何人 厌倦了在单独的文档中管理提示

✨ 主要特点

核心功能

• ⚡ 长时间快速更换：将500多个单词的提示替换为简单的 /commands
• 🎨 复杂模板：存储多段指令、人物角色和思维链推理
• 📝 自定义创建：保存您精心制作的提示，并立即重复使用
• 🗂️ 智能组织：按用例、项目或工作流分类
• ⭐ 收藏夹系统：快速访问最强大的提示
• 🔍 智能搜索：按关键字或描述查找正确的提示

高性能

• 💾 永久存储：您的快捷方式保存在本地，并在会话之间同步
• 📊 使用情况分析：跟踪您最常用的快捷方式
• 🏷️ 标签系统：使用自定义标签组织快捷方式，以便更好地发现
• 📤 导入/导出：与他人共享快捷方式集合
• 🔄 版本控制：跟踪快捷方式的更改和更新

开发者体验

• 📚 TypeScript优先：完全类型安全和IntelliSense支持
• 🧪 综合测试：单元测试、集成测试和测试场景
• 📖 丰富的文档：API参考资料、体系结构指南和示例
• 🔧 易于配置：基于JSON的配置，带有环境变量覆盖

🏗️ 建筑

为通用MCP兼容性而构建：

┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   Any MCP       │    │  Prompt Shortcut │    │  Local Storage  │
│   Compatible    │◄──►│   MCP Server     │◄──►│   & Templates   │
│   Platform      │    │                  │    │                 │
└─────────────────┘    └──────────────────┘    └─────────────────┘

支持的平台：

• 克劳德桌面版 -Anthropic官方应用
• Cline（VSCode） -AI助手扩展
• Continue.dev -开源编码助手
• 光标IDE -AI驱动的代码编辑器
• 自定义应用程序 -任何兼容MCP的客户端

核心组件：

• MCP协议：完全符合模型上下文协议
• Node.js/TypeScript：现代、类型安全的服务器实现
• @模型上下文协议/sdk：用于协议合规性的官方MCP SDK
• 快速经理：快捷命令的智能解析和扩展
• 本地数据库：自定义快捷方式的持久存储

📦 安装

系统要求

• macOS12.0（蒙特利）或更晚
• Node.js：18.0+（建议使用LTS）
• 程序包管理器：npm 8.0+或纱线1.22+
• 快捷方式应用程序：预装macOS

🚀 快速开始

# Clone and setup
git clone 
cd shortcut-mcp

# Install dependencies
npm install

# Build the project
npm run build

# Verify installation
npm run test

# Start the MCP server
npm start

🔧 配置

创建自定义配置文件：

# Copy example config
cp examples/config.example.json config/local.json

基本配置：

{
  "server": {
    "name": "my-shortcut-mcp",
    "version": "1.0.0"
  },
  "shortcuts": {
    "allowedPrefixes": ["Safe", "Public", "Demo"],
    "blockedShortcuts": ["System Config", "Admin Tools"],
    "maxExecutionTime": 30000,
    "enableCache": true
  },
  "security": {
    "requireConfirmation": false,
    "logExecutions": true,
    "allowSystemShortcuts": false
  },
  "logging": {
    "level": "info",
    "console": true
  }
}

🔐 环境变量

用环境变量覆盖配置：

export LOG_LEVEL=debug
export MAX_EXECUTION_TIME=45000
export ENABLE_CACHE=true
export ALLOW_SYSTEM_SHORTCUTS=false

🔌 MCP平台集成

此MCP服务器与 任何兼容MCP的平台:

克劳德桌面版

{
  "mcpServers": {
    "prompt-shortcuts": {
      "command": "node",
      "args": ["/path/to/shortcut-mcp/dist/index.js"]
    }
  }
}

Cline（VSCode扩展）

{
  "mcpServers": {
    "prompt-shortcuts": {
      "command": "node",
      "args": ["/path/to/shortcut-mcp/dist/index.js"],
      "env": {
        "LOG_LEVEL": "info"
      }
    }
  }
}

Continue.dev

{
  "models": [...],
  "mcpServers": {
    "prompt-shortcuts": {
      "command": "node",
      "args": ["/path/to/shortcut-mcp/dist/index.js"]
    }
  }
}

自定义MCP客户端

import { MCPClient } from '@modelcontextprotocol/client';

const client = new MCPClient({
  transport: {
    type: 'stdio',
    command: 'node',
    args: ['/path/to/shortcut-mcp/dist/index.js']
  }
});

// Use parse_shortcut tool
const result = await client.callTool('parse_shortcut', {
  input: '/th How does AI reasoning work?'
});

📝 创建自己的快捷方式

示例：保存代码审查提示

// Your current workflow:
// 1. Open your prompts document
// 2. Find your code review prompt (300+ words)
// 3. Copy it
// 4. Paste into AI chat
// 5. Add your code

// With Shortcut MCP:
create_shortcut({
  command: "/myreview",
  name: "My Team's Code Review",
  prompt: `You are reviewing code for our team's production system.
  
  Check for:
  - Our style guide compliance (4 spaces, no tabs)
  - Security issues specific to our stack (Node.js, PostgreSQL)
  - Performance implications for our 100k daily users
  - Missing error handling for our payment system
  - Compliance with our logging standards
  - Unit test coverage (minimum 80%)
  - Documentation in our format
  
  [... your full 300+ word prompt ...]
  
  Code to review: {input}`
})

// Now just type: /myreview [code]

示例：保存调试模板

create_shortcut({
  command: "/debug-prod",
  name: "Production Debugging Guide",
  prompt: `[Your 500+ word debugging methodology that includes:
  - System architecture context
  - Common failure points
  - Log analysis steps
  - Database query patterns
  - Performance profiling steps
  - Rollback procedures
  - Incident documentation
  ...]
  
  Issue to debug: {input}`
})

// Usage: /debug-prod "Users can't login after deployment"

🚀 用法

快速入门示例

基本快捷方式用法

只需在任何对话中键入快捷命令：

User: "/th How can we solve climate change effectively?"
→ Expands to: "Think harder about this problem. Analyze it step by step with deep reasoning and consider multiple perspectives. How can we solve climate change effectively?"

User: "/ider 故事发生在2150年的火星殖民地，人类和AI共同治理社会..."
→ Expands to: "You are a skilled science fiction writer. Based on the following prompt, write a compelling story with rich details: 故事发生在2150年的火星殖民地..."

User: "/code Create a Python function to calculate Fibonacci numbers"
→ Expands to: "You are an expert programmer. Write clean, well-documented code for: Create a Python function to calculate Fibonacci numbers"

内置快捷方式

MCP工具

parse_shortcut -展开命令

检测并展开用户输入中的快捷命令。

{
  "name": "parse_shortcut",
  "arguments": {
    "input": "/th How does quantum computing work?"
  }
}

list_shortcuts -浏览可用快捷方式

使用筛选选项查看所有快捷方式。

{
  "name": "list_shortcuts",
  "arguments": {
    "category": "writing",
    "favorites": true
  }
}

快捷方式管理工具

create_shortcut -创建自定义快捷方式

使用自定义提示和模板构建自己的快捷方式。

{
  "name": "create_shortcut",
  "arguments": {
    "command": "/debug",
    "name": "Code Debugger",
    "description": "Help debug code issues",
    "prompt": "You are an expert debugger. Analyze this code and identify potential issues, suggest fixes, and explain your reasoning: {input}",
    "category": "coding",
    "tags": ["debug", "programming", "troubleshooting"]
  }
}

update_shortcut -修改现有快捷方式

更新快捷方式的任何方面。

{
  "name": "update_shortcut",
  "arguments": {
    "id": "shortcut_123",
    "prompt": "Enhanced prompt with better instructions: {input}",
    "isFavorite": true
  }
}

delete_shortcut -删除快捷方式

清理你不再需要的快捷方式。

{
  "name": "delete_shortcut",
  "arguments": {
    "id": "shortcut_123",
    "confirm": true
  }
}

get_shortcut_details -详细视图

获取有关任何快捷方式的全面信息。

{
  "name": "get_shortcut_details",
  "arguments": {
    "id": "shortcut_123"
  }
}

真实世界的例子

创意写作助理

User: "/ider 一个机器人意识觉醒的故事"
→ Creates a compelling sci-fi story about robot consciousness awakening

User: "/th What are the philosophical implications of AI consciousness?"
→ Deep analysis of AI consciousness from multiple perspectives

编程助手

User: "/code Create a REST API for user authentication"
→ Generates clean, documented code with best practices

User: "/debug My React component is not re-rendering properly"
→ Expert debugging assistance with step-by-step solutions

学习助理

User: "/explain How does blockchain technology work?"
→ Simple, clear explanation with analogies and examples

User: "/pros-cons Remote work vs office work"
→ Balanced analysis of advantages and disadvantages

发展

看 docs/DEVELOPMENT.md 详细的开发说明。

项目结构

shortcut-mcp/
├── src/
│   ├── index.ts          # Main server entry point
│   ├── server.ts         # MCP server implementation
│   ├── shortcuts/        # Shortcut interaction logic
│   ├── types/           # TypeScript type definitions
│   └── utils/           # Utility functions
├── docs/                # Documentation
├── examples/            # Example configurations and usage
├── tests/              # Test suites
└── package.json        # Node.js package configuration

贡献

1. 复刻仓库
2. 创建要素分支(git checkout -b feature/amazing-feature)
3. 提交您的更改(git commit -m 'Add amazing feature')
4. 推到分支(git push origin feature/amazing-feature)
5. 打开拉取请求

隐私和安全

• 本地存储：所有快捷方式都存储在本地计算机上
• 无数据收集：您的快捷方式和使用模式保持私密
• 输入验证：所有输入在处理前都经过验证
• 安全执行：模板无需执行代码即可安全扩展

故障排除

常见问题

1. 快捷方式未加载：检查是否 ~/.shortcut-mcp/shortcuts.json 存在且可读
2. 命令无法识别：确保您的命令以开头 / （例如。， /th，不 th)
3. 权限错误：验证MCP是否具有创建快捷方式文件的写入权限
4. 模板变量：使用 {input} 在用户输入的提示模板中

调试模式

启用调试日志记录：

DEBUG=shortcut-mcp:* npm start

👤 作者

朱爱子

• github： @艾子珠
• 项目： 快捷方式mcp

📄 许可证

MIT许可证-请参阅 许可证 文件以获取详细信息。

🙏 致谢

• Apple for Shortcuts应用程序和自动化框架
• 用于协议开发和标准化的MCP社区
• 开源贡献者和TypeScript生态系统
• 早期测试人员和反馈提供者

🗺️ 路线图

核心功能

• \[\]高级模板变量（条件逻辑、循环）
• \[\]快捷方式收集和共享
• \[\]多语言提示模板
• \[\]使用分析和优化建议

平台集成

• \[\]所有MCP平台的自动完成建议
• \[\]特定于平台的UI增强功能
• \[\]移动应用程序兼容性（iOS/Android）
• \[\]基于Web的快捷方式管理界面

生态系统

• \[\]与外部提示库集成
• \[\]社区快捷交易市场
• \[\]自定义行为插件系统
• \[\]用于第三方集成的API

企业功能

• \[\]团队快捷方式共享和管理
• \[\]基于角色的访问控制
• \[\]分析和使用情况报告
• \[\]集中配置管理

\=======

快捷方式mcp

用于自定义提示快捷方式的通用MCP服务器。在Claude Desktop、Cursor、Cline、Continue.dev和任何兼容MCP的平台上，将/th转换为“更努力地思考”的提示。

> > > > > > c402362fc942e18cae89ab3edfcceaa01ec327c3