Base Mini App Builder 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 |
|---|---|
| generate_mini_app_manifestC | Generate a complete Base mini app manifest with all required fields. |
| generate_mini_app_codeC | Generate starter code for a Base mini app with MiniKit integration. |
| get_base_deployment_guideC | Get step-by-step deployment guide for Base mini apps. |
| validate_mini_app_requirementsB | Check if your mini app meets Base featured placement requirements. |
| get_base_account_guideB | Get guide for implementing Base Account features like sponsored gas and batch transactions. |
| generate_embed_metadataC | Generate embed metadata for social sharing of your mini app. |
| get_design_guidelinesB | Get comprehensive design guidelines for Base mini apps including colors, typography, spacing, and navigation. |
| get_debugging_guideB | Get comprehensive debugging guide for Base mini app development issues. |
| get_base_app_compatibilityC | Get Base App compatibility information and feature support status. |
| get_search_discovery_guideB | Get guide for optimizing Base mini app search and discovery. |
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 10 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-separated into categories like generation (generate_*), guides (get_*_guide), and validation, each targeting specific aspects of mini app development such as metadata, code, manifests, guides, and requirements checking. There is no overlap in functionality.
The tool names follow a highly consistent verb_noun pattern throughout. All tools use either 'generate_' or 'get_' prefixes followed by descriptive nouns, with consistent snake_case formatting. This predictability makes it easy for agents to understand and select the right tool.
With 10 tools, the count is well-scoped for the server's purpose of Base mini app building. Each tool earns its place by covering essential aspects like code generation, guides, validation, and metadata, providing a comprehensive toolkit without being overwhelming or insufficient.
The tool surface is nearly complete for the domain of Base mini app development, covering generation, guides, and validation. Minor gaps exist, such as the lack of tools for updating or deleting resources, but agents can work around this as the server focuses on creation and guidance rather than full lifecycle management.