Skip to main content
Glama
Oekalegon

INDI MCP Server

by Oekalegon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_indi_serverB

Start the INDI server (indiserver) on the given port.

Restarts it if it is already running.
stop_indi_serverA

Stop the running INDI server (indiserver).

restart_indi_serverA

Restart the INDI server (indiserver), optionally switching to a new port.

get_indi_server_statusA

Report whether the INDI server (indiserver) is running, and on which port.

list_indi_driver_catalogA

List every INDI driver installed on this device, whether or not it is running.

start_indi_driverB

Start the INDI driver identified by its catalog label (e.g. "CCD Simulator").

stop_indi_driverB

Stop the running INDI driver identified by its catalog label.

list_running_indi_driversA

List all currently running INDI drivers.

start_indi_messagingA

Connect to the INDI server and start streaming its property/message events.

stop_indi_messagingA

Disconnect from the INDI server and stop streaming its events.

get_indi_messaging_statusA

Report whether the INDI messaging stream is running, and its host/port.

list_indi_messagesC

List the most recently seen INDI events, newest first, optionally filtered to one device.

send_indi_propertyC

Send a command to an INDI device, setting elements on its property name.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation5/5

Every tool targets a distinct operation: server control, driver management, messaging, listing, and property sending. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, e.g., start_indi_server, list_indi_driver_catalog, send_indi_property.

Tool Count5/5

13 tools provide complete coverage for managing an INDI server and its drivers without being excessive; each tool serves a clear purpose.

Completeness4/5

Covers all major operations: server lifecycle, driver start/stop, messaging, and property setting. Minor gap: no dedicated tool to query a driver's current property state, though messages provide partial coverage.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive

Resources