The Wyze Blog

com.thewyze由 thewyze.com 發布官方發布者v1.0.0更新於 Nov 7, 2026

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

已驗證Streamable HTTP可網頁執行知識與記憶商業與電商

概覽

AI 產生的概覽

唯讀存取 The Wyze 部落格(涵蓋保證租金、臨時住宿與英國租賃業務),讓助理搜尋文章並讀取附連結的全文。

可以做什麼
  • 依最新優先列出部落格文章,含標題、日期、作者、摘要與網址,可依搜尋詞篩選
  • 依 slug 或部落格網址讀取單篇文章的純文字全文
  • 透過游標分頁,每頁可回傳 1 至 20 篇
適用情境
當你希望助理針對保證租金方案、臨時住宿或租賃業務經營給出有依據的回答,並附上原文連結,而不是憑記憶作答時適用。
執行需求
遠端 streamable HTTP 端點;不需帳號、API 金鑰或 OAuth 登入。用戶端需支援 streamable HTTP,而非舊式 SSE。
安裝前請注意
僅唯讀:無法建立、修改或傳送任何內容,且只能看到已發布的部落格文章,不涉及帳戶、房客、房東或房產資料。工具呼叫會送往 The Wyze 的伺服器,但聊天內容本身不會。結果快取五分鐘,新文章可能稍有延遲。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 The Wyze Blog,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.thewyze%2Fblog/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

來源:README.md,提交 6083de1

工具

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.

輸入參數limitcursorsearch

get_blog_post

Get blog post

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

輸入參數slug必填

版本歷史

1
  1. v1.0.0最新Nov 7, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分