Framer Plugin MCP Server

Framer Plugin MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for creating and managing Framer plugins with web3 capabilities.

What you get

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.

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

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Framer Plugin MCP is connected, these are the calls the assistant has available:

• create_plugin — Parameters: - name: Plugin name - description: Plugin description - outputPath: Output directory path - web3Features: Array of features to include
• build_plugin — The build_plugin tool exposed by this server

Configuration and credentials

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

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the framer plugin mcp mcp server does with a few real requests.

Choosing this one

This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Framer Plugin MCP's toolset — create_plugin, build_plugin — is a fair guide to whether it matches your workflow. It is maintained by Sheshiyer; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Framer Plugin MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.