mcpField
F
Framer Plugin MCP Server

Framer Plugin MCP Server

Local
github.com/SheshiyerDeveloper Tools37Updated 97w ago

About Framer Plugin MCP Server

Framer Plugin MCP Server is an MCP server for creating and managing Framer plugins with web3 features. It suits developers who want wallet, contract, or NFT functionality inside Framer plugins.

Key features

  1. 01Creates Framer plugin projects with web3 options
  2. 02Builds plugins for production
  3. 03Wallet Connect integration
  4. 04Smart contract interactions
  5. 05NFT display components

Use cases

  1. 01Adding wallet login to a Framer site
  2. 02Displaying NFT content in a Framer plugin
  3. 03Scaffolding plugin projects from an MCP client

MCP support

This project is an MCP server that exposes create_plugin and build_plugin tools to MCP clients for generating and building plugin projects.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Framer Plugin MCP Server

A Model Context Protocol (MCP) server that enables creation and management of Framer plugins with web3 capabilities. This server provides tools for creating, building, and managing Framer plugins with integrated web3 features like wallet connections, contract interactions, and NFT displays.

Features

  • Create new Framer plugins with web3 capabilities
  • Build plugins for production
  • Integrated web3 features:
    • Wallet Connect integration
    • Smart contract interactions
    • NFT display components

Requirements

  • Node.js 16 or higher
  • NPM or Yarn
  • Framer desktop app for testing plugins

Installation

  1. Clone this repository:
git clone https://github.com/sheshiyer/framer-plugin-mcp.git
cd framer-plugin-mcp
  1. Install dependencies:
npm install
  1. Build the server:
npm run build

Configuration

Add the server to your MCP settings file:

For Claude Desktop App (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "framer-plugin": {
      "command": "node",
      "args": ["/path/to/framer-plugin-mcp/build/index.js"]
    }
  }
}

For Cursor/Claude Dev (~/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):

{
  "mcpServers": {
    "framer-plugin": {
      "command": "node",
      "args": ["/path/to/framer-plugin-mcp/build/index.js"]
    }
  }
}

Usage

Once configured, the server provides the following tools:

create_plugin

Creates a new Framer plugin project with web3 capabilities.

Parameters:

  • name: Plugin name
  • description: Plugin description
  • outputPath: Output directory path
  • web3Features: Array of features to include (wallet-connect, contract-interaction, nft-display)

Example:

{
  "name": "my-web3-plugin",
  "description": "A Framer plugin with web3 features",
  "outputPath": "./plugins/my-web3-plugin",
  "web3Features": ["wallet-connect", "nft-display"]
}
build_plugin

Builds a Framer plugin project for production.

Parameters:

  • pluginPath: Path to plugin directory

Example:

{
  "pluginPath": "./plugins/my-web3-plugin"
}

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see LICENSE file for details

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.