Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
The Wyze Blog
Overview
Description from the maker (original English)
The Wyze blog: guaranteed rent, temporary accommodation and lettings guides for UK letting agents.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiEarly★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- Can do 2 things (tools) list_blog_posts, get_blog_post
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
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:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://thewyze.com/api/mcpRun this in your terminal
claude mcp add --transport http blog https://thewyze.com/api/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"blog": {
"url": "https://thewyze.com/api/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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"blog": {
"type": "http",
"url": "https://thewyze.com/api/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:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://thewyze.com/api/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.
What it can do
Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.
list_blog_postsLists The Wyze blog posts, newest first, with title, date, author, excerpt and URL. Optionally filter by a search term. Use get_blog_post with a slug for the full article.
get_blog_postReturns one The Wyze blog post in full (plain text) by its slug.
Basic checksi
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 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain thewyze.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 300 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 2 tool descriptions and found no hidden instructions to the AI
Compared with others in Otheri
- More stars than 0% of the other 18513 servers in this category
- Published to the registry more recently than 96% of the other 18513 servers in this category
- Basic checks equal to or better than 100% of the other 18513 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is The Wyze Blog safe?
It passed 3 of 3 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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 days ago.
Which apps can use it?
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.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Cape Winelands Visit Planner
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud✓ desktopcommander.app
Cape Winelands Visit Planner
Cape Winelands wine farm finder and day-route planner
Runs in the cloud✓ aiagenttools.co.za
README from the maker
Open the README
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.
What is this?
The Wyze is property management software for UK landlords and letting agents, and its blog covers guaranteed rent, temporary accommodation and running a lettings business.
This MCP server lets AI assistants like Claude, ChatGPT and Gemini search and read that blog directly, so answers come from the actual articles, with links, rather than from guesswork.
It's hosted, so there's nothing to install or run.
How it works
You ask your assistant a question. It calls one of the two blog tools over the open Model Context Protocol and answers from what comes back, linking each post it used. Your chat never goes to The Wyze, only the tool call does: the same request the website makes.
Getting started
Add this URL to your AI assistant:
https://thewyze.com/api/mcpThat's it. No account, no API key.
Claude (web, desktop and mobile)
- Open Settings → Connectors and choose Add custom connector.
- Name it The Wyze Blog and paste the URL above. Leave the OAuth fields empty: no login is needed.
- In a new chat, open the tools menu, turn The Wyze Blog on, and ask your question.
Claude Code
claude mcp add --transport http thewyze https://thewyze.com/api/mcpCursor
One click: it opens Cursor and adds a server named thewyze with the URL above. Or paste the config below.
Gemini CLI
gemini extensions install https://github.com/The-Wyze/MCPChatGPT
- Open Settings → Apps & Connectors. Custom servers sit under Advanced settings (developer mode).
- Create a connector named The Wyze Blog, paste the URL above, and choose No authentication.
- Add it to a chat from the + menu and ask your question.
VS Code and GitHub Copilot, Windsurf, config files, and everything else
VS Code / GitHub Copilot: add .vscode/mcp.json to your project (or run *MCP: Add Server*), start the server from the file, then pick it in Copilot Chat's tools list in agent mode:
{"servers": { "thewyze": { "type": "http", "url": "https://thewyze.com/api/mcp" } } }
Cursor by hand (~/.cursor/mcp.json):
{"mcpServers": { "thewyze": { "url": "https://thewyze.com/api/mcp" } } }
Windsurf (~/.codeium/windsurf/mcp_config.json):
{"mcpServers": { "thewyze": { "serverUrl": "https://thewyze.com/api/mcp" } } }
Gemini CLI by hand (~/.gemini/settings.json, then restart; /mcp lists the tools):
{"mcpServers": { "thewyze": { "httpUrl": "https://thewyze.com/api/mcp" } } }
Anything else that speaks MCP: streamable HTTP at the URL above (POST, one JSON-RPC message per request, JSON responses, no sessions). A plain GET on the same URL describes the server; the registry card is at /.well-known/mcp/server.json, with a copy in server.json.
Check it's working
Ask: *"What are the latest posts on The Wyze blog?"*
Your assistant should call list_blog_posts and answer with titles, dates and links. If it answers from memory instead, the server isn't switched on in that chat yet (see Troubleshooting).
What an answer looks like
Every answer can link the post it came from, so you can read the original yourself.
Things you can ask
- *"What has The Wyze written about guaranteed rent schemes?"*
- *"Summarise The Wyze's latest article and give me the link."*
- *"Find posts on temporary accommodation for councils."*
- *"What does The Wyze blog say about property management software for letting agents?"*
- *"List everything published this year, oldest last."*
The tools
There are two, and they only read:
| Tool | Arguments | What it returns |
|---|---|---|
list_blog_posts | search (optional), limit 1–20 (default 10), cursor (optional) | Posts newest first: slug, title, date, author, excerpt, URL and featured image, plus nextCursor for the next page |
get_blog_post | slug (required; a /blog/ URL works too) | One post in full as plain text, with its modified date, author, reading time, description and FAQs |
Both carry readOnlyHint and return structured JSON alongside the text.
What it can and can't see
- It only sees blog posts already published on thewyze.com/blog. No accounts, tenants, landlords, properties or personal data, ever.
- Help-centre, what's-new and glossary posts aren't served, exactly as the website's
/blogpages don't show them. - It can't create, change or send anything.
- Results are cached for five minutes, so a new post shows up shortly after it's published.
Troubleshooting
| What you see | What it means |
|---|---|
| The assistant answers without using the blog | The server isn't switched on in that chat. In Claude, open the tools menu and turn it on; in Cursor and Gemini CLI, restart after adding it. |
No blog post with that slug. | The slug is wrong, or the post isn't a blog post. Ask the assistant to search with list_blog_posts first. |
The blog is temporarily unavailable | The blog's backend didn't answer. Try again in a minute. |
405 / *This server offers no SSE stream* | The client opened an old-style SSE connection. Choose *HTTP* or *streamable HTTP* when adding the server. |
404 Not Found | The address must be exactly https://thewyze.com/api/mcp. Agency portal domains don't serve it. |
Found a problem?
If it's a security issue, please email info@thewyze.com rather than opening a public issue: see SECURITY.md. For anything else, issues are very welcome.
Source code
The code behind the public server is in src/, so you can see exactly what each tool does and returns. It runs inside The Wyze's Next.js app and uses the app's WordPress helpers, so it won't run on its own from this repo; it's here to be read and checked.
| Where | What |
|---|---|
src/app/api/mcp/route.ts | The endpoint: JSON-RPC handling, the two tools and what they return |
src/lib/mcp/serverInfo.ts | The server's name, version and registry card |
src/app/.well-known/mcp/server.json/route.ts | Serves the registry card |
The diagrams in this README are SVG files in assets/, drawn by scripts/make-docs-images.py so they can be redrawn when the tools change. The assistant marks are their owners', used only to name the products that connect.
Releasing a new version, and how it reaches the MCP Registry, is in RELEASING.md.
Licence
The files in this repo are MIT. The blog content the server returns isn't: it's The Wyze's, and the name and logo are ours, so please don't use them as your own.
Made in the UK by The Wyze · Wise Systems Limited · Changelog