# zenn-mcp-server [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/GitHub30/zenn-mcp-server  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/zenn-mcp-server

## Description
A MCP server for Zenn that automates publishing new articles from GitHub via GitHub Actions.

## Tools
Capabilities this server exposes over MCP:

- **post_zenn_article** — Zenn に新規投稿します

Args:
  title: 記事タイトル
  body:  本文 (Markdown)
  topics:  例: ["python", "fastmcp"]

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "zenn-mcp-server": {
    "url": "https://zenn-dev.fastmcp.app/mcp?repo_name=owner/repo&token=YOUR_TOKEN"
  }
}
```

## Documentation

## What zenn-mcp-server MCP server does

The zenn-mcp-server MCP server supports publishing new Zenn articles from a GitHub repository. Its documented workflow links an MCP connector to a repository and uses GitHub Actions to carry out the article publication process. This makes the repository the source for article content while the workflow performs the publishing step.

The project is aimed at a specific use case: maintaining Zenn article files in GitHub and starting publication through an MCP client. It is not documented as a general Zenn administration interface, an article editor, or a tool for managing other Zenn resources.

## How it works

The server is exposed through a FastMCP endpoint at `https://zenn-dev.fastmcp.app/mcp`. The connector URL includes two query parameters:

- `repo_name`: the GitHub repository in `owner/repo` format
- `token`: the access token used with that repository

After the connector is configured, the GitHub Actions workflow from the repository is responsible for processing a new-article request. The README presents the workflow file as a setup requirement, so the repository must contain the relevant action before the connector can be used for this publishing flow.

The zenn-mcp-server MCP server therefore depends on three parts working together: an MCP client, the hosted MCP endpoint, and a GitHub repository configured with the supplied workflow.

## Setup and configuration

Setup begins by adding the project’s GitHub Actions workflow to the target repository. The README links to the `new-article.yml` file in the project’s `.github/workflows` directory as the workflow to add.

Next, create a GitHub token. The documentation includes a token-creation example but does not state the required token scopes in text. Treat the token as a secret and avoid placing it in source files or sharing the complete connector URL in logs, since the URL contains the token as a query parameter.

Finally, create an MCP connector using a URL in this form:

```text
https://zenn-dev.fastmcp.app/mcp?repo_name=owner/repo&token=YOUR_TOKEN
```

Replace `owner/repo` with the target repository and `YOUR_TOKEN` with the GitHub token.

## Tools and capabilities

The documented capability is initiating publication of new Zenn articles from GitHub through GitHub Actions.

Use cases supported by the documentation include:

- Keep Zenn article content in a GitHub repository.
- Start new-article publication from an MCP-compatible client.
- Run the publication process through a repository GitHub Actions workflow.

## Limitations and notes

It also does not document local runtime requirements because the setup uses a hosted endpoint. Confirm those details in the repository workflow and the target client before adopting the integration.

The connector URL carries the GitHub token directly in its query string. Handle that URL as credential-bearing configuration and replace the example values with a repository and token that have the intended access.

_Full upstream README: https://allmcps.com/mcp/zenn-mcp-server/readme_