MakersMCP

io.github.MakersMCP由 GitHub 账号 MakersMCP 发布v0.2.0更新于 Nov 16, 2026

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

已验证Streamable HTTP可网页运行浏览器自动化媒体与设计

概览

MakersMCP 的托管 MCP 服务(mcp.makersmcp.com);需要 OAuth 登录;Streamable HTTP。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

端点
mcp.makersmcp.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 MakersMCP,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.MakersMCP%2Fmakersmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

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

README

[MakersMCP]

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 [email protected]: 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

bash
claude mcp add makersmcp -- npx -y [email protected]

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:

json
{  "mcpServers": {    "makersmcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "[email protected]"]    }  }}

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": "<folder>" } 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:

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

VS Code

bash
code --add-mcp '{"name":"makersmcp","command":"npx","args":["-y","[email protected]"]}'

Codex

bash
codex mcp add makersmcp -- npx -y [email protected]

Windsurf

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

OpenClaw

Add it under mcp.servers in your OpenClaw config:

json
{  "mcp": {    "servers": {      "makersmcp": {        "command": "npx",        "args": ["-y", "[email protected]"]      }    }  }}

Check it with openclaw mcp doctor makersmcp --probe.

Hermes

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

yaml
mcp_servers:  makersmcp:    command: "npx"    args: ["-y", "[email protected]"]    timeout: 60

Other clients

Any MCP client that runs stdio servers can start it with npx -y [email protected].

Run it from source

bash
git clone https://github.com/MakersMCP/makersmcp.gitcd makersmcpnpm installnpm 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 launch-film 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:

bash
npx -y [email protected]                                   # every kitnpx -y [email protected] --kits all                        # every kit, the samenpx -y [email protected] --kits easybrandkit,launch-film   # only these two

In a client's settings, the same goes at the end of args, like ["-y", "[email protected]", "--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 <dir> 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 [email protected] --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 or ffmpeg: set CHROME_PATH and FFMPEG_PATH in the server's env. makersmcp gives them to every kit, to launch-film as LAUNCH_FILM_CHROME and LAUNCH_FILM_FFMPEG too, with LAUNCH_FILM_FFPROBE the ffprobe beside that ffmpeg. Without them, it gives each kit the Chrome and the ffmpeg --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 <list>MAKERSMCP_KITSturns on only these kits, like easybrandkit,launch-film; leave it out or give all for every kit
--out <dir>MAKERSMCP_OUTwhere the folders go, made with the first job; ~ is your home folder
--kit-path <kit>=<dir>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 launch-film is on) and the folder, and exits

Use it in your own server

js
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, 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. 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", "<kit user>", "--", "<wrapper>", "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 on its machines; the tools then take a file an earlier job saved, as job:<job_id>/<path>, or a link where a parameter takes one, instead of paths, and return links to the files. A call that leaves out a parameter with a hosted default reaches such a backend with that value, and a parameter the tools there leave out has it in every call, like jobs 1, so a launch film renders one clip at a time there; a service that starts a job another way gets the kit's own default. Where its job view has a value of another type than JobView gives, like a file whose path is not text, the result leaves that value out and shows the rest. loadKitDefinitions, validateKitDefinition, buildCommand and describeSetup are exported too.

Add a kit

makersmcp has no code for any kit. Each kit is a JSON file in kits/ that names its npm package, its tools, and how each tool's parameters become the kit's arguments. A new kit is a new file there and its package in the dependencies of package.json, which is how it comes with makersmcp; removing a kit is the reverse, and npm test fails while the two do not match. docs/kits.md describes the file.

Develop

bash
npm installnpm test

To try changes to a kit that are not on npm yet, start makersmcp with --kit-path <kit>=<folder>, like --kit-path musicfit=../musicfit, and it runs that checkout instead of the package. npm test tries the bounds of every number in kits/ with each kit's package; MAKERSMCP_KIT_PATHS=musicfit=../musicfit npm test tries the checkout's instead.

MIT

来源:README.md,提交 671750c

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.2.0最新Nov 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分