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 分