Skip to main content
Glama

mcp-server-zenn: Unofficial MCP server for Zenn (https://zenn.dev/)

Overview

This is an unofficial Model Context Protocol server for Zenn. Build on top of Zenn's dev API.

Related MCP server: Notion MCP Server

Features

  • Fetch a list of articles

  • Fetch a list of books

Run this project locally

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.git

You can launch the MCP inspector via npm:

npx @modelcontextprotocol/inspector uv --directory=src/mcp_server_zenn run mcp-server-zenn

Upon 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"
    ]
  }
}

Deployment

(TODO)

License

Available Tools

2 tools
articleC

Fetch articles from Zenn.dev

Inputs: username, topicname, order, page, +1 more.

bookC

Fetch books from Zenn.dev

Inputs: username, topicname, order, page, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers