Framer Plugin MCP Server
The Framer Plugin MCP Server enables the creation and management of Framer plugins with integrated web3 capabilities.
Create Framer Plugins: Build new plugin projects with customizable web3 features
Web3 Integration: Add wallet connections, smart contract interactions, and NFT displays
Build for Production: Compile and prepare existing plugins for production use
Enables creation and management of Framer plugins with web3 capabilities, including wallet connections, smart contract interactions, and NFT displays
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Framer Plugin MCP Server create a new plugin called Web3Gallery with wallet connect and NFT display features"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Framer Bridge MCP
Requirements
Node.js 16 or higher
NPM or Yarn
Framer desktop app for testing plugins
Installation
Clone this repository:
git clone https://github.com/sheshiyer/framer-plugin-mcp.git
cd framer-plugin-mcpInstall dependencies:
npm installBuild the server:
npm run buildConfiguration
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
Available Tools
2 toolsbuild_pluginC
Build a Framer plugin project
Inputs: pluginPath (required).
create_pluginC
Create a new Framer plugin project with web3 capabilities
Inputs: description (required), name (required), outputPath (required), web3Features.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'build_plugin' handles compiling an existing project, while 'create_plugin' initiates a new project with specific web3 features. There is no overlap in functionality, making tool selection straightforward for an agent.
Both tools follow a consistent verb_noun naming pattern ('build_plugin' and 'create_plugin'), using snake_case and clear action verbs. This uniformity aids in predictability and readability across the tool set.
With only two tools, the server feels under-scoped for a plugin development domain. Typical plugin workflows would require additional operations like testing, deploying, or managing dependencies, making this set too thin for comprehensive agent support.
The tool set is severely incomplete for Framer plugin development. It lacks essential CRUD operations such as updating, deleting, or testing plugins, and misses lifecycle coverage like deployment or version management, which are critical for this domain.
Maintenance
Related MCP Connectors
Edit and publish your FramerToNextJS sites (converted Framer or AI-built) from Claude, Cursor or Codex. 19 tools: read pages, rewrite copy, restyle elements, add sections and pages, design Studio sites, manage CMS collections and items, then publish to your own host. OAuth with a read-only option, and MCP runs no model on FNJ's side. Requires an FNJ plan (Lifetime or any AI builder plan).
Create, change and install StellaFrame website widgets from an AI agent. OAuth sign-in, no API key.
Helps AI coding agents integrate MetaMask Embedded Wallets (Web3Auth) SDKs.
AI-powered design and management for Webflow Sites
Related MCP Servers
- AlicenseBqualityDmaintenanceThis plugin enables interaction with blockchain data and NFTs through the Alchemy SDK, allowing operations such as retrieving NFT metadata, fetching NFTs for wallet addresses, and getting the latest block number.22ISC
- AlicenseNot gradedqualityDmaintenanceConnects IDEs to the Framer and Framer Motion ecosystem by providing animation snippets and React component scaffolding. It enables users to generate high-fidelity UI effects and code-ready components compatible with Framer's property controls.ISC
- FlicenseNot gradedqualityDmaintenanceEnables programmatic interaction with Framer canvas via a local MCP server and companion plugin, allowing automation of page generation, content updates, and component manipulation.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Webflow's Data API and Designer through natural language, supporting content analysis, blog and SEO workflows, internal linking, and on-canvas design creation such as responsive sections and CTA buttons. It offers both a remote OAuth-authenticated setup and a local install using a Webflow API token.501 npmMIT