The Wyze Blog

com.thewyzePublished by thewyze.comOfficial publisherv1.0.0Updated Nov 7, 2026

The Wyze blog: guaranteed rent, temporary accommodation and lettings guides for UK letting agents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Read-only access to The Wyze blog on guaranteed rent, temporary accommodation and UK lettings, letting an assistant search posts and read full articles with…

What you can do
  • List blog posts newest first with title, date, author, excerpt and URL, optionally filtered by a search term
  • Read a single post in full as plain text by its slug or blog URL
  • Page through results with a cursor and limit of 1 to 20 posts
When to use it
Useful when you want answers about guaranteed rent schemes, temporary accommodation or running a lettings business grounded in The Wyze's published articles, with links to the originals, instead of the assistant's memory.
Requirements
A remote streamable HTTP endpoint; no account, API key or OAuth login is needed. The client must support streamable HTTP rather than old-style SSE.
Before you install
Read-only: it cannot create, change or send anything, and it only sees published blog posts, not accounts, tenants, landlords or properties. Tool calls go to The Wyze's server, though the chat itself does not. Results are cached for five minutes, so brand-new posts may lag.

Installation

In SourceWeft

  1. Open The Wyze Blog in the dashboard and add it to a workspace.
  2. 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/com.thewyze%2Fblog/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "the-wyze-blog": {
      "type": "http",
      "url": "https://thewyze.com/api/mcp"
    }
  }
}

README

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

[How it works: you ask a question, your assistant picks a blog tool and calls it, the Wyze MCP server reads the live blog, and the assistant answers with a link to each post. Below, an example exchange about guaranteed rent.]

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/mcp

That's it. No account, no API key.

Claude (web, desktop and mobile)

[Where the setting lives in Claude: Settings, then Connectors, then Add custom connector. The dialog takes a name, The Wyze Blog, and the server address. A schematic, not a screenshot.]
  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it The Wyze Blog and paste the URL above. Leave the OAuth fields empty: no login is needed.
  3. In a new chat, open the tools menu, turn The Wyze Blog on, and ask your question.

Claude Code

bash
claude mcp add --transport http thewyze https://thewyze.com/api/mcp

Cursor

[Add The Wyze Blog to Cursor]

One click: it opens Cursor and adds a server named thewyze with the URL above. Or paste the config below.

Gemini CLI

bash
gemini extensions install https://github.com/The-Wyze/MCP

ChatGPT

  1. Open Settings → Apps & Connectors. Custom servers sit under Advanced settings (developer mode).
  2. Create a connector named The Wyze Blog, paste the URL above, and choose No authentication.
  3. 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:

json
{  "servers": {    "thewyze": { "type": "http", "url": "https://thewyze.com/api/mcp" }  }}

Cursor by hand (~/.cursor/mcp.json):

json
{  "mcpServers": {    "thewyze": { "url": "https://thewyze.com/api/mcp" }  }}

Windsurf (~/.codeium/windsurf/mcp_config.json):

json
{  "mcpServers": {    "thewyze": { "serverUrl": "https://thewyze.com/api/mcp" }  }}

Gemini CLI by hand (~/.gemini/settings.json, then restart; /mcp lists the tools):

json
{  "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

[An illustrated chat: the question about guaranteed rent, the list_blog_posts tool call with its arguments, three posts with dates and thewyze.com/blog links. Titles are blanked and dates are examples.]

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

[The two tools as cards. list_blog_posts takes an optional search, limit and cursor, and returns posts newest first with slug, title, date, author, excerpt, URL and image. get_blog_post takes a slug and returns the full article as plain text with its description, reading time and FAQs.]

There are two, and they only read:

ToolArgumentsWhat it returns
list_blog_postssearch (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_postslug (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

[Two lists. It sees: published blog posts with their text, FAQs and URLs. It never sees or does: accounts, tenants, landlords, properties or personal data; help-centre, what's-new and glossary posts or drafts; creating, changing or sending anything.]
  • 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 /blog pages 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 seeWhat it means
The assistant answers without using the blogThe 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 unavailableThe blog's backend didn't answer. Try again in a minute.
405 / This server offers no SSE streamThe client opened an old-style SSE connection. Choose HTTP or streamable HTTP when adding the server.
404 Not FoundThe 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 [email protected] 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.

WhereWhat
src/app/api/mcp/route.tsThe endpoint: JSON-RPC handling, the two tools and what they return
src/lib/mcp/serverInfo.tsThe server's name, version and registry card
src/app/.well-known/mcp/server.json/route.tsServes 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

Source: README.md at commit 6083de1

Tools

2

list_blog_posts

List blog posts

Lists 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.

Parameterslimitcursorsearch

get_blog_post

Get blog post

Returns one The Wyze blog post in full (plain text) by its slug.

Parametersslugrequired

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts