TraceWeave vs Flutter Skill — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
TraceWeave vs Flutter Skill
In-depth architectural comparison of the TraceWeave and Flutter Skill MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
TraceWeave
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Flutter Skill
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose TraceWeave if you need specialized Developer Tools tools running via a local process. Choose Flutter Skill if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose TraceWeave when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Read-only summary of cached session data and suggested next calls; mirrors `parse_sim_log`'s `protocol_symptom_hint` so a scoreboard failure surfaces the protocol-health pointer at session start
get_sim_paths
Discover compile logs, sim logs, waveforms, simulator, and cases. Optional explicit `sim_log` / `wave_file` / `compile_log` overrides win over auto-discovery; omitted fields are still discovered (anchored at the `sim_log`/`wave_file` directory)
build_tb_hierarchy
Stream compile evidence and build the full testbench hierarchy server-side without retaining raw source bodies; return a slim payload (project, stats, depth-2 tree skeleton, interfaces, ambiguous_basenames, `build_metrics`, `hierarchy_handle`). For split VCS flows, pass ordered `supplementary_compi…
scan_structural_risks
Scan compiled RTL/TB sources for structural risk patterns in a lock-free cancellable worker; returns `eligible_file_count`, `files_scanned`, `coverage_status`, and `coverage_warnings` so zero or partial source coverage cannot be mistaken for a clean scan
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
TraceWeave is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Flutter Skill belongs to Developer Tools using local stdio subprocess. Select TraceWeave when you need capabilities focused on developer tools and Flutter Skill when you require tools for developer tools.
Parse and normalize runtime failures into grouped summaries and `failure_events`; also returns `log_snapshot_id` so same-path reruns can be compared after the simulator overwrites the log. Its `candidate_previous_logs` are evidence-backed simulation siblings selected from bounded head/tail samples;…
diff_sim_failure_results
Compare two simulation runs by paths or by `base_snapshot_id` / `new_snapshot_id`. If only `new_log_path` is supplied after an earlier `parse_sim_log` of the same path, TraceWeave uses the previous parsed snapshot as the baseline.
get_error_context
Extract raw log context around a specific line
search_signals
Resolve full hierarchical signal paths. `keyword` accepts a single string or a **list of keywords** (max 16) — pass a list to batch several lookups in one call (one result entry per keyword, in input order) instead of issuing consecutive single-keyword searches. Each result also carries `direction`…
get_signal_at_time
Query a signal value at a specific timestamp
get_signal_transitions
Retrieve transitions for a signal over the strict closed interval `[start_time_ps, end_time_ps]`; FSDB and VCD never mix an earlier timestamp into `transitions`. The last value-change strictly before the window is exposed separately as `predecessor`, which clocked samplers use to classify a transit…
get_signals_around_time
Retrieve context around a failure timestamp. `transitions_in_window` is a strict closed-window list; `pre_window_transitions` contains only earlier value changes, capped by `extra_transitions` and ordered chronologically on both FSDB and VCD. Flags a `value_at_center` that is a **sub-cycle transien…
get_signals_by_cycle
Sample signals cycle-by-cycle on a clock edge
+9 more tools listed on main page
Flutter Skill Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.