Skip to main content
Glama
Mr-Web3

Base Mini App Builder MCP Server

by Mr-Web3

generate_mini_app_manifest

Generate a complete Base mini app manifest with all required fields including app name, description, category, and domain to streamline development workflow.

Instructions

Generate a complete Base mini app manifest with all required fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYesName of your mini app (max 32 chars)
categoryYesPrimary category for the app
descriptionYesApp description (max 170 chars)
domainYesYour app domain (e.g., myapp.vercel.app)
tagsNoSearch tags (max 5, lowercase, no spaces)

Implementation Reference

  • server.ts:72-107 (registration)
    Registration of the 'generate_manifest' tool in the ListTools response, including name, description, and input schema for generating the mini app manifest.
    {
      name: 'generate_manifest',
      description: 'Generate and save the Base mini app manifest file.',
      inputSchema: {
        type: 'object',
        properties: {
          project_path: {
            type: 'string',
            description: 'Path to the project directory',
          },
          app_name: {
            type: 'string',
            description: 'Name of your mini app (max 32 chars)',
          },
          description: {
            type: 'string',
            description: 'App description (max 170 chars)',
          },
          category: {
            type: 'string',
            description: 'Primary category for the app',
            enum: ['games', 'social', 'finance', 'utility', 'productivity', 'health-fitness', 'news-media', 'music', 'shopping', 'education', 'developer-tools', 'entertainment', 'art-creativity'],
          },
          domain: {
            type: 'string',
            description: 'Your app domain (e.g., myapp.vercel.app)',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Search tags (max 5, lowercase, no spaces)',
          },
        },
        required: ['project_path', 'app_name', 'description', 'category', 'domain'],
      },
    },
  • The main handler implementation for the 'generate_manifest' tool. It constructs a complete Base mini app manifest object, creates the necessary directory, writes the farcaster.json file, and returns success/error messages with next steps.
        case 'generate_manifest': {
          const { project_path, app_name, description, category, domain, tags = [] } = args as any;
          
          const manifest = {
            accountAssociation: {
              header: "",
              payload: "",
              signature: ""
            },
            baseBuilder: {
              allowedAddresses: [""]
            },
            miniapp: {
              version: "1",
              name: app_name,
              homeUrl: `https://${domain}`,
              iconUrl: `https://${domain}/icon.png`,
              splashImageUrl: `https://${domain}/splash.png`,
              splashBackgroundColor: "#000000",
              webhookUrl: `https://${domain}/api/webhook`,
              subtitle: description.substring(0, 30),
              description: description,
              screenshotUrls: [
                `https://${domain}/screenshot1.png`,
                `https://${domain}/screenshot2.png`,
                `https://${domain}/screenshot3.png`
              ],
              primaryCategory: category,
              tags: tags.length > 0 ? tags : ["base", "miniapp", "web3"],
              heroImageUrl: `https://${domain}/hero.png`,
              tagline: "Built on Base",
              ogTitle: app_name,
              ogDescription: description,
              ogImageUrl: `https://${domain}/og.png`,
              noindex: true
            }
          };
    
          try {
            // Create .well-known directory
            const wellKnownDir = path.join(project_path, 'public', '.well-known');
            createDirectory(wellKnownDir);
            
            // Write manifest file
            writeFile(
              path.join(wellKnownDir, 'farcaster.json'),
              JSON.stringify(manifest, null, 2)
            );
    
          return {
            content: [
              {
                type: 'text',
                  text: `# ✅ Manifest Generated Successfully!
    
    ## Manifest Details:
    - **App Name**: ${app_name}
    - **Category**: ${category}
    - **Domain**: ${domain}
    - **Location**: ${path.join(wellKnownDir, 'farcaster.json')}
    
    ## Next Steps:
    1. **Deploy your app** to get a live URL
    2. **Generate accountAssociation** at https://base.dev/preview?tab=account
    3. **Update manifest** with the generated credentials
    4. **Test validation** at https://base.dev/preview
    
    ## Required Images:
    - Icon: 1024x1024px PNG
    - Splash: 200x200px PNG  
    - Screenshots: 1284x2778px PNG (portrait)
    - Hero: 1200x630px PNG
    - OG Image: 1200x630px PNG
    
    Your manifest is ready! 🎉`,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: 'text',
                  text: `❌ Error generating manifest: ${error instanceof Error ? error.message : 'Unknown error'}`,
              },
            ],
          };
          }
        }
  • Helper function used by the manifest handler to create the public/.well-known directory if it doesn't exist.
    function createDirectory(dirPath: string) {
      if (!fs.existsSync(dirPath)) {
        fs.mkdirSync(dirPath, { recursive: true });
      }
    }
  • Helper function used by the manifest handler to write the manifest JSON file, ensuring the directory exists first.
    function writeFile(filePath: string, content: string) {
      const dir = path.dirname(filePath);
      createDirectory(dir);
      fs.writeFileSync(filePath, content);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool generates a manifest but lacks details on output format, whether it's a read-only operation, potential side effects, or any constraints like rate limits or authentication needs. This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence that front-loads the core action ('Generate a complete Base mini app manifest') and specifies the scope ('with all required fields'). There is no wasted text, making it highly concise and well-structured.

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 complexity of generating a manifest with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the output looks like, how to handle the generated manifest, or any behavioral traits, leaving the agent with incomplete context for proper tool invocation.

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?

The input schema has 100% description coverage, clearly documenting all 5 parameters with details like max lengths and enum values. The description adds no additional parameter semantics beyond implying it generates a 'complete' manifest, which aligns with the schema but doesn't provide extra value. This meets the baseline for high schema coverage.

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 verb 'Generate' and the resource 'complete Base mini app manifest with all required fields', which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'generate_mini_app_code' or 'validate_mini_app_requirements', which might also relate to mini app creation or validation.

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. It doesn't mention prerequisites, context for generating manifests, or how it relates to sibling tools such as 'generate_mini_app_code' or 'validate_mini_app_requirements', leaving the agent to infer usage scenarios.

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

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/Mr-Web3/BaseKit-MCP'

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