Ask for it. It lands in your code.
Plug Moving parts into Claude, Claude Code or Cursor. Your assistant searches the library, reads the sheet of the component and writes its files into your project, byte for byte, with the settings you asked for.
SoonThe MCP server of the library, for every account
(02) Watch it ship
Ask for it. Watch it land.
One sentence to your assistant, and the real component is in your page. Then the next one. Every effect here is the library, recorded as it runs.
(03) Plug it in
One address. One sign-in.
Pick your assistant, paste one line, sign in with your Moving parts account.
SoonThe server is not open yet. This is how it will plug in.
claude mcp add --transport http moving-parts \
https://movingparts.supply/mcp- Run the line in your terminal, in any project.
- Type
/mcp, pick moving-parts, sign in with your Moving parts account. - Ask: “add a pixel trail on my hero”.
Serverhttps://movingparts.supply/mcp
Also works withVS Code · Windsurf · v0 · Zed · Kiro · opencode · any client that speaks MCP
(04) Four tools
What your assistant can reach.
search_componentsThe effects that match what you describe, best firstEvery accountlist_componentsThe whole library by family, one line eachEvery accountget_componentThe sheet: loading, markup, every setting, the API, the pitfallsEvery accountget_component_filesThe script, the stylesheet and the markup, never minifiedMembers, or the free ones(05) Where it runs
Any assistant that speaks MCP.
The Model Context Protocol is the open way assistants reach outside tools. One server, the same library everywhere you work.
- ClaudeDesktop and web
- Claude CodeIn the terminal and the IDE
- CursorAgent mode
- CodexCLI and IDE
- ChatGPTConnectors, developer mode
- Gemini CLIIn the terminal
- AntigravityAgent
- LovablePersonal connectors
- VS CodeCopilot agent mode
- Any MCP clientOne address, one sign-in
No. It only answers with the library: names, sheets, files. Your assistant reads your project and writes into it, on your machine, as it already does.
The same files, byte for byte, read from the same source as the component page. Webflow, code, AI prompt and MCP all ship one engine.
Yes. Search, the list and every sheet are open. The files come with the five free components; the rest of the library is for members.
The one you already work in. A coding assistant that sees your files, like Claude Code or Cursor, goes furthest: it finds where the component belongs and puts it there.