Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Model Context Protocol (MCP) server for AI-assisted development of CAP applications.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"cap-js": {
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}
}在终端中运行这条命令
claude mcp add cap-js -- npx -y @cap-js/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cap-js": {
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cap-js": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 cap-js 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于11天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, topo^alpin
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Model Context Protocol (MCP) server for the SAP Cloud Application Programming Model (CAP). Use it for AI-assisted development of CAP applications (_agentic coding_).
The server helps AI models answer questions such as:
search_modelsearch_docsSee Getting Started on how to jumpstart your development and grow as you go with SAP Cloud Application Programming Model.
Configure your MCP client (Cline, opencode, Claude Code, GitHub Copilot, etc.) to start the server using the command npx -y @cap-js/mcp-server as in the following examples.
Register the server with Claude Code.
For all projects (user scope):
claude mcp add --scope user cds-mcp -- npx -y @cap-js/mcp-server
For the current project only (local scope, not committed):
claude mcp add cds-mcp -- npx -y @cap-js/mcp-server
For the current project only (committed to the repository):
claude mcp add --scope project cds-mcp -- npx -y @cap-js/mcp-server
To set an environment variable, add --env before the server name:
claude mcp add --scope user --env CDS_MCP_MODEL=nomic-ai/nomic-embed-text-v1.5 cds-mcp -- npx -y @cap-js/mcp-server
Example for VS Code extension Cline:
{
"mcpServers": { "cds-mcp": { "command": "npx", "args": ["-y", "@cap-js/mcp-server"], "env": {} } } }
Example for VS Code global mcp.json:
Note: GitHub Copilot uses the
mcp.jsonfile as source for it's Agent mode.
{
"servers": { "cds-mcp": { "command": "npx", "args": ["-y", "@cap-js/mcp-server"], "env": {}, "type": "stdio" }, "inputs": [] } }
To set an environment variable, replace the server's empty env object with:
"env": {
"CDS_MCP_MODEL": "nomic-ai/nomic-embed-text-v1.5" }
See VS Code Marketplace for more agent extensions.
Register the server with OpenAI Codex:
codex mcp add cds-mcp -- npx -y @cap-js/mcp-server
To set an environment variable, add --env before the command:
codex mcp add cds-mcp --env CDS_MCP_MODEL=nomic-ai/nomic-embed-text-v1.5 -- npx -y @cap-js/mcp-server
Add to opencode.jsonc in your project, or to ~/.config/opencode/opencode.jsonc for global use:
{
"$schema": "https://opencode.ai/config.json", "mcp": { "cds-mcp": { "type": "local", "command": ["npx", "-y", "@cap-js/mcp-server"], "environment": { "CDS_MCP_MODEL": "nomic-ai/nomic-embed-text-v1.5" }, "enabled": true } } }
This is the opencode v1 format. In opencode v2, use the same config but nest the server under "servers" — "mcp": { "servers": { "cds-mcp": { ... } } } — or use the CLI instead:
opencode mcp add --global cds-mcp -- npx -y @cap-js/mcp-server
To set an environment variable:
opencode mcp add --global cds-mcp \
--env CDS_MCP_MODEL=nomic-ai/nomic-embed-text-v1.5 \ -- npx -y @cap-js/mcp-server
[!WARNING]
The following environment variables are still experimental.
| Variable | Description |
|---|---|
CDS_MCP_OFFLINE | Set to true to use locally cached embeddings without checking for updates. Accepts true or false. |
CDS_MCP_MODEL | Non-empty embedding model name. |
CDS_MCP_MANIFEST_TIMEOUT | Manifest request timeout in positive integer milliseconds. Defaults to 15000. |
CDS_MCP_DOWNLOAD_TIMEOUT | Bundle response-header timeout in positive integer milliseconds. Defaults to 30000. |
CDS_MCP_GENERIC_EMBEDDINGS | Set to true to skip the runtime filter and search all runtimes. By default search_docs keeps only the chunks of the detected project runtime (Node.js or Java) plus the runtime-agnostic chunks. |
CDS_MCP_MAX_RESULTS | Upper limit on the number of search_docs results, as a positive integer. Caps the per-call maxResults. |
CDS_MCP_RERANK_ENABLED | Set to true to rerank search_docs results with a local cross-encoder model. Accepts true or false; disabled by default. |
CDS_MCP_RERANK_MODEL | Non-empty cross-encoder model name used when reranking. Defaults to Xenova/ms-marco-MiniLM-L-6-v2. |
CDS_MCP_RERANK_DTYPE | Non-empty data type used to load the reranking model. Defaults to q8; set to fp32 for models without model_quantized.onnx. |
CDS_MCP_RERANK_EXTERNAL_DATA | Set to true for reranking models whose ONNX weights are stored in external .onnx_data files. Accepts true or false. |
CDS_MCP_RERANK_BATCH_SIZE | Positive integer number of results to process in each reranking batch. Defaults to 1. |
The following rules help the LLM use the server correctly:
- You MUST search for CDS definitions, like entities, fields and services (which include HTTP endpoints) with cds-mcp, only if it fails you MAY read \*.cds files in the project.
cds CLI from CAP. Do NOT propose, suggest or make any changes without first checking it.
Add these rules to your existing global or project-specific AGENTS.md (specifics may vary based on respective MCP client).
You can also use the tools directly from the command line.
npm i -g @cap-js/mcp-server
[!WARNING]
When the package is installed globally,
npxuses the installed version instead of downloading the latest from npm. You must update the package manually:
`sh
npm update -g @cap-js/mcp-server
`
This will provide the command cds-mcp, with which you can invoke the tools directly as follows.
# Search CAP documentation
cds-mcp search_docs "how to add columns to a select statement in CAP Node.js" 1
cds-mcp search_model . Books entity
[!NOTE]
Tools are meant to be used by AI models and do not constitute a stable API.
The server provides these tools for CAP development:
search_docsThis tool uses vector embeddings to locally search through preprocessed CAP documentation, stored as embeddings. The process works as follows:
This semantic search approach enables you to find relevant documentation even when your query does not use the exact keywords found in the docs, all locally on your machine.
search_modelThis tool performs fuzzy searches against names of definitions from the compiled CDS model (Core Schema Notation). CDS compiles all your .cds files into a unified model representation that includes:
The fuzzy search algorithm matches definition names and allows for partial matches, making it easy to find entities like "Books" even when searching for "book".
This project is open to feature requests/suggestions, bug reports, and so on, via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please don't create GitHub issues for security-related doubts or problems.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Copyright 2025 SAP SE or an SAP affiliate company and @cap-js/cds-mcp contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.