AgentHubAgentHub

使用场景/Cursor 开发必备

Cursor 必备 MCP 组合推荐

面向 Cursor 用户的入门组合:文件、GitHub、文档、浏览器。快速搭建 AI 编程工作流。

共匹配 6,490 个资源 · 第 11 / 136 页

什么是Cursor 开发必备?

Cursor 对 MCP 的支持是原生且开箱即用的:在 Settings → MCP 或项目根的 .cursor/mcp.json 中粘贴一段 JSON 即可接入任意 MCP Server。搭配 AgentHub 的一键配置生成器,从发现到接入通常不超过一分钟。

推荐的入门组合覆盖四类高频需求:Filesystem(读写项目文件)、GitHub(PR / Issue / diff)、Context7(最新框架文档,减少幻觉)、Playwright(浏览器验证与 E2E)。之后再按业务补充数据库、抓取或国内服务类 MCP。

本页列出的每个资源都附带 Cursor 专用配置片段:在 AgentHub 打开资源详情页 → 选择 Cursor Tab → 复制 JSON 粘贴即可,安装命令与鉴权环境变量一并给出。

适合做什么

  • 全栈开发
  • 开源贡献
  • 学习新框架
  • 小型自动化脚本

不太适合

  • 纯对话无代码场景
  • 不允许本地进程的企业环境
常见组合: Filesystem + GitHub + Context7 + Playwright

相关资源

查看全部 →

test-collaboration

SkillSkillsMP

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.

source

test-collaboration

SkillSkillsMP

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.

source

SRS 内部代码地图

SkillSkillsMP

把 SRS 与 Oryx 的代码任务路由到最小相关的可信代码库地图与验证指引。只要支持、开发、调试、评审或维护工作需要定位、选择、阅读、修改、测试或验证 SRS/Oryx 代码时使用。覆盖第一代 C++ 源站与边缘媒体服务器及其 State Threads 依赖、下一代 Go 服务器、浏览器推流与播放、SRS Docker 镜像工具链、SRS 测试,以及 Oryx 的 Go 后端、React 控制台、一体化运行时、打包、安装器、发布与测试。作为父级支持与发展技能的代码导航依赖;面向用户的工作流程与结果仍由父技能负责。

source

brownfield-retrospective

SkillSkillsMP

Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.

source

revops(收入运营)

SkillSkillsMP

当用户需要收入运营、线索生命周期管理或市场到销售的交接流程支持时使用。用户提到 RevOps、revenue operations、线索评分、线索路由、MQL、SQL、pipeline stages、deal desk、CRM 自动化、marketing-to-sales handoff、数据清洗、线索没有流转到销售、pipeline 管理、线索资格判定,或“市场何时该交接给销售”等场景时也适用。凡涉及连接市场与收入的系统和流程均可使用。冷邮件触达见 cold-email,邮件序列营销见 emails,定价决策见 pricing。

source

prompt-caching-strategy

SkillSkillsMP

Optimize LLM prompt caching hit rate to reduce API costs and improve latency. Analyzes prompt structure, identifies cacheable vs non-cacheable content, and recommends restructuring to maximize cache reuse. TRIGGER when: user says "prompt cache", "cache hit rate", "reduce LLM cost", "optimize token usage", "cheaper LLM calls", or asks about prompt caching strategies for OpenAI/Anthropic/other providers. DO NOT TRIGGER when: user just wants to optimize a single prompt's quality (use prompt-optimizer instead), or asks about general caching infrastructure.

source

Claude API 参考

SkillSkillsMP

Claude API / Anthropic SDK 参考——模型 id、定价、参数、流式输出、工具调用、MCP、agent、缓存、token 计数、模型迁移。触发条件:提示中出现任何 Claude/Anthropic 相关名称(Claude、Anthropic、Fable、Opus、Sonnet、Haiku 等);用户询问 LLM 相关问题(定价/选型/限额/缓存)时不要凭记忆回答;或任务属于 LLM 类且未指明供应商。仅当明确针对其他供应商(OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama)时跳过。

source

gke-ai-troubleshooting-tpu-performance-degradation

SkillSkillsMP

Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (`gcloud alpha mldiagnostics monitored-events` / `hypercomputecluster.googleapis.com/v1alpha`) and 1-minute Cloud Monitoring system metrics (`kubernetes.io/node/accelerator/*`). Distinguishes hardware and network fabric throttling from workload resource bottlenecks (HBM capacity, host memory, or host CPU saturation). Use when TPU training throughput or duty cycle drops without crashing pods, when `PERFORMANCE_DEGRADATION` monitored events fire, or when triaging slow multi-slice training steps. Don't use for complete multi-slice XLA execution stalls with `HANG_DETECTED` logs (use gke-ai-troubleshooting-tpu-mxla-hang) or pod eviction/interruption restarts (use gke-ai-troubleshooting-jobset-interruption).

source

常见问题

Cursor 里 MCP 配置放在项目还是全局?

两者皆可:项目级 .cursor/mcp.json 随仓库共享给团队,全局 ~/.cursor/mcp.json 对本机所有项目生效。含密钥的配置建议放项目级并加入 .gitignore,或用环境变量引用。

一次接太多 MCP 会影响 Cursor 性能吗?

每个启用的 MCP 都会向上下文注入工具定义,建议按项目启用、用完禁用不常用的服务器,把上下文留给真正需要的工具。

Windows / macOS 配置有区别吗?

JSON 结构相同,差异主要在命令路径与环境变量写法(如 npx 与绝对路径、引号转义)。AgentHub 详情页会区分 stdio 与远程托管(streamable-http/SSE)两类接入方式。

配套安装与配置教程

相关场景