The Wyze

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.

Related MCP server: LondonIQ MCP Server

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

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

Claude (web, desktop and mobile)

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

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

Cursor

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

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

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.

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