原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

MakersMCP

✓ 品牌同名 GitHub · github.com/makersmcp

作者:MakersMCP版本 0.2.2i★ 1i电脑或云端官方网站 ↗
注册名称io.github.MakersMCP/makersmcp

安装方法

能做什么

Free kits for makers: brand kits, fonts, screenshots, films, music, captions and video formats.

作者提供的原文

  • 连接方式 电脑或云端
  • 账号或密钥 云端:连接时登录该服务(OAuth) · 本地:无需密钥
  • 分类 设计、图片与音频

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

impeccable

The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

作者:pbakaus★ 113,0421 个 skill

Skill · 操作手册

diagram-design

Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.

作者:cathrynlavery★ 68,2961 个 skill

Skill · 操作手册

frontend-slides

Create beautiful slides on the web using a coding agent's frontend skills

作者:zarazhangrui★ 32,5791 个 skill

Skill · 操作手册

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-19

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 5/5 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 MakersMCP。按照 https://mcp.popnx.com/i/makersmcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.makersmcp.com) · ✓ 命令已检查 2026年11月19日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称MakersMCP
    Remote MCP server URL · 地址https://mcp.makersmcp.com/v1

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsMakersMCP

  4. 试一试

    用 MakersMCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 MakersMCP,或回答中出现 MakersMCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称MakersMCP
    Connection · 地址https://mcp.makersmcp.com/v1
  3. 在聊天中选择 MakersMCP

    开启新聊天,输入前先从插件列表中选择 MakersMCP

  4. 试一试

    用 MakersMCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 MakersMCP,或回答中出现 MakersMCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user makersmcp https://mcp.makersmcp.com/v1
  3. 在 Claude Code 中输入 /mcp

    应能看到 MakersMCP 在列表中并显示已连接

  4. 试一试

    用 MakersMCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 MakersMCP,或回答中出现 MakersMCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MakersMCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 MakersMCP,或回答中出现 MakersMCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MakersMCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 MakersMCP,或回答中出现 MakersMCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.makersmcp.com/v1

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 MakersMCP 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user makersmcp https://mcp.makersmcp.com/v1

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "makersmcp": {
      "url": "https://mcp.makersmcp.com/v1"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "makersmcp": {
      "type": "http",
      "url": "https://mcp.makersmcp.com/v1"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user makersmcp -- npx -y makersmcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "makersmcp": {
      "command": "npx",
      "args": [
        "-y",
        "makersmcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "makersmcp": {
      "command": "npx",
      "args": [
        "-y",
        "makersmcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "makersmcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "makersmcp"
      ]
    }
  }
}

需要你填写的值

  • MAKERSMCP_OUT env
    kits 保存其文件夹的位置; 表示你的主文件夹。留空则使用 makersmcp 启动时所在的文件夹;若无法写入该文件夹,则使用 /makersmcp。
    查看英文原文Where the kits save their folders; ~ is your home folder. Leave it out for the folder makersmcp starts in, or ~/makersmcp when it cannot write there.
  • MAKERSMCP_KITS env
    要启用的 kits,用逗号分隔,例如 easybrandkit,launch-film。留空或填写 all 则启用全部 kits。
    查看英文原文The kits to turn on, with commas between them, like easybrandkit,launch-film. Leave it out, or give all, for every kit.
  • MAKERSMCP_KIT_PATHS env
    要代替 makersmcp 自带包运行的 kit 代码检出目录,格式为 kit=folder,多个之间用逗号分隔。
    查看英文原文A kit's checkout to run instead of the package that comes with makersmcp, as kit=folder, with commas between several.
  • CHROME_PATH env
    kits 使用的 Chrome、Chromium、Edge 或 Brave,可通过路径或 PATH 中的命令名指定,适用于 makersmcp 未能自动找到它的情况。
    查看英文原文The Chrome, Chromium, Edge or Brave the kits use, by its path or a command name on PATH, when makersmcp does not find one.
  • FFMPEG_PATH env
    视频和音乐 kits 使用的 ffmpeg,可通过路径或 PATH 中的命令名指定,适用于 makersmcp 未能自动找到它的情况。
    查看英文原文The ffmpeg the video and music kits use, by its path or a command name on PATH, when makersmcp does not find one.
  • FFPROBE_PATH env
    film、reframe 和 caption 工具包用于读取视频的 ffprobe,可通过路径或 PATH 上的命令名指定,当 makersmcp 在 ffmpeg 旁边找不到它时使用。
    查看英文原文The ffprobe the film, reframe and caption kits read videos with, by its path or a command name on PATH, when makersmcp finds none beside ffmpeg.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
103/周
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.2.2
发布到注册中心i
2026年11月19日
代码最后更新i
2026年11月17日
最近检查
2026年11月16日
作者
MakersMCP
软件包
npm: makersmcp
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 MakersMCP 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3天前

  • ✓ 通过

    有许可证

    使用 MIT

  • ✓ 通过

    端点有响应

    在 467 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

已公开的漏洞(OSV.dev)

尚未检查

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/makersmcp.svg)](https://mcp.popnx.com/en/servers/makersmcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“设计、图片与音频”中的其他服务器比较i

  • 星标数多于此分类中其他 3313 个服务器的 79%
  • 发布到注册中心的时间比此分类中其他 3313 个服务器的 99% 更新
  • 基础检查结果等于或优于此分类中其他 3313 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MakersMCP 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于3天前,最新版本(0.2.2)于昨天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

作者:pascalorg广泛使用↓ 1037/周★ 2.6万 整个仓库的星标前天更新

电脑或云端✓ 服务方 · pascal.app

draw.io

Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.

作者:jgraph广泛使用★ 58603天前更新

在云端运行✓ 服务方 · draw.ioPopNx 团队已实际试用

Figma MCP Server

The Figma MCP server brings Figma design context directly into your AI workflow.

作者:figma广泛使用★ 221313个月前更新

在云端运行✓ 服务方 · mcp.figma.com
与相似项目对比
本项
MakersMCP
HyperFrames by HeyGenPascal 3D Editordraw.ioFigma MCP ServerRemocn: Remotion MCP server
运行位置云端或安装在电脑上都可以在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是否否是否
基础检查5/54/45/54/44/44/4
许可证MITApache-2.0MITApache-2.0–MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

#

Free kits for makers, one MCP. https://makersmcp.com

Open source kits for people who make things, from creators to product teams: image, video, sound, design and more. MakersMCP serves every kit to your agent through one MCP server, and they all run on your own machine, with no account or key.

The kits

Each kit lives in its own repository and works on its own too, as a CLI and an agent skill. makersmcp comes with all of them, so no kit needs installing on its own.

FieldKitTools
Designeasybrandkit: a website's logo files, colors, fonts and first screenmake_brand_kit
Designeasyfontkit: a site's fonts with their licenses and free look-alikesmake_font_kit
Imageeasyscreenshotkit: clean screenshots and a short demo video of a websitetake_screenshots, record_demo_video, check_pwa_screenshots
Videolaunch-film: a launch film with music, the launch pictures, and a check for any videomake_launch_film, plan_launch_film, render_launch_film, make_launch_stills, check_video, launch_film_guide
Videoreframekit: one finished video in the shape, length and size each place takes, and a check of any file against a place's limitsreframe_video, plan_reframe, check_place_limits
Videoeasycaptionkit: captions burned into a video in the brand's fonts, clear of each app's buttons, with the subtitle filescaption_video, make_subtitles, list_caption_styles
Soundmusicfit: a music track cut to fit your video and laid under itfit_music, analyze_music

More kits are on the way.

Set it up

You need Node 22 or newer and the Chrome, Chromium, Edge or Brave you already have. Demo videos, launch films, music, reframed videos and captions also need ffmpeg, which comes with ffprobe. Every setup runs npx -y makersmcp@0.2.1: keep the version in it, since npx can otherwise go on using an older copy it cached.

Then ask your agent for what you need, like "make a launch film for linear.app" or "get the brand kit and the fonts of stripe.com".

Claude Code
claude mcp add makersmcp -- npx -y makersmcp@0.2.1

Check it with claude mcp get makersmcp, or /mcp inside Claude Code.

Claude Desktop

Add this to claude_desktop_config.json, then quit Claude Desktop fully and open it again:

{

"mcpServers": { "makersmcp": { "type": "stdio", "command": "npx", "args": ["-y", "makersmcp@0.2.1"] } } }

Claude Desktop starts servers outside any project, so the files go to ~/makersmcp, which makersmcp makes with the first job. For another folder, add "env": { "MAKERSMCP_OUT": " " } to the entry, like "~/Documents/makersmcp": a leading ~ is your home folder.

Cursor

Open the command palette (Cmd+Shift+P, or Ctrl+Shift+P on Windows and Linux), run "Open MCP settings" and add:

{

"mcpServers": { "makersmcp": { "command": "npx", "args": ["-y", "makersmcp@0.2.1"] } } }

VS Code
code --add-mcp '{"name":"makersmcp","command":"npx","args":["-y","makersmcp@0.2.1"]}'
Codex
codex mcp add makersmcp -- npx -y makersmcp@0.2.1
Windsurf

Open Settings, then MCP, and add the same entry as for Cursor.

OpenClaw

Add it under mcp.servers in your OpenClaw config:

{

"mcp": { "servers": { "makersmcp": { "command": "npx", "args": ["-y", "makersmcp@0.2.1"] } } } }

Check it with openclaw mcp doctor makersmcp --probe.

Hermes

Add it under mcp_servers in ~/.hermes/config.yaml, then run /reload-mcp:

mcp_servers:

makersmcp: command: "npx" args: ["-y", "makersmcp@0.2.1"] timeout: 60

Other clients

Any MCP client that runs stdio servers can start it with npx -y makersmcp@0.2.1.

Run it from source
git clone https://github.com/MakersMCP/makersmcp.git

cd makersmcp npm install npm run build

In any setup above, use node as the command and the full path of dist/index.js as its argument. node dist/index.js --check lists the kits it found, the Chrome and the ffmpeg found for them (and ffprobe while a kit that reads videos with it is on) and the folder it saves to.

Pick your kits

Every kit is on unless you say otherwise. To give your agent fewer tools, name the kits you use:

npx -y makersmcp@0.2.1                                   # every kit

npx -y makersmcp@0.2.1 --kits all # every kit, the same npx -y makersmcp@0.2.1 --kits easybrandkit,launch-film # only these two

In a client's settings, the same goes at the end of args, like ["-y", "makersmcp@0.2.1", "--kits", "easybrandkit,launch-film"].

Where the files go

Every tool saves its files in a folder and returns the folder, the files it saved there and the kit's own notes, like BRAND.md. The folders go where makersmcp starts, which is your project for a coding agent, or ~/makersmcp when it can't write there; a folder that is not there yet is made with the first job. A tool given a video, like reframe_video or caption_video, saves in a folder next to that video. Every kit puts a run's files in place only once the run has ended well, so a run that fails or is canceled leaves its folder as it was. Choose another place with --out or MAKERSMCP_OUT, or give a tool its own out_dir. A call with an argument the tool does not take, like output_dir, is refused with the one it most likely meant, and starts nothing.

launch-film keeps the brand kit a film uses in a brand/ folder next to film.json. When it plans from a brand kit you give it, it deletes that folder and makes it again, and from an App Store page it may; from any other site, easybrandkit makes the kit again in it, replacing only a kit's own files. Its tools tell the client they may replace files, and they do not start when makersmcp finds they would lose anything in that brand/ but a kit's own files: a file you added, a file named like a kit's own in other letters or with a character that does not show, a link the kit would delete files through, or a kit you give that is that same brand/ folder under another name, holds it, or has its brand.json as a link into it. To use a brand/ folder where it is, give it as brand written the way out_dir is, with /brand added. makersmcp looks only before the kit starts, and a folder mounted from the same disk, inside brand/ or as the out_dir, can still hide from it where it really is, so keep files you care about outside brand/.

A long job, like rendering a film, keeps going after the tool returns. The tool then gives back a job_id, and your agent calls wait_for_job with it until the job ends. list_jobs and cancel_job do what they say, and check_setup tells what is missing when a kit fails to start. When the client closes makersmcp, or makersmcp ends some other way, its jobs stop too, with the browsers and ffmpeg they started.

When something fails

  • The tools don't appear: check that node --version says 22 or newer, then restart the client. npx -y makersmcp@0.2.1 --check lists what makersmcp found.
  • A kit's tools are missing: --check says why. Every kit comes with makersmcp, so look at --kits and --kit-path, and from source run npm install again after a pull.
  • A kit can't find Chrome, ffmpeg or ffprobe: set CHROME_PATH and FFMPEG_PATH in the server's env, and FFPROBE_PATH for an ffprobe that is not beside that ffmpeg. makersmcp gives them to every kit, to launch-film as LAUNCH_FILM_CHROME, LAUNCH_FILM_FFMPEG and LAUNCH_FILM_FFPROBE too, with the ffprobe beside that ffmpeg when no FFPROBE_PATH is set. Without them, it gives each kit the Chrome, the ffmpeg and the ffprobe --check shows. A setting names a program by its path, or by a command name on PATH like ffmpeg. --check also names a setting that leads to no program, and until it is fixed makersmcp starts no tool that reads a program from it.
  • A long job meets the client's time limit: no call waits longer than wait_seconds, 45 by default, counted from the start of the call. A job still running then comes back with a job_id and next_action: wait_for_job, and the agent should call that, never the first tool again, which would start a second job. A call the client gave up on is still covered: the same call again within 10 minutes continues its job, and says so, instead of starting another. Where a client lets you set a tool timeout, keep it above 45 seconds.

Settings

OptionEnvironmentWhat it does
--kits MAKERSMCP_KITSturns on only these kits, like easybrandkit,launch-film; leave it out or give all for every kit
--out MAKERSMCP_OUTwhere the folders go, made with the first job; ~ is your home folder
--kit-path = MAKERSMCP_KIT_PATHSruns a kit's checkout instead of the package that comes with makersmcp; ~ is your home folder
--checkprints the kits, the Chrome and the ffmpeg found for them (and ffprobe while a kit that reads videos with it is on) and the folder, and exits

Use it in your own server

import { serveStdio } from 'makersmcp';

await serveStdio({ kits: ['easybrandkit', 'launch-film'], outDir: '/srv/makersmcp' });

serveStdio serves on stdin and stdout and ends the process when the client goes away. createMcpServer takes the same options, kits, outDir, kitPaths, definitions, backend and maxToolInputElements, and works over any MCP transport; close the server when the client is gone, since the stdio transport alone never notices. maxToolInputElements is the most array items and object members one tool call may carry, 10,000 unless you give another, and Infinity turns that check off: a call with more gets one short error before its arguments are checked, and starts nothing. A kit tool call identical to one whose answer did not reach the client, cancelled or cut off with its connection, or to one that ended in an error after its job started, continues that call's job for 10 minutes, and so does one made at least 10 seconds after an identical call that still waits; repeatTiming changes both times, whose defaults the package exports as REPEAT_TIMING, and one process keeps at most MAX_REPEAT_RECORDS, 1,000, of those calls, the oldest going first. This holds for the calls of one backend identity in one process: LocalBackend has one of its own, and a hosted backend gives the user its jobs belong to. The backend decides where the jobs run. The default, LocalBackend, runs them on this machine and stops them when the server closes or the process ends. A service that runs kits for others can give LocalBackend an env of its own, so its secrets never reach a kit, and confine: true, so no tool call can name a file or folder outside baseDir, and no job returns a doc or lists a file a kit left outside it or behind a link. To run its kits as another user, it gives a launcher: a command that execs makersmcp's dist/supervise.js in place of itself with the kit's script and arguments, like ["sudo", "-n", "-u", " ", "--", " ", "run"]. No signal reaches another user's processes, so a cancel then closes the supervisor's stdin, and the supervisor stops the kit; a job's pid is its process group, the one to keep while it runs when the service sweeps up what kits left behind. A service can also pass its own KitBackend (src/backend.ts) to run them o

只显示了开头部分;其余内容请在仓库中阅读