Skip to main content
Glama
Framer Plugin MCP Server

Framer Plugin MCP Server

by Sheshiyer

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

  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

Available Tools

2 tools
build_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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables programmatic interaction with Framer canvas via a local MCP server and companion plugin, allowing automation of page generation, content updates, and component manipulation.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      MIT