MakersMCP
io.github.MakersMCPPublished by GitHub account MakersMCPv0.2.0Updated Nov 16, 2026
Free kits for makers: brand kits, fonts, screenshots, films, music, captions and video formats.
Overview
MakersMCP's hosted MCP server (mcp.makersmcp.com); OAuth sign-in required; Streamable HTTP.
No AI overview yet: these facts come from the registry entry and the server itself.
- Endpoint
- mcp.makersmcp.com
- Documentation
- makersmcp.com
- Last checked
Installation
In SourceWeft
- Open MakersMCP in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.MakersMCP%2Fmakersmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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.
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
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:
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:
VS Code
Codex
Windsurf
Open Settings, then MCP, and add the same entry as for Cursor.
OpenClaw
Add it under mcp.servers in your OpenClaw config:
Check it with openclaw mcp doctor makersmcp --probe.
Hermes
Add it under mcp_servers in ~/.hermes/config.yaml, then run /reload-mcp:
Other clients
Any MCP client that runs stdio servers can start it with npx -y [email protected].
Run it from source
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:
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 --versionsays 22 or newer, then restart the client.npx -y [email protected] --checklists what makersmcp found. - A kit's tools are missing:
--checksays why. Every kit comes with makersmcp, so look at--kitsand--kit-path, and from source runnpm installagain after a pull. - A kit can't find Chrome or ffmpeg: set
CHROME_PATHandFFMPEG_PATHin the server'senv. makersmcp gives them to every kit, to launch-film asLAUNCH_FILM_CHROMEandLAUNCH_FILM_FFMPEGtoo, withLAUNCH_FILM_FFPROBEthe ffprobe beside that ffmpeg. Without them, it gives each kit the Chrome and the ffmpeg--checkshows. A setting names a program by its path, or by a command name on PATH likeffmpeg.--checkalso 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 ajob_idandnext_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
Use it in your own server
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
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.
Source: README.md at commit 671750c
Tools
0Version history
1- v0.2.0LatestNov 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts