Chatwork MCP Server

ChatworkをAIから操作するためのMCP(Model Context Protocol)サーバー. Exposed over MCP by the chatwork mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Chatwork を AI から操作するための MCP (Model Context Protocol) サーバーです。

Configuration

You will need 2 environment variables: CHATWORK_API_TOKEN, YOUR_CHATWORK_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @chatwork/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by chatwork; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Chatwork's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the chatwork mcp server does with a few real requests.