Skip to main content
Glama
thinq-connect

ThinQ Connect MCP Server

Official
by thinq-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
THINQ_PATYesYour personal access token for ThinQ Open API calls
THINQ_COUNTRYYesYour ThinQ account's country code

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
get_device_listA

Retrieves a list of all devices connected to the ThinQ Connect platform Args: None

Returns:
    String containing connected device list information
get_device_available_controlsA

Retrieves available control commands and parameter information for a specific device Args: device_type: Device type (e.g., DEVICE_AIR_CONDITIONER, DEVICE_ROBOT_CLEANER, DEVICE_STYLER) device_id: Unique ID of the device to query

Returns:
    String containing device control commands and parameter information
get_device_statusB

Retrieves status information for a specific device Args: device_id: Unique ID of the device to query

Returns:
    String containing device status information
post_device_controlC

Send control commands to a specific device on the ThinQ Connect platform to change its settings or state Args: device_type: Device type (e.g., DEVICE_AIR_CONDITIONER, DEVICE_ROBOT_CLEANER, DEVICE_STYLER) device_id: Unique ID of the device to control control_method: Co ntrol method name to execute (e.g., set_air_con_operation_mode, set_target_temperature, set_wind_strength) control_params: Parameter dictionary to pass to the control method (e.g., {'operation': 'POWER_OFF'}, {'temperature': 25}, {'wind_strength': 'HIGH'})

Returns:
    String containing device control result message

Prompts

Interactive templates invoked by user choice

NameDescription
I want to know how to use the ThinQ Connect MCP Server

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.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct purpose: listing devices, getting status, querying available controls, and sending control commands. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_device_*, post_device_*), with clear and predictable naming.

Tool Count4/5

With 4 tools, the set covers essential operations for device management without being overly minimal or excessive. It's slightly on the lower end but well-scoped.

Completeness4/5

The set covers device listing, status retrieval, available controls, and control execution. Minor gaps like device registration or batch control are absent but acceptable for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources