MTDevKit
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_flutter_projectA | Scaffold a new Flutter project from the custom clean-architecture template. Runs the full 11-step setup:
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. |
| list_flutter_projectsB | List Flutter projects in a given directory (looks for pubspec.yaml). |
| get_project_infoB | Get details about an existing Flutter project (pubspec, flavors, config files, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-flutter-project | Scaffold a new Flutter project from the MT clean-architecture template |
| list-flutter-projects | List all Flutter projects in a directory |
| project-info | Get details about an existing Flutter project |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create a new project, list existing projects, and get project details. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case: create_flutter_project, list_flutter_projects, get_project_info. Predictable and clear.
Three tools is an appropriate scope for a server focused on Flutter project scaffolding and inspection. Each tool earns its place without unnecessary bloat.
The tools cover core creation and read operations (list, info). Missing update or delete tools, but this is reasonable for a scaffolding-focused server; the create tool handles extensive setup.