Framer Plugin MCP Server
# 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:
```bash
git clone https://github.com/sheshiyer/framer-plugin-mcp.git
cd framer-plugin-mcp
```
2. Install dependencies:
```bash
npm install
```
3. Build the server:
```bash
npm run build
```
## Configuration
Add the server to your MCP settings file:
For Claude Desktop App (`~/Library/Application Support/Claude/claude_desktop_config.json`):
```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`):
```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:
```json
{
"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:
```json
{
"pluginPath": "./plugins/my-web3-plugin"
}
```
## Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
## License
MIT License - see LICENSE file for detailsTDQS
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.