Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Check, add and control the smart home sensors and automations in your own Chirp home.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp-auth.chirpwireless.io/mcpRun this in your terminal
claude mcp add --transport http chirp https://mcp-auth.chirpwireless.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chirp": {
"url": "https://mcp-auth.chirpwireless.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"chirp": {
"type": "http",
"url": "https://mcp-auth.chirpwireless.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp-auth.chirpwireless.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain chirpwireless.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
The address needs your own account values, so we cannot check it for you
The address needs your own account values, so we cannot check it for you
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Intervals MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Remote MCP server for intervals.icu run data and analysis
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
https://mcp-auth.chirpwireless.io/mcp
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.
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.
| Area | What it can do |
|---|---|
| Sensors | List the sensors in your home, see their details and readings, add a new one — a LoRaWAN sensor or a tracker — from the available profiles |
| Control | Send a command to a device, and check that it went through |
| Connections | See how your home is connected, and set up a connection for a new sensor |
| Automations | Go through what you've built, and see what each one actually does |
| Alerts | Look at your alerts, summarize what has been triggering and how often, send a test notification to check it lands on your phone |
| Dashboards | List your dashboards and pull the data behind a widget, so it can chart or explain a reading |
| Household | Look up your home's details and members, invite someone, set what they can see |
Anything that changes something asks you first. Anything that only looks stays out of your way.
claude mcp add --transport http chirp https://mcp-auth.chirpwireless.io/mcp
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.
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.
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:
https://mcp-auth.chirpwireless.io/o/{organizationId}/mcp
The ID for a home is in the Chirp web app. You can only connect to a home you're a member of.
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.
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.
Two devices are free — start at chirpwireless.io.