Headers Reference
6 min
headers reference the litmus mcp server is stateless every tool call reads its credentials from the request headers (sse mode) or environment variables (stdio mode) this page documents every header the server understands litmus edge (rest / sdk) required for almost every tool except a few system only ones header required description edge url yes litmus edge base url include https // edge api client id yes oauth2 client id issued by litmus edge edge api client secret yes oauth2 client secret generate the client credentials under litmus edge > system > access control nats (live values) used by get current value from topic and get multiple values from topic header required default description nats source yes litmus edge ip, no scheme prefix nats port no 4222 nats broker port nats user yes access token username from system > access control > tokens nats password yes access token value nats tls no true set to false to disable tls influxdb (time series) used by every marked influxdb tool ( get historical data from influxdb , list influxdb measurements , get device historical data , query tag data , get tag statistics , get device data for inference , get device connection status ) header required default description influx host yes litmus edge ip, no scheme prefix influx port no 8086 influxdb port influx db name no tsdata database name influx username yes datahub user influx password yes datahub password allow port 8086/tcp in litmus edge > system > network > firewall litmus edge manager (lem) used by every lem tool lem tools talk to a cloud edge manager tenant rather than an edge header required default description edge manager url yes lem base url include https // edge api token yes api token issued by lem edge manager project id no default project id, used when a tool's project id argument is omitted edge manager admin url no \<edge manager url host> 8446 admin url validate certificate no false true to verify tls certs on the lem bridge the lem bridge tools additionally tunnel through lem to a specific edge and require both project id and device id as call arguments they do not switch the active edge instance stdio mode when the server runs in stdio mode ( enable stdio=true ), the same names are read from the process environment instead of http headers pass them through your mcp client's env block see claude desktop (stdio) # header configuration guide edge url include https // edge api client id / edge api client secret oauth2 credentials from litmus edge nats source ip only, no http / https nats user / nats password token credentials from system > access control > tokens influx host ip only, no http / https influx username / influx password datahub user credentials