Skip to main content
Glama
stephangopaul

MTDevKit

create_flutter_project

Scaffold a new Flutter project with clean architecture, flavors, localization, and Android build configuration. Automates full 11-step setup from a custom template.

Instructions

Scaffold a new Flutter project from the custom clean-architecture template.

Runs the full 11-step setup:

  1. Install/update app_starter_plus

  2. Clone template & rename project

  3. Initialise Git (+ hooks if present)

  4. Install Flutter dependencies

  5. Generate localisations

  6. Update flavorizr.yaml with project name & org

  7. Commit all files before flavorizr

  8. Generate flavors (flavorizr)

  9. Revert main.dart & app.dart (overwritten by flavorizr)

  10. Create config files (dev / uat / prod)

  11. Configure Android build (desugaring, HMS, ProGuard)

Automatically detects fvm; falls back to plain flutter/dart if fvm is not installed. Returns the absolute path to the ready-to-develop project.

NOTE: This tool does NOT ask for confirmation — it runs immediately. Use dry_run=true first if you want to preview the plan before executing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dirNoParent directory to create the project in (default: current working directory)
orgYesOrganisation identifier in reverse-domain, e.g. mu.mt
nameYesDart/Flutter project name, e.g. telecom_app_enterprise
dry_runNoIf true, report what would happen without executing anything
templateNoTemplate repo URL (default: https://bitbucket.org/mtinnovation/flutter_clean_template_2025)
Behavior5/5

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

Discloses immediate execution (no confirmation), automatic fvm detection, absolute path return, and 11-step process. No annotations provided, so description bears full burden.

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

Conciseness4/5

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

Well-structured with numbered steps. Some repetition of process but overall efficient given complexity. Could be slightly shorter.

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

Completeness5/5

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

Covers full 11-step process, return value, and conditional behavior (fvm). No output schema, but description is self-contained and complete.

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 covers 100% of parameters. Description adds minimal value beyond schema, e.g., mentions dry_run for preview but no new semantic detail. Baseline 3.

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

Purpose5/5

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

Clearly states it scaffolds a Flutter project from a custom clean-architecture template. Distinguishes from siblings list_flutter_projects and get_project_info.

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

Usage Guidelines4/5

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

Suggests using dry_run=true first to preview. Provides context on when to use but lacks explicit exclusions or alternatives beyond dry_run.

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/stephangopaul/MTDevKit'

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