articleC
Fetch articles from Zenn.dev
Inputs: username, topicname, order, page, +1 more.
Provides access to Zenn's content platform API, allowing fetching lists of articles and books from Zenn.dev.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Zenn MCP Server fetch recent articles about Python programming"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This is an unofficial Model Context Protocol server for Zenn. Build on top of Zenn's dev API.
Related MCP server: Notion MCP Server
Fetch a list of articles
Fetch a list of books
This project is not yet set up for ephemeral environments (e.g. uvx usage). Run this project locally by cloning this repo:
git clone https://github.com/shibuiwilliam/mcp-server-zenn.gitYou can launch the MCP inspector via npm:
npx @modelcontextprotocol/inspector uv --directory=src/mcp_server_zenn run mcp-server-zennUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
OR Add this tool as a MCP server:
{
"zenn": {
"command": "uv",
"args": [
"--directory",
"/path/to/mcp-server-zenn",
"run",
"mcp-server-zenn"
]
}
}(TODO)
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches articles and the other fetches books from Zenn.dev. There is no overlap in functionality, and an agent can easily differentiate between them based on the resource type (articles vs. books).
Both tools follow a consistent naming pattern using simple, descriptive nouns (article and book) that directly indicate the resource being fetched. There are no deviations in style or convention, making the naming straightforward and predictable.
With only two tools, the server feels thin for a content platform like Zenn.dev. While fetching articles and books covers core read operations, the lack of tools for creating, updating, or managing content (e.g., publishing, searching, or user interactions) makes the set under-scoped for typical agent workflows.
The tool set is severely incomplete for a Zenn.dev server. It only supports fetching articles and books, missing essential operations such as creating or updating content, searching, managing user profiles, or handling interactions (e.g., likes, comments). This will likely cause agent failures when trying to perform common tasks beyond basic retrieval.
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for Studex tools, notifications, and profile integrations
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server