flutter_mcp_toolkit_capability_core

Core MCP capability (fmt) for Flutter MCP Toolkit: VM inspection, UI interaction, navigation, logs, diagnostics, and hot-reload coordination.

Server-side Dart only — no Flutter SDK dependency.

Install

dependencies:
  flutter_mcp_toolkit_capability_core: ^0.1.0
  flutter_mcp_toolkit_capability_kernel: ^0.1.0
  flutter_mcp_toolkit_core: ^0.1.0

Usage

import 'package:flutter_mcp_toolkit_capability_core/flutter_mcp_toolkit_capability_core.dart';

final capability = FmtCapability(/* host services */);

Adding tools with @AgentTool (Phase 6c pilot)

Optional codegen via intentcall_codegen + build_runner. Hand-written ToolRegistration remains first-class.

1. Add deps (intentcall_codegen, intentcall_core, intentcall_mcp) and build_runner dev_dep (see pubspec.yaml).
2. Annotate a top-level function returning Future<AgentResult>:

part 'my_tool.g.dart';

@AgentTool(namespace: 'fmt', name: 'my_tool', description: '...')
Future<AgentResult> fmtMyTool(@AgentParam('...') String arg) async { ... }

3. Run dart run build_runner build in this package.
4. Register through the host path:

context.registerTool(
  agentCallEntryToToolRegistration(
    myToolCallEntry,
    mergeInputSchema: (schema) => { /* e.g. connection override */ ...schema },
    handler: (args) => runCommand(runner, args, MyCommand(...)),
  ),
);

Pilot: lib/src/tools/codegen/get_recent_logs_tool.dart → get_recent_logs. Generated .g.dart uses getRecentLogsInputSchema; registerLogTools still merges the same schema at host registration for regen safety.

Additional fmt_* tools via @AgentTool are pilot-only until a second tool passes low blast-radius review; prefer hand-written ToolRegistration for new server tools. Operator migration uses hand-written fmt_migrate_agent_entries.

Monorepo development

pubspec_overrides.yaml resolves sibling packages from local paths (not published).

Pub.dev publishing checklist

License

MIT — see LICENSE.