Skip to main content
Glama
Sheshiyer

Framer Plugin MCP Server

by Sheshiyer

build_plugin

Compile a Framer plugin project from a specified directory to enable web3 features such as wallet connections, contract interactions, and NFT displays.

Instructions

Build a Framer plugin project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pluginPathYesPath to plugin directory

Implementation Reference

  • The handler function that implements the build_plugin tool. It resolves the plugin directory, verifies it exists, executes 'npm run build' in that directory, and returns a success message.
    private async handleBuildPlugin(args: BuildPluginArgs) {
      try {
        const pluginDir = path.resolve(args.pluginPath);
        
        // Verify plugin directory exists
        if (!await fs.pathExists(pluginDir)) {
          throw new Error(`Plugin directory not found: ${pluginDir}`);
        }
    
        // Run build command
        const { execSync } = require('child_process');
        execSync('npm run build', { cwd: pluginDir, stdio: 'inherit' });
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully built plugin at ${pluginDir}`
            }
          ]
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to build plugin: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • TypeScript interface defining the input parameters for the build_plugin tool: pluginPath (string).
    interface BuildPluginArgs {
      pluginPath: string;
    }
  • src/index.ts:93-106 (registration)
    Tool registration in the ListTools response, including name, description, and JSON input schema.
    {
      name: 'build_plugin',
      description: 'Build a Framer plugin project',
      inputSchema: {
        type: 'object',
        properties: {
          pluginPath: {
            type: 'string',
            description: 'Path to plugin directory'
          }
        },
        required: ['pluginPath']
      }
    }
  • src/index.ts:114-115 (registration)
    Dispatch case in the CallToolRequest handler that routes to the build_plugin handler function.
    case 'build_plugin':
      return this.handleBuildPlugin(request.params.arguments as unknown as BuildPluginArgs);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Build' implies a potentially complex or resource-intensive operation, but the description doesn't mention side effects, permissions, output format, or error conditions. It lacks critical behavioral details for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'build' entails (e.g., compilation, packaging), what the result is, or any behavioral context. For a tool with no structured metadata, this minimal description leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the single parameter 'pluginPath' is documented in the schema), so the baseline is 3. The description adds no additional parameter information beyond what's in the schema, but it doesn't need to compensate for gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Build') and target resource ('a Framer plugin project'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'create_plugin', which might be a related but distinct operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_plugin', nor does it mention prerequisites, context, or exclusions. It simply states what the tool does without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sheshiyer/framer-plugin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server