Chirp Home Automation
io.chirpwirelessPublished by chirpwireless.ioOfficial publisherv1.0.0Updated Oct 24, 2026
Check, add and control the smart home sensors and automations in your own Chirp home.
Overview
Hosted Chirp MCP server that lets an assistant inspect and control the sensors, automations, alerts and dashboards in your own Chirp smart home.
- What you can do
- List sensors, view their details and readings, and add a new LoRaWAN sensor or tracker from available profiles
- Send a command to a device and check whether it went through
- Review how the home is connected and set up a connection for a new sensor
- Go through existing automations and see what each one does
- Review alerts, summarize what has been triggering and how often, and send a test notification
- List dashboards, pull the data behind a widget, and look up household details and members, including inviting people and setting what they can see
- When to use it
- Useful when you already run a Chirp smart home and want to ask an AI app about sensor readings, quiet sensors or past alerts, or have it act on a device, without writing scripts. It fits ad-hoc questions and quick actions rather than scheduled exports, which the separate REST API covers.
- Requirements
- A remote Streamable HTTP endpoint hosted by Chirp; nothing to install and no API key. You need a Chirp account and sign in through the browser with OAuth, and you can only connect to a home you are a member of. Multi-home users can pin a specific home by organization ID in the endpoint path.
Installation
In SourceWeft
- Open Chirp Home Automation in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.chirpwireless%2Fchirp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"chirp-home-automation": {
"type": "http",
"url": "https://mcp-auth.chirpwireless.io/mcp"
}
}
}README
Chirp Home Automation MCP Server
Point the AI app you already talk to at your own home. Ask which sensors have gone quiet, what set off last night's alert, how cold the garage got — and tell it to do something about it.
The server is hosted by Chirp. Nothing to install, no key to generate or paste: you sign in with your usual Chirp account in the browser, once.
This repository holds the public metadata for that server — its registry manifest, its icon, and the setup steps below. The service itself is closed-source.
What is MCP?
MCP is a shared way for an AI app to reach out and use something else safely. Chirp speaks it, so the app you already use can talk to your home with no custom plumbing — Claude Code, Claude Desktop, ChatGPT, Codex, Cursor and more.
What can your AI app do with your home?
Anything that changes something asks you first. Anything that only looks stays out of your way.
Connecting Claude Code
Run /mcp inside Claude Code, pick chirp, and sign in when the browser opens. Run /mcp again and
it shows as connected — then ask it which of your sensors went quiet this week.
Connecting Claude Desktop, ChatGPT, Cursor or Codex
If your app has a Connectors, Integrations or MCP servers screen, choose whatever it calls
"add a custom server", paste https://mcp-auth.chirpwireless.io/mcp, and sign in when the browser
opens.
If it is configured from a file or a terminal instead, add the same address as a Streamable HTTP server. Your app's own documentation will say where that setting lives.
Which home does it see?
If you only have one home, skip this — it just works.
The plain address follows whichever home is selected in the Chirp app. If you look after a holiday flat as well as your own place and want each AI client fixed to one, pin it:
The ID for a home is in the Chirp web app. You can only connect to a home you're a member of.
What it can and can't see
Your AI app sees exactly what you see. If something is hidden from you, it's hidden from your assistant. There's no key to lose, because there is no key — the connection is your own browser sign-in, and you can end it whenever you like.
API vs MCP
The REST API is for code you write — a script that exports readings into a spreadsheet every Sunday, or a bridge to another home platform. It runs on a key you create, with the scopes you choose. MCP is for asking questions and getting things done in the moment, as yourself.
Links
- Chirp: chirpwireless.io
- Documentation: docs.chirpwireless.io — MCP Server
- Contact: chirpwireless.io/contact
- Privacy policy: chirpwireless.io/privacy-policy · Terms: chirpwireless.io/terms-of-service
Two devices are free — start at chirpwireless.io.
Source: README.md at commit 51187b1
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts