Chatwork API

Is there a Chatwork MCP server?

You don't need an MCP server to give your agent Chatwork. Jentic connects it directly from the API Directory: import the Chatwork API, store your X-ChatWorkToken once, and your agent calls it.

What authentication does the Chatwork API use?

The spec behind this page declares an API key passed in the X-ChatWorkToken header, and Chatwork generates those tokens per user from the account settings page. Chatwork's own OpenAPI definition on developer.chatwork.com additionally declares OAuth 2.0 with an authorization-code flow and per-resource scopes such as rooms.messages:write. Through Jentic, the credential is stored encrypted in your Jentic One instance and injected at execution time, so agents never see the raw value.

Can I post messages to a Chatwork room with the API?

Yes. POST /rooms/{room_id}/messages accepts a body parameter and posts the message to the specified room. Chatwork supports its own [To:] and [info] tags inside message bodies for mentions and styling.

How do I create a task in Chatwork via the API?

Use POST /rooms/{room_id}/tasks with the body, assigned account ids (to_ids), and an optional limit timestamp. The endpoint returns the created task ids, which you can later mark complete with the task status update operation.

What are the rate limits for the Chatwork API?

Chatwork's documentation states a limit of 300 API requests per 5 minutes, with the remaining call count and the reset time returned in response headers. Posting messages or tasks to a room is capped separately at 10 calls per 10 seconds. Exceeding either limit returns HTTP 429, so retry with backoff and batch reads where possible.

How do I post a message to Chatwork through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh` on the machine hosting your instance, then run `jentic register` on the separate machine where your agent runs. Add the Chatwork API from the API Directory, store your token once, and ask the agent to post the message: Jentic resolves the intent to POST /rooms/{room_id}/messages and injects the X-ChatWorkToken header at execution time.

Can I limit what my agent is allowed to do with the Chatwork API?

Yes. Because Chatwork puts the room id in the URL path (/rooms/{room_id}/...), a rule in your self-hosted Jentic One instance can pin your agent to a single room, letting it post messages, add tasks with POST /rooms/{room_id}/tasks, and upload files there and nothing else. You choose which operations the agent may call, so creating new group chat rooms with POST /rooms is excluded unless you add it. Your own rules decide which endpoints and the X-ChatWorkToken credential the agent can use at execution time.