Astrophotography workspace

Publish the sky with the story behind the image.

Lumigraph brings session planning, gear profiles, source frames, drafts, and posts into one workspace — reachable from the web, a first-party CLI, and your AI assistant over MCP.

Read the docs

Plan tonight's sessionSync frames from the CLIDrive it with Claude

Published post

Emission nebula · 14.5h

Rosette Nebula (NGC 2244)

Telescope

RedCat 51

Camera

ASI2600MC

Integration

174 × 300s

Site Bortle

Class 4

Planner score92 · Excellent

3

ways in — web, CLI, MCP

FITS

headers peeked on scan

Resumable

dedupe-aware frame sync

OpenAPI

documented public API

Workflow

From camera card to published story.

Lumigraph follows the night the way you actually work it — plan, capture, sync, organize, publish — without scattering the work across folders and tools.

  1. 01

    Plan

    Pick a date and site, read the nightly score — weather, moon, darkness — and rank DSO targets worth the drive.

  2. 02

    Capture

    Shoot your lights, darks, flats, and bias. Your gear profiles keep the rig behind every night on record.

  3. 03

    Sync

    `lumigraph sync` uploads frames with frame-type filtering, path + size dedupe, and resumable batches.

  4. 04

    Organize

    Integration sets keep lights, calibration masters, and exports grouped by target instead of scattered on disk.

  5. 05

    Publish

    Turn the finished image into a structured post — target data, acquisition details, and the processing story.

Command line

A first-party CLI for the parts that live on disk.

The `lumigraph` command handles auth, filesystem inspection, and frame sync — built for terabytes of subs and camera cards.

Scan camera media

Detect mounted volumes, group by frame type, and peek FITS headers before anything uploads.

Sync, with resume

Path + size dedupe and a local manifest mean an interrupted upload picks up where it left off.

Mirror offline

`--to-local` mirrors a card to a local folder with zero auth — handy in the field.

zsh — lumigraph
$ lumigraph login # browser approval → tokens in your keychain
$ lumigraph scan /Volumes/NIKON_Z6 # summarize media + peek FITS
$ lumigraph sync --from ./M31 --to-cloud "Andromeda 2026-05-24"
            --include "*.fit,*.fits" --frame-type LIGHT
  ✓ 174 lights uploaded · 18 skipped (dupes) · resumable
$ lumigraph mcp:serve # expose the workspace to Claude Code
Model Context Protocol

Point your AI assistant at your library.

`lumigraph mcp:serve` runs a stdio MCP server that merges local tools (filesystem walks, FITS peeks, plan & execute sync) with the API's tools into one surface. Connect Claude Code or Cursor and let the agent scan a card, plan a sync, and organize integration sets — no shelling out required.

Set up MCPDestructive tools carry an MCP destructive hint for HITL confirmation.

Tools exposed to the agent

scanFolderplanSyncexecuteSynclistIntegrationSetscreateIntegrationSetlistVolumespeekFitsHeaderqueryDSOCatalogcreatePost
The workspace

Everything one image needs, in one place.

Plan, capture context, source data, and the published story stay connected instead of living in five different apps.

Session planner

Nightly score with weather, moon, and darkness, ranked DSO targets, and a calendar of saved sessions.

Gear library & rigs

Cameras, telescopes, mounts, filters, and reusable rig profiles that follow your sessions and images.

Integration sets

Lights, calibration masters, and exports grouped by target — the raw side of the work, kept private.

Drafts → posts

Iterate privately on a draft, then publish a structured record with the image, metadata, and the story.

Gallery

See what other astrophotographers are publishing.

Browse finished images with the full story attached — target, acquisition details, gear, and the processing notes behind them.

Start the log behind your next image.

Sign in to plan a session, sync your frames, and publish the story — all from one cosmic workspace.

View on GitHub