satellite_alt FlutterSDK Telescope

Stop pasting stack traces into Claude. Let your agent read them itself.

Name: Telescope
Author: FlutterSDK

9 MCP tools give Claude Code direct access to HTTP traffic, exceptions, logs, debugPrint dumps, DB queries, and cache hits (over VM Service extensions, with zero release overhead).

Read the docs View on pub.dev

terminal

flutter pub add fluttersdk_telescope
dart run fluttersdk_telescope telescope:install

Powered by our Sponsors

Helping us build the future of Flutter development.

Become a Sponsor arrow_forward

Why Telescope?

The agent loop, closed.

Every time your agent debugs a Flutter app, it asks you to paste something. Stack trace. HTTP response. Log line. Telescope reads them directly, so the agent closes the fix loop without you in the middle.

content_paste_off

The paste-loop

Claude asks: "Can you paste the stack trace?" You copy. You paste. You repeat. Multiply by 50 debug iterations per feature.

hub

The agent reads directly

Telescope ring-buffers HTTP, logs, exceptions, queries, cache hits at the framework layer. 9 MCP tools expose them. Claude calls telescope_exceptions, reads the last 500 stack traces, suggests the fix. No copy-paste.

check_circle

Closes the fix loop

One MCP roundtrip replaces a five-step copy ritual. The agent debugs unsupervised, you review the diff. Closes the fix loop.

What Telescope ships

Every layer, queryable.

9 watchers ring-buffer the data. 9 MCP tools surface it. 6 CLI commands stream it. 11 VM Service extensions wire it. Zero release overhead.

cable

HTTP capture

Every request and response, ring-buffered for instant query via telescope_requests.

error_outline

Exception watcher

Stack traces captured at the framework layer. Queryable by your agent through telescope_exceptions.

description

Log + debugPrint

Structured log records plus raw debugPrint dumps surfaced via telescope_dumps. Agent-readable runtime, end to end.

storage

DB query trace

Magic-aware query records: SQL string, bound params, duration. telescope_queries returns the last N.

bolt

Cache hits

Cache get/put/forget records via telescope_caches. See exactly what your app stored and when.

auto_fix_high

Magic event lifecycle

Model + event + gate + cache watchers from the Magic SDK wire into telescope automatically.

hub

9 MCP tools

Flutter-native MCP server: telescope_requests, telescope_tail, telescope_exceptions, telescope_events, telescope_gates, telescope_dumps, telescope_queries, telescope_caches, telescope_clear.

terminal

6 CLI commands

telescope:install bootstraps. telescope:tail streams live. telescope:requests / telescope:queries / telescope:caches snapshot. telescope:clear resets.

compress

Debug-only tree-shake

kDebugMode gates the entire subsystem. dart2js and dart2native AOT tree-shake the imports to zero in release builds.

Stream it

telescope:tail in your terminal.

Every record type, color-coded, live-streamed. The agent reads the same buffer over MCP.

./bin/fsa telescope:tail

$ ./bin/fsa telescope:tail
[HTTP] GET /api/users → 200 in 87ms
[LOG ] User session refreshed
[EXC ] FormatException at lib/auth.dart:42
[HTTP] POST /api/login → 200 in 142ms
[QRY ] SELECT * FROM users WHERE id = 1 (3.2ms)
[CACH] set: session.user:42 (ttl: 3600s)
[LOG ] Route guard: /dashboard allowed
[HTTP] GET /api/profile → 304 in 12ms

Live tail, parsed buffers, MCP exposure

Every HTTP request, log line, exception, query, and cache hit lands in a typed ring buffer the moment it happens.

telescope:tail prints them as they arrive. Color-coded by record type. Tailable, greppable, scriptable.

What your agent sees when it reads your app is the same buffer: 9 MCP tools expose it as structured JSON.

Read the CLI docs arrow_forward

MCP layer

9 tools your agent calls.

Every MCP tool exposes a typed buffer. Claude Code calls them directly, reads structured JSON, decides the next debug step.

telescope_requests arrow_forward

Returns the last N HTTP records (URL, status, timing, headers).

telescope_tail arrow_forward

Streams new HTTP + log + exception records as they happen.

telescope_exceptions arrow_forward

Returns the last N captured exceptions with stack traces.

telescope_events arrow_forward

Returns Magic event records (event name, payload, listener count).

telescope_gates arrow_forward

Returns gate decision records (gate name, result, user context).

telescope_dumps arrow_forward

Returns debugPrint and explicit dump() records.

telescope_queries arrow_forward

Returns DB query records (SQL, bindings, duration).

telescope_caches arrow_forward

Returns cache get/put/forget records (key, hit/miss, ttl).

telescope_clear arrow_forward

Wipes all ring buffers (debug session reset).

What your agent sees when it reads your app

11 VM Service extensions wire 9 watchers into 9 MCP tools. One unified Flutter-native MCP server. Your agent gets the runtime, end to end.

Read MCP docs

Magic SDK companion

One call, full coverage.

If you're on the Magic SDK, telescope wires itself into every watcher in one line.

welcome.dart

import 'package:fluttersdk_magic/fluttersdk_magic.dart';
import 'package:fluttersdk_telescope/fluttersdk_telescope.dart';

void main() {
    if (kDebugMode) {
        MagicTelescopeIntegration.install();
    }
    runApp(const MyApp());
}

cable

HTTP adapter

Every Dio + http request wrapped, ring-buffered.

dataset

Model watcher

Magic Model save / update / delete events surfaced.

bolt

Cache + gate watchers

Cache hits + gate decisions captured.

event

Event lifecycle

Every Magic event dispatch + listener execution traced.

Wire it up

In context

Where telescope fits.

Three alternatives the team probably considered. Telescope picks the runtime + agent surface no one else does.

Sentry

Crash reporting

check_circle Exception capture (both have it)
cancel Release-only (Sentry skips dev)
cancel SaaS roundtrip required
cancel No MCP / agent surface

Flutter DevTools

Project tooling

check_circle Profile, inspect widgets, debug
cancel UI-driven (no agent surface, no CLI tail)
cancel No ring buffer (point-in-time only)
cancel dart mcp-server scaffolds projects (not runtime telemetry)

print() + debugPrint

The default

check_circle Zero setup
cancel Unstructured (one log stream, no record types)
cancel No query surface (agent paste-loop)
cancel No release tree-shake guarantee

Telescope picks runtime + structured + agent

Debug-only, ring-buffered, color-coded, CLI-streamable, MCP-callable. The first Flutter MCP server for runtime observability, not UI automation.

history_edu

Inspired by Laravel Telescope.

Laravel Telescope for Flutter. Your AI agent can read it too. Same model: HTTP watcher, log watcher, exception watcher, query watcher. Surfaced to CLI and to Laravel Telescope's spiritual successor on the Flutter side (over MCP instead of a browser dashboard). Agent-readable runtime, end to end.

Start reading your runtime.

terminal

flutter pub add fluttersdk_telescope
dart run fluttersdk_telescope telescope:install

fluttersdk/telescope | pub.dev/packages/fluttersdk_telescope | menu_book Documentation