Integration

Chatwork integration

Chatwork is a Japanese business chat service. An agent can read the user's profile, unread counts and tasks, list contacts and approve or reject contact requests, list, create, update, leave or delete group chats and change their members, read, post, edit and delete messages (Chatwork message notation such as [To:account_id] is supported), mark messages read or unread, create tasks and change their status, list and upload files, and manage a chat's invitation link. Requests are limited to 300 per 5 minutes, and posting messages or tasks to one chat to 10 per 10 seconds. Authentication is an API token sent in the x-chatworktoken header (it never expires and grants full access; organisation plans need admin approval to use the API), or OAuth 2.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Chatwork.Built from the 32 Chatwork tools below, on the connection you add once.

What you can do with Chatwork

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Message, 7 operations

  • create_messageCreate messagePOSTPost a message to a chat. Supports Chatwork notation such as [To:account_id] mentions. Limited to 10 posts per 10 seconds per chat (messages and tasks together).
  • delete_messageDelete messageDELETEDelete a message from a chat. Irreversible.
  • get_messageGet messageGETGet one message of a chat: poster, body, send time and last update time.
  • list_messagesList messagesGETList up to 100 messages of a chat. By default only messages new since the previous call are returned; force=1 returns the latest 100.
  • mark_messages_readMark messages readPUTMark the messages of a chat as read, up to message_id when given. Fails with 400 when they are already read. Returns the new unread and mention counts.
  • mark_messages_unreadMark messages unreadPUTMark the messages of a chat as unread from message_id onwards. Fails with 400 when they are already unread. Returns the new unread and mention counts.
  • update_messageUpdate messagePUTReplace the body of one of your messages in a chat.

Room, 5 operations

  • create_roomCreate roomPOSTCreate a group chat with a name and members by role (at least one admin, account IDs of contacts or organisation members), optionally with an invitation link. Returns room_id.
  • get_roomGet roomGETGet one chat: name, type, the user's role, pin flag, unread, mention, task, message and file counts, icon, last update time and description.
  • leave_or_delete_roomLeave or delete roomDELETELeave a group chat (deletes your tasks and files in it) or delete it (deletes all its messages, tasks and files) with action_type. Irreversible.
  • list_roomsList roomsGETList the chats the user belongs to with type (my, direct, group), the user's role, pin flag, unread, mention and task counts and last update time.
  • update_roomUpdate roomPUTChange a group chat's name, description or icon. Leave a field out to keep its current value.

Task, 5 operations

  • create_taskCreate taskPOSTCreate a task in a chat for one or more members (to_ids), with an optional deadline (Unix seconds). Returns the new task IDs. Limited to 10 per 10 seconds per chat.
  • get_taskGet taskGETGet one task of a chat: assignee, requester, body, deadline, deadline type and status.
  • list_my_tasksList my tasksGETList up to 100 tasks assigned to the authenticated user, optionally only those requested by one account or with status open or done.
  • list_room_tasksList room tasksGETList up to 100 tasks of a chat, optionally filtered by assignee, requester or status (open or done).
  • update_task_statusUpdate task statusPUTSet the status of a task to done or open (reopen).

Invitation link, 4 operations

  • create_room_linkCreate room linkPOSTCreate the invitation link of a chat, with an optional code, approval setting and description. Fails with 400 if a link already exists.
  • delete_room_linkDelete room linkDELETEDelete the invitation link of a chat. Fails with 400 if the link is disabled.
  • get_room_linkGet room linkGETGet the invitation link of a chat: whether it is public, its URL, whether joining needs admin approval and its description.
  • update_room_linkUpdate room linkPUTChange the invitation link of a chat (code, approval setting, description). Leave a field out to keep it. Fails with 400 if the link is disabled.

Contact request, 3 operations

  • approve_contact_requestApprove contact requestPUTApprove a contact request sent to the authenticated user. Returns the new contact.
  • list_contact_requestsList contact requestsGETList up to 100 contact requests sent to the authenticated user, with the requester's account and message.
  • reject_contact_requestReject contact requestDELETEReject a contact request sent to the authenticated user.

File, 3 operations

  • get_room_fileGet room fileGETGet one file of a chat: uploader, message, file name, size and upload time; with create_download_url=1 also a download URL valid for 30 seconds.
  • list_room_filesList room filesGETList up to 100 files of a chat, optionally only those uploaded by one account.
  • upload_room_fileUpload room filePOSTUpload a file (5 MB maximum) to a chat, with an optional message posted with it. Returns the file ID.

Room member, 2 operations

  • list_room_membersList room membersGETList the members of a chat with their role (admin, member, readonly), name, Chatwork ID, organisation and avatar URL.
  • update_room_membersUpdate room membersPUTChange the members of a group chat in bulk, by role: comma-separated account IDs for admins (at least one), members and read-only members.

Contact, 1 operation

  • list_contactsList contactsGETList the contacts of the authenticated user with their account ID, direct chat room ID, name, Chatwork ID, organisation and avatar URL.

Me, 1 operation

  • get_meGet meGETGet the profile of the authenticated user: account ID, own chat room ID, name, Chatwork ID, organisation, department, title, contact details and avatar URL.

Status, 1 operation

  • get_my_statusGet my statusGETGet the authenticated user's counters: unread messages, unread mentions and open tasks, plus how many chats have each.

Use Chatwork from Claude Code, Cursor or Codex

Connect Chatwork in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Chatwork operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Chatwork

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Chatwork once

    Add your Chatwork connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Chatwork integration FAQ

What can you do with the Chatwork integration?

LiveContext exposes 32 operations on Chatwork, covering message, room, task and invitation link.

Popular integrations

Browse the whole catalog