Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Manufacturing cost of CNC and sheet-metal parts from STEP or DXF: process plan, times, 10 lot sizes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.arcnm.io/mcp-server/mcp在终端中运行这条命令
claude mcp add --transport http arcnm https://api.arcnm.io/mcp-server/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"arcnm": {
"url": "https://api.arcnm.io/mcp-server/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"arcnm": {
"type": "http",
"url": "https://api.arcnm.io/mcp-server/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.arcnm.io/mcp-server/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 arcnm.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 466 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(4.2.1)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FOGA node
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Manufacturing should-cost from CAD and drawings, for your agent. Connect ARCNM to Claude, GitHub Copilot, Cursor or any MCP client, and it can price a part from a STEP file or PDF drawing, explain what drives the cost, read the process plan, compare designs, lot sizes and costing environments, and nest sheet-metal orders. Every figure traces back to the physics that produced it.
This repository documents the server. ARCNM hosts it, so there is nothing to install or run.
| Endpoint | https://api.arcnm.io/mcp-server/mcp (Streamable HTTP) |
| Registry | io.arcnm/arcnm in the MCP Registry |
| Sign-in | OAuth with your ARCNM account, or an ARCNM API key as a bearer token |
| Docs | arcnm.io/docs/mcp |
An ARCNM account. The Free plan includes 10 calculations a month, no card required. Reading results costs nothing; starting a calculation uses your quota, and check_quota tells your agent how much is left.
Add the server to .vscode/mcp.json:
{
"servers": { "arcnm": { "type": "http", "url": "https://api.arcnm.io/mcp-server/mcp" } } }
Start it from the MCP view and sign in to ARCNM in the browser when asked. To use an API key instead, send it as a header:
{
"inputs": [ { "type": "promptString", "id": "arcnm-key", "description": "ARCNM API key", "password": true } ], "servers": { "arcnm": { "type": "http", "url": "https://api.arcnm.io/mcp-server/mcp", "headers": { "Authorization": "Bearer ${input:arcnm-key}" } } } }
ARCNM is in the Claude connector directory. Add it there and sign in with your ARCNM account.
claude mcp add --transport http arcnm https://api.arcnm.io/mcp-server/mcp
Then run /mcp in Claude Code to sign in. With an API key:
claude mcp add --transport http arcnm https://api.arcnm.io/mcp-server/mcp \
--header "Authorization: Bearer $ARCNM_API_KEY"
In ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": { "arcnm": { "url": "https://api.arcnm.io/mcp-server/mcp" } } }
Cursor opens the ARCNM sign-in. With an API key, add "headers": { "Authorization": "Bearer ${env:ARCNM_API_KEY}" }.
Point a Streamable HTTP transport at https://api.arcnm.io/mcp-server/mcp. A client that supports MCP authorization finds the sign-in on its own, from the server's protected-resource metadata. Otherwise, send Authorization: Bearer .
OAuth. You sign in with your ARCNM account and choose the organization the client may use. The consent screen lists every permission the client asks for, and you can untick any of them. The client sees only that organization's data.
API key. Create one in ARCNM under Settings → API keys and give it only the scopes your agent needs:
| Scope | Lets the agent |
|---|---|
parts:read | read calculations, costs, process plans and costing environments |
parts:write | price parts (upload_and_quote, quote_part) and cancel a calculation |
uploads:write | upload files directly, with the uploads toolset |
Your agent is only ever shown the tools its credential can use.
With no extra configuration, the server lists these 18 tools. Each one carries its readOnlyHint and destructiveHint, so your client knows which calls only read and which ones change something, and can ask you first.
Price a part
| Tool | What it does | |
|---|---|---|
upload_and_quote | Prices a new part from its CAD file in one call: a STEP file, or a DXF flat pattern with its sheet thickness and material, plus an optional PDF drawing. Uses quota only if the calculation succeeds. | write |
get_upload_link | A link to the ARCNM upload page, for a file that is on your computer. | read |
quote_part | Prices a part already in ARCNM again: another lot size, material or costing environment, or several environments at once. Uses quota only if the calculation succeeds. | write |
precheck_part | Reads a CAD file the way its calculation will, before it starts: how an assembly splits into made parts, catalogue parts and parts left out, how many calculations it starts and how many your plan pays for. Free; start it with upload_and_quote and precheck_id. | write |
get_precheck | One precheck: its status and, once read, its answer. | read |
attach_drawing | Gives a drawing to the part it belongs to: before a run, on a precheck, or after it, on the part's calculation, which is then priced again. It plans by default; apply=true attaches. | write |
Follow or stop it
| Tool | What it does | |
|---|---|---|
get_calculation | One calculation: its status, the time left while it runs and, once priced, its result. | read |
list_calculations | Finds calculations, by part, batch, status or start time. | read |
cancel_calculation | Stops a calculation that is queued or running. A cancelled calculation is never charged. | write |
Read the result
| Tool | What it does | |
|---|---|---|
explain_cost | Headline cost and times, the prediction band, the breakdown and the top cost drivers. | read |
get_cost_breakdown | The itemised cost sheet, at any lot size. | read |
get_process_plan | The routing, with work centres and cycle times. | read |
Improve and compare
| Tool | What it does | |
|---|---|---|
preview_cost | Re-prices a calculation with factors moved or at another lot size. Uses no quota and writes nothing. | read |
optimize_lot_size | The lot size with the lowest total cost, and the cost-versus-quantity curve. | read |
suggest_cost_savings | Every cost-reduction direction, each with its lever and confidence. | read |
compare_calculations | Two calculations: the price difference. Three to twenty: a ranking. | read |
Lookups
| Tool | What it does | |
|---|---|---|
list_environments | The organization's costing environments. | read |
check_quota | The organization's remaining calculation quota. | read |
None of these 18 deletes anything. More tools — direct uploads, parts, ranked cost drivers, costing environments and what-if adjustments, job nests for sheet metal, the materials and tooling catalog, calibration, folders — are listed when your client sends the X-MCP-Toolsets header with the toolsets it wants, or all; see toolsets.
The server also ships 5 prompts that walk an agent through a whole job: cost_a_part, compare_calculations, compare_environments, explain_cost and find_cost_drivers.
Questions and problems: hello@arcnm.io, or open an issue here. Documentation: arcnm.io/docs/mcp. Runnable API examples: arcnm/arcnm-examples.
ARCNM is built by rattle mng GmbH in Überlingen, Germany.