Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
The Wyze blog: guaranteed rent, temporary accommodation and lettings guides for UK letting agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://thewyze.com/api/mcp在终端中运行这条命令
claude mcp add --transport http blog https://thewyze.com/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"blog": {
"url": "https://thewyze.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"blog": {
"type": "http",
"url": "https://thewyze.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://thewyze.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
list_blog_postsLists 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.
get_blog_postReturns one The Wyze blog post in full (plain text) by its slug.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过域名 thewyze.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 300 毫秒内响应(HTTP 200)
无需登录
已读取 2 个工具描述,未发现针对 AI 的隐藏指令
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Aiterm MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
Add this URL to your AI assistant:
https://thewyze.com/api/mcp
That's it. No account, no API key.
claude mcp add --transport http thewyze https://thewyze.com/api/mcp
One click: it opens Cursor and adds a server named thewyze with the URL above. Or paste the config below.
gemini extensions install https://github.com/The-Wyze/MCP
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.
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).
Every answer can link the post it came from, so you can read the original yourself.
There are two, and they only read:
| Tool | Arguments | What it returns |
|---|---|---|
list_blog_posts | search (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_post | slug (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.
/blog pages don't show them.| What you see | What it means |
|---|---|
| The assistant answers without using the blog | The 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 unavailable | The blog's backend didn't answer. Try again in a minute. |
405 / *This server offers no SSE stream* | The client opened an old-style SSE connection. Choose *HTTP* or *streamable HTTP* when adding the server. |
404 Not Found | The address must be exactly https://thewyze.com/api/mcp. Agency portal domains don't serve it. |
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.
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.
| Where | What |
|---|---|
src/app/api/mcp/route.ts | The endpoint: JSON-RPC handling, the two tools and what they return |
src/lib/mcp/serverInfo.ts | The server's name, version and registry card |
src/app/.well-known/mcp/server.json/route.ts | Serves 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.
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