Get the FREE Ultimate OpenClaw Setup Guide →

framer-plugin

A Model Context Protocol (MCP) server for creating and managing Framer plugins with web3 capabilities

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio sheshiyer-framer-plugin-mcp node /path/to/framer-plugin-mcp/build/index.js

How to use

The Framer Plugin MCP Server enables the creation and management of Framer plugins with integrated web3 capabilities. It provides tooling to generate new Framer plugins that include wallet connectivity, smart contract interactions, and NFT display components, as well as a build command to package plugins for production. Once configured in your MCP settings, you can access two primary tools: create_plugin and build_plugin. create_plugin scaffolds a new Framer plugin project with the requested web3 features, while build_plugin compiles the plugin for production use, ensuring optimized output for deployment. This server thus streamlines the end-to-end workflow from plugin creation to production-ready builds, all within the MCP ecosystem.

How to install

Prerequisites:

  • Node.js 16 or higher
  • npm or Yarn
  • Access to Framer desktop app for testing plugins

Installation steps:

  1. Clone the MCP repository: git clone https://github.com/sheshiyer/framer-plugin-mcp.git cd framer-plugin-mcp

  2. Install dependencies: npm install

    or if you prefer yarn:

    yarn install

  3. Build the MCP server: npm run build

    or if you use yarn:

    yarn build

  4. Run the server (example): node build/index.js

    Depending on your environment, you may run with a process manager in production.

  5. Configure MCP settings to include the server (see Configuration section in README).

Additional notes

Tips and notes:

  • Ensure Node.js version matches the required 16+ or higher to avoid compatibility issues with build tooling.
  • After building, point your MCP settings to the generated build/index.js path as shown in the README configuration examples.
  • The server exposes two main actions: create_plugin (to scaffold a new Framer plugin with web3 capabilities) and build_plugin (to production-build an existing plugin folder). Use those in your MCP workflow to manage plugin lifecycles.
  • If you encounter path issues, verify that the path in args exactly points to your built index.js and that the file is executable by the runtime.
  • For testing wallet connectivity or contract interactions, ensure you have appropriate environment or testnet configurations in your Framer plugin project to avoid blocking development flows.

Related MCP Servers

Sponsor this space

Reach thousands of developers