search_cy_fe_articlesLABSCO SUMMARY
One archive, searched properly, plus a prompt that uses it.
This is deliberately narrow — one publication's back catalogue — and the payoff is that search covers content and tags rather than titles alone, with a relevance score on every hit. The prompt is what shows the intent: it calls the search tool itself to find related posts, so a summary lands in the publication's existing voice rather than a generic one.
What it is
A TypeScript MCP server for blog search over a Zenn publication's archive. It also ships an MCP prompt that generates frontend-weekly summaries in that publication's style, calling the search tool itself to find related posts.
What you get
- Posts searched across title, description, URL, tags and content, with multiple space-separated keywords treated as OR conditions —
search_cy_fe_articles - Results carrying title, publication date, description, link, content, tags and a relevance score, paged by
limit(default 10, max 100),offsetandorder - A prompt that turns a list of URLs into weekly summaries — a short description, context on the technology, and future implications —
fe-weekly - Two ways to run it:
npx @sakupi01/zenn-articlesor thesakupi/zenn-articlesDocker image
Requirements
No account and no key. npx @sakupi01/zenn-articles over stdio, or pull the Docker image and run it with --network=host. Running the server yourself in code listens on port 8000, with the client pointed at http://localhost:8000/mcp. The query parameter is required and must be 1 to 100 characters. The package is @sakupi01/zenn-articles 1.2.2.
Setup effort
One command — npx @sakupi01/zenn-articles
USE CASES
01
Finding what has already been covered
Search the archive on a topic before writing about it again, and read the scores to judge relevance.
02
Drafting a weekly roundup
Hand the prompt a list of URLs and get consistent summaries with context and implications.
03
Using it without installing anything
Run it from the published sakupi/zenn-articles Docker image instead of installing Node.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
npx (Node.js) for the npm package route, or docker on PATH for the Docker image route
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @sakupi01/zenn-articlesMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"zenn-articles": {
"command": "npx",
"args": [
"@sakupi01/zenn-articles"
]
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"@sakupi01.com/mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"sakupi/zenn-articles"
]
}
}
}
