Nest Protect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEST_CLIENT_ID | Yes | Your Google OAuth Client ID | |
| NEST_PROJECT_ID | Yes | Your Google Cloud Project ID | |
| NEST_CLIENT_SECRET | Yes | Your Google OAuth Client Secret | |
| NEST_REFRESH_TOKEN | Yes | Your OAuth refresh 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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_nest_devicesA | Discover Nest Protect Devices. List all detectors, room locations, and online status with rich UI cards for home safety overview. |
| get_device_healthC | Get Device Health Status. Real-time battery, smoke, CO, and connectivity metrics with visual health indicators in chat. |
| get_nest_eventsB | Get Recent Device Events. Retrieve a list of recent smoke, CO, or connectivity events for a specific device. |
| hush_active_alarmA | Silence Active Alarm Device. Temporarily hush smoke or CO alarms for maintenance or false triggers (30-300 seconds). |
| run_safety_testC | Execute Device Safety Test. Trigger full, smoke, or CO self-tests on the device to verify alarm functionality. |
| set_device_ledA | Set Device LED Brightness. Adjust the brightness level (0-100) of the Nest Protect status light ring. |
| trigger_test_alarmA | |
| set_security_modeA | Set Guard Security Mode. Arm (home/away) or disarm the Nest security system using an optional passcode. |
| get_server_statusA | Get Server System Status. Retrieve host CPU, memory, and disk usage metrics for the MCP server process. |
| get_mcp_processA | Get MCP Process Metrics. Retrieve detailed memory and CPU consumption for the specific Nest Protect MCP process. |
| check_api_connectivityB | Check API Connection Health. Verify real-time connectivity and latency to the Google Smart Device Management API. |
| list_server_toolsB | List Available MCP Tools. Retrieve a comprehensive list of all registered tools and their functional descriptions. |
| get_tool_detailsA | Get Tool Practical Help. Retrieve detailed parameters, usage examples, and safety constraints for a specific tool. |
| search_mcp_toolsA | Search Tools by Keyword. Discovery helper to find relevant tools based on name, description, or capability keywords. |
| start_google_oauthB | Initiate Google OAuth Flow. Start the secure OAuth 2.0 authorization process to link your Nest account. |
| finish_google_oauthB | Complete Google OAuth Callback. Process the authorization code and exchange it for persistent access and refresh tokens. |
| refresh_nest_tokenC | Refresh Nest Access Token. Force or verify the renewal of the current OAuth 2.0 access token for API calls. |
| get_nest_auth_statusA | Get Nest Auth Configuration Status. Summarize whether NEST_* credentials and tokens are loaded (masked); reads repo |
| get_oauth_redirect_referenceA | Get OAuth Redirect URI Reference. Return example redirect URIs (CLI vs web wizard), doc links, and |
| get_pcm_authorize_urlB | Get PCM Authorize URL. Build the Partner Connections Manager authorization URL (same as start_google_oauth); optional browser. |
| validate_nest_credentialsA | Validate Nest SDM Credentials. Optionally refresh the access token, then call SDM |
| get_mcp_configA | Get Current Server Configuration. Retrieve the active configuration values for API endpoints, timeouts, and device filters. |
| update_mcp_configA | Update Server Configuration Values. Modify active settings and optionally persist them to the config.toml file. |
| reset_mcp_configA | Reset Configuration to Defaults. Revert all server settings to their original factory values (requires confirmation). |
| export_config_fileC | Export Config To File. Save the current active configuration to a local file in TOML or JSON format. |
| import_config_fileA | Import Config From File. Load configuration settings from a local file and merge them into the server state. |
| analyze_home_safetyD | Assess Home Safety AI. Perform comprehensive safety evaluation using advanced AI orchestration and sampling patterns. |
| coordinate_emergency_aiC | Coordinate Emergency AI Response. Execute intelligent coordination during safety incidents using sampling for complex decisions. |
| forecast_maintenance_needsB | Forecast Device Maintenance Needs. Predict future battery replacements and sensor failures using environmental AI analysis. |
| configure_smart_automationC | Configure Smart Safety Automation. Set up adaptive automation rules that learn your lifestyle patterns for proactive safety. |
| get_server_infoB | Get Server Information. Retrieve version, capabilities, and operational documentation for this Nest Protect MCP instance. |
| list_supported_hardwareB | List Supported Nest Hardware. Retrieve detailed technical specifications for supported Nest Protect generations and models. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| nest_protect_setup | Guide to set up Nest Protect MCP auth (Google OAuth, refresh token). |
| nest_protect_safety_check | How to run a safety test on a Nest Protect device. |
| nest_protect_overview | Overview of Nest Protect MCP tools and capabilities. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 32 tools
Several tools have overlapping purposes, particularly the AI-related tools (analyze_home_safety, coordinate_emergency_ai, forecast_maintenance_needs, configure_smart_automation) which are vaguely described and difficult to distinguish. Additionally, there are multiple OAuth and configuration tools that, while distinct, could confuse agents due to their number.
All 32 tools follow a consistent verb_noun pattern in snake_case (e.g., list_nest_devices, get_device_health, hush_active_alarm). The naming is predictable and clear across the entire set.
With 32 tools, the server has far more than is typical for a focused home safety domain. Many tools are meta or overlap, suggesting scope creep. This exceeds the recommended range and may overwhelm agents.
The server covers device management, OAuth, configuration, and system info reasonably well, but includes vague AI features that are not clearly integrated. Missing essential operations like firmware update or device removal, and includes an out-of-scope security mode tool.