inception-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INCEPTION_URL | Yes | The controller URL (either local http://192.168.1.50 or through your SkyTunnel serial https://skytunnel.com.au/Inception/IN12345678). | |
| INCEPTION_API_TOKEN | Yes | The Inception User API Token. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inception_get_system_infoA | Returns the Inception controller's name, serial number and REST API protocol version, and whether the firmware is supported (7.3.0.8528 or later, protocol version 18). Use it to confirm connectivity. |
| inception_list_itemsA | Lists areas, doors, inputs or outputs the API user can see, each with its current state decoded into names. Area states include Armed, Disarmed, Alarm, EntryDelay, ExitDelay, ArmReady, AwayArm (Full), StayArm (Perimeter), SleepArm (Night). Door states include Locked, Unlocked, Open, Closed, Forced, HeldOpenTooLong, LockedOut. Input states include Active (unsealed/open), Sealed, Tamper, Isolated. Output states are On/Off. Use has_state to filter, e.g. type=input with has_state=["Active"] lists open zones. |
| inception_get_eventsA | Queries the controller's review (event) log. Returns most recent first by default. Each event has a numeric messageId, its category (System, Audit, Access, Security, Hardware, Integration), an event type name and the panel's description, plus who/what/where. Filter by time range, category, message IDs (use inception_list_event_types to find IDs, e.g. area armed/disarmed) or involved item IDs. For paging use offset, or reference_id + reference_time from an earlier event instead of start/end. |
| inception_list_event_typesA | Searches the catalogue of review event types (from the Inception API docs) so you can find numeric IDs to pass as message_ids to inception_get_events. Example: query='armed' or 'disarm', category='Security'. Works offline; does not contact the panel. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct purpose: connection/system metadata, listing configured items, browsing the offline event-type catalogue, and querying the event log. The only superficially similar pair (list_event_types vs get_events) is explicitly disambiguated in the descriptions as catalogue lookup versus actual log query.
All four tools use a uniform prefix + verb_noun pattern (inception_get_system_info, inception_list_items, inception_list_event_types, inception_get_events). No casing or verb-style deviations.
Four tools is lean but defensible for a read/inspection-focused integration, and each tool earns its place. It is slightly under-scoped rather than bloated.
Coverage is read-only: connectivity, item listing, event-type lookup, and event retrieval are all present, but there is no way to act on the panel (arm/disarm areas, control doors or outputs) and no per-item detail fetch. For a security panel integration, the absence of any control operation is a notable gap.