impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Free kits for makers: brand kits, fonts, screenshots, films, music, captions and video formats.
Skills that teach the AI this kind of work; they work alongside this one
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
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.
Create beautiful slides on the web using a coding agent's frontend skills
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 20/100 | Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-11-19 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 5/5 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install MakersMCP. Follow https://mcp.popnx.com/i/makersmcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (mcp.makersmcp.com) · ✓ Commands checked Nov 19, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
MakersMCPhttps://mcp.makersmcp.com/v1Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsMakersMCP
Use MakersMCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using MakersMCP or shows a MakersMCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
MakersMCPhttps://mcp.makersmcp.com/v1Start a new chat and pick MakersMCP from your plugins before typing
Use MakersMCP and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using MakersMCP or shows a MakersMCP tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user makersmcp https://mcp.makersmcp.com/v1You should see MakersMCP listed as connected
Use MakersMCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using MakersMCP or shows a MakersMCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use MakersMCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using MakersMCP or shows a MakersMCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use MakersMCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using MakersMCP or shows a MakersMCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.makersmcp.com/v1JSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user makersmcp https://mcp.makersmcp.com/v1Cursor (~/.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 makersmcpClaude 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 envMAKERSMCP_KITS envMAKERSMCP_KIT_PATHS envCHROME_PATH envFFMPEG_PATH envFFPROBE_PATH envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: makersmcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account MakersMCP, which owns the repo
Code last changed 3 days ago
Uses MIT
Responded in 467 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/makersmcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 3 days ago, and the latest version (0.2.2) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| This one MakersMCP | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | Yes | No |
| Basic checks | 5/5 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| License | MIT | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
#
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.
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.
| Field | Kit | Tools |
|---|---|---|
| Design | easybrandkit: a website's logo files, colors, fonts and first screen | make_brand_kit |
| Design | easyfontkit: a site's fonts with their licenses and free look-alikes | make_font_kit |
| Image | easyscreenshotkit: clean screenshots and a short demo video of a website | take_screenshots, record_demo_video, check_pwa_screenshots |
| Video | launch-film: a launch film with music, the launch pictures, and a check for any video | make_launch_film, plan_launch_film, render_launch_film, make_launch_stills, check_video, launch_film_guide |
| Video | reframekit: one finished video in the shape, length and size each place takes, and a check of any file against a place's limits | reframe_video, plan_reframe, check_place_limits |
| Video | easycaptionkit: captions burned into a video in the brand's fonts, clear of each app's buttons, with the subtitle files | caption_video, make_subtitles, list_caption_styles |
| Sound | musicfit: a music track cut to fit your video and laid under it | fit_music, analyze_music |
More kits are on the way.
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 mcp add makersmcp -- npx -y makersmcp@0.2.1
Check it with claude mcp get makersmcp, or /mcp inside Claude Code.
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.
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"] } } }
code --add-mcp '{"name":"makersmcp","command":"npx","args":["-y","makersmcp@0.2.1"]}'
codex mcp add makersmcp -- npx -y makersmcp@0.2.1
Open Settings, then MCP, and add the same entry as for Cursor.
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.
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
Any MCP client that runs stdio servers can start it with npx -y makersmcp@0.2.1.
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.
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"].
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.
node --version says 22 or newer, then restart the client. npx -y makersmcp@0.2.1 --check lists what makersmcp found.--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.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.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.| Option | Environment | What it does |
|---|---|---|
--kits | MAKERSMCP_KITS | turns on only these kits, like easybrandkit,launch-film; leave it out or give all for every kit |
--out | MAKERSMCP_OUT | where the folders go, made with the first job; ~ is your home folder |
--kit-path = | MAKERSMCP_KIT_PATHS | runs a kit's checkout instead of the package that comes with makersmcp; ~ is your home folder |
--check | prints 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 |
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