INDI MCP Server

An MCP server that controls astrophotography equipment via INDI on a Raspberry Pi (or equivalent device), and exposes it to other computers on the local network.

What it does

• Equipment control — connect to an INDI server and control mounts, cameras, filter wheels, focusers and other astrophotography gear through MCP tools.

• INDI server management — manage the INDI server itself: install/remove drivers, and start, stop or restart the server, all via MCP.

• Frame storage — captured frames are stored on the Raspberry Pi and can be listed, inspected and transferred to another computer on the local network via MCP.

Related MCP server: mcp-server-ascom

Status

Early setup stage — project scaffolding only, no functionality implemented yet.

Tech stack

• Python 3.12+, managed with uv

• Official Python MCP SDK (mcp)

• indipyclient — pure-Python INDI client, used for equipment control

• indiweb — used as a library only (its IndiServer/DriverCollection classes), for indiserver process/FIFO control and driver-catalog parsing; its bundled web app is not used

• Ruff for linting and formatting

• ty for static type checking

• pytest, with pytest-asyncio and pytest-cov

• pre-commit to run the above on every commit

Development setup

uv sync --dev
uv run pre-commit install

Common tasks:

uv run ruff check .          # lint
uv run ruff format .         # format
uv run ty check .            # type-check
uv run pytest --cov          # test

Contributing / branching model

This project follows a git-flow-style workflow:

• main — always releasable; only accepts merges from release/* or hotfix/* branches.

• develop — integration branch for ongoing work.

• feature/* — branched from and merged back into develop.

A CI check (enforce-merge-policy) rejects pull requests that don't follow these rules.