mcpField
T
The Wyze Blog

The Wyze Blog

Remote
thewyze.comBusiness & Marketing0Updated 1w ago

About The Wyze Blog

The Wyze Blog is an MCP server for UK landlords and letting agents to search and read published articles about guaranteed rent, temporary accommodation and lettings. Its two read-only tools return article details or full text with source links.

Key features

  1. 01Search and list blog posts
  2. 02Read full article text
  3. 03Return dates, authors and links
  4. 04Paginate and limit search results

Use cases

  1. 01Find articles about guaranteed rent
  2. 02Research temporary accommodation guidance
  3. 03Get the latest posts with source links

MCP support

The hosted MCP server exposes `list_blog_posts` and `get_blog_post` over streamable HTTP. Both tools are read-only and return published blog content.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://thewyze.com/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README
The Wyze Blog MCP: guaranteed rent, temporary accommodation and property management articles for UK letting agents, in your AI assistant

MCP Registry Read only No login Licence

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

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

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.