SMAHO MCP server

The SMAHO MCP server connects AI assistants and other Model Context Protocol (MCP) clients to your SMAHO account, with the same Locations, Rooms, Controls, Devices, and Automations that you know from the SMAHO app.

Server details

• Endpoint: https://mcp.smaho.io/mcp
• Transport: Streamable HTTP, MCP protocol version 2026-07-28. The server refuses earlier protocol versions.
• Authorization: OAuth authorization code flow against the authorization server https://auth.smaho.io. Use PKCE with S256. Send the access token in the Authorization: Bearer header.
• Protected resource metadata: https://mcp.smaho.io/.well-known/oauth-protected-resource/mcp. A request without a token gets 401 with a WWW-Authenticate header that points there.

Connect a client

OAuth clients are registered in advance. The server doesn't support dynamic client registration. Registered clients:

• Claude: find SMAHO in Claude's Connectors Directory.
• ChatGPT: find SMAHO in ChatGPT's plugin directory.

To use another MCP client, write to engineering@smaho.com.

When you connect, sign in the way you do in the SMAHO app, review the permissions, and select Allow Access.

Permissions

The client sees only the tools that your granted scopes allow.

What you can do

• See your Locations and Rooms, and the current state of your Controls and Devices.
• Switch Devices on and off, dim lights, change colors, and set the temperature.
• List, run, enable, and disable your Automations.
• Create, edit, and delete Automations, including their triggers, conditions, and actions.
• Create, rename, or move a Control, and change which Devices it operates.
• Ask how SMAHO works. The server includes the SMAHO reference documentation.

Confirmations

Commands act on real hardware. Every tool that changes something carries destructiveHint: true, so a client that honors tool annotations can ask for your approval before it runs the tool.

Some tools also take a confirm argument. The server refuses them unless confirm is true, and the client should set it only after you confirm in the conversation:

• Deleting an Automation, or one of its triggers or actions.
• Replacing an Automation's conditions.
• Operating a Device that needs confirmation, such as a lock, a garage door opener, or a security system. This includes running an Automation, or adding or changing an Automation action, that operates such a Device.

Without devices:read, the server can't check the Device, so running an Automation, or adding or changing an Automation action, always needs confirm.

Enabling an Automation, or adding or changing its triggers, doesn't need confirm, even when the Automation operates such a Device.

Limits

• The server can't add or remove Devices or Connectors, create or delete Locations or Rooms, delete Controls, or change your account settings. Use the SMAHO app for those.
• The server reaches only the Locations that your SMAHO account has access to.

Troubleshooting

• Sign-in fails with invalid_client. Your client isn't registered, or its client credentials are wrong. Write to engineering@smaho.com.
• Requests fail with 401. The token is missing, has expired, or isn't valid for this server. Disconnect, connect again, and sign in.
• A tool is missing. The token doesn't grant that tool's scope. Make sure the client requests every scope listed in the protected resource metadata, and then connect again.
• A Device doesn't react. Check in the SMAHO app that the Device is online and responds there.
• An Automation doesn't run. Check that the Automation is enabled.
• A tool returns an error from SMAHO. The message names what SMAHO couldn't do and, in most cases, why.

Support

For help, to report a problem, or to request access for another MCP client, write to engineering@smaho.com.