Framer Plugin MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_pluginC | Create a new Framer plugin project with web3 capabilities |
| build_pluginC | Build a Framer plugin project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.