Chatwork
Chatwork is a team communication platform featuring group chats, file sharing, and task management, aiming to enhance collaboration and productivity for businesses
Verdict
Common use cases
- Triage unread messages across all rooms
- Audit room membership before sharing sensitive files
- Retrieve file metadata for compliance reviews
- Delete outdated messages from project threads
- Surface mentions and tasks at standup
Integration
- Vendor
- Chatwork
- Category
- communication
- Auth
- API_KEY
- Tools
- 8
- Composio slug
chatwork
Tools
- Delete Messagedestructive
This tool allows you to delete a specific message from a chatwork room by calling the delete endpoint at https://api.chatwork.com/v2/rooms/{room id}/messages/{message id}. it requires authentication using a chatwork api token provided in th
- Get Chatwork Contacts
This tool retrieves a list of all contacts from chatwork. it is a fundamental tool that fetches all contact information such as account id, room id, name, chatwork id, organization details, department, and avatar image url, without needing
- Get Chatwork File
This tool retrieves information about a specific file in a chat room. the api endpoint get /v2/rooms/{room id}/files/{file id} provides file details such as file id, account id, message id, filename, filesize, upload time, and download url,
- Get Chatwork Rooms
This tool retrieves a list of all chat rooms associated with the authenticated chatwork account. it includes group chats, direct chats, and personal chats, and does not require any additional parameters beyond authentication.
- Get My Chatwork Status
This tool retrieves the current status of the authenticated user, including unread message counts and task status. it provides a quick overview of unread messages, mentions, and tasks, making it valuable for monitoring chatwork activity and
- Get Room Members
This tool retrieves a list of all members in a specified chatwork room using the endpoint get /rooms/{room id}/members. it provides essential details like account id, role, name, chatwork id, organization id, and organization name, compleme
- Get Room Messages
This tool retrieves messages from a specific chatwork room using the get https://api.chatwork.com/v2/rooms/{room id}/messages endpoint. it requires a room id parameter and an optional force flag to refresh the cache by retrieving the 100 ne
- Upload File to Chatwork Room
This tool allows users to upload files to a specific chatwork room. it enables file sharing functionality within the chatwork platform by providing an endpoint to upload files (along with an optional message) to a given room.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Chatwork from the communication category. 3. Log into your Chatwork account at chatwork.com, go to Account Settings > API Token, and generate a new token with full read/write permissions. 4. Copy the token and paste it into the API Key field in Switchy, then click 'Connect'. 5. Switchy will verify the token by fetching your user status; if successful, you'll see 'Connected' with a green indicator. 6. Open any Space, type '@Chatwork get my status' and send — the AI should return your unread message count and task summary. 7. If the response includes valid data, the integration is live and ready for team use.
What teammates see: by default, memories from Chatwork are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Unread Message Summary
@Chatwork get my status and summarize which rooms have the most unread messages or mentions waiting for me.Open in a Space →
Room Member Audit
@Chatwork get room members for room ID 12345678 and tell me who has admin versus member roles.Open in a Space →
Recent Message Scan
@Chatwork get room messages from room ID 12345678 and extract any tasks or deadlines mentioned in the last 20 messages.Open in a Space →
File Retrieval Check
@Chatwork get file details for file ID 87654321 in room ID 12345678 and show me the uploader and timestamp.Open in a Space →
Contact Directory Lookup
@Chatwork get my contacts and find anyone from the 'Engineering' department with 'Tokyo' in their organization name.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@chatwork show me all unread messages and mentions across my rooms, then summarize what needs my attention today
Based on your Chatwork status, you have 23 unread messages across 5 rooms, with 4 direct mentions. Here's what needs attention: In 'Product Launch Q1', you're mentioned in 2 threads about the pricing deck deadline (today at 5pm). In 'Engineering Sync', there's a blocker on the API integration that tags you. The 'Client - Acme Corp' room has 12 unread messages but no direct mentions—mostly status updates. Two tasks are assigned to you: finalize the budget spreadsheet and review the contract amendment.
This example combines the 'Get My Chatwork Status' tool with 'Get Room Messages' to provide context-aware triage. The MCP requires API key authentication with read permissions. Note that Chatwork's API has rate limits (typically 100 requests per 5 minutes), so fetching messages from many rooms simultaneously may hit throttling on larger workspaces.
@chatwork upload the revised_contract.pdf file to the 'Legal Review' room with a message saying it's ready for final approval
File uploaded successfully to the 'Legal Review' room (Room ID: 198472651). The file 'revised_contract.pdf' (2.3 MB) has been posted with your message: 'This is ready for final approval.' All 6 room members will see the notification. The file is now accessible at the provided Chatwork file URL and can be downloaded by anyone with room access.
This demonstrates the 'Upload File to Chatwork Room' tool, which posts files directly into conversations. Important: This action is immediate and irreversible through the MCP—you'll need to manually delete the message in Chatwork if you upload to the wrong room. Ensure you have the correct room ID before executing, as room names aren't unique identifiers in the API.
@chatwork find all rooms where 'Q1 budget' appears in recent messages, then list the members of those rooms so I know who to follow up with
Found 'Q1 budget' mentioned in 3 rooms over the past 100 messages: (1) 'Finance Team' room has 8 members including Sarah Chen (CFO), Marcus Liu (Finance Manager), and 6 analysts. (2) 'Executive Committee' room has 5 members: all C-suite executives. (3) 'Product Strategy' room has 12 members spanning product, engineering, and marketing. The most recent budget discussion was 2 hours ago in Finance Team, where Sarah requested updated projections by EOD Thursday.
This workflow chains 'Get Chatwork Rooms', 'Get Room Messages' (with search logic applied by the AI), and 'Get Room Members' to surface cross-functional context. The MCP doesn't offer native search—the AI filters messages client-side, so this works best for recent conversations (last ~100 messages per room). For deep historical search, use Chatwork's web interface directly.
Use-case deep-dives
When Chatwork beats Slack for external client threads
A 6-person design agency runs client projects in Chatwork because their Japanese and Taiwanese clients already live there. The MCP shines here: agents pull room messages and file metadata during weekly status calls, then post summaries back to the client room without tab-switching. The Get Room Members tool confirms who's active before tagging stakeholders. The threshold: if your clients are on Slack or Teams, this MCP adds friction instead of removing it. Chatwork's API is solid but narrow—no threading, no reactions, no search beyond message retrieval. If your agency books 80% of revenue from APAC clients on Chatwork, this MCP turns your AI into a bilingual project coordinator.
How small support teams use Chatwork MCP for inbox zero
A 3-person customer success team at a SaaS company uses Chatwork for B2B support in Japan. Every morning, an agent calls Get My Chatwork Status to surface unread mentions and tasks, then fetches messages from high-priority rooms. The AI drafts replies in Japanese, flags escalations, and marks resolved threads. The Delete Message tool cleans up test pings or duplicate asks. This works because Chatwork's task system is built into the platform—agents can check task counts without a separate tool. The limit: if your support volume exceeds 200 messages per day, Chatwork's lack of bulk-read endpoints makes this slow. For teams under that threshold, the MCP cuts triage time by half.
When Chatwork MCP replaces manual standup summaries
A 10-person engineering team spread across Tokyo, Manila, and Singapore runs async standups in a Chatwork room. Each morning, an agent pulls the last 24 hours of messages, groups updates by person, and posts a digest to a separate planning room. The Get Chatwork Contacts tool maps account IDs to names for clean formatting. The Upload File tool attaches sprint board screenshots. This scenario works because Chatwork's room structure is flat—no channels, no noise. The trade-off: if your team uses threaded conversations or emoji reactions for context, those signals are invisible to the MCP. For teams that post linear updates in a single room, this MCP turns standup chaos into a readable log.
Frequently asked
What can the Chatwork MCP do in Switchy?
It connects your Chatwork workspace to Switchy's AI agents so they can read messages, fetch room lists, retrieve contacts, check your unread counts, and upload or delete files. Agents can't send messages or create rooms — those actions require Chatwork's webhook API, which this MCP doesn't expose. Use it when you want AI to summarize threads, find files, or audit room membership without leaving Switchy.
Do I need admin access to connect Chatwork?
No. Chatwork uses API key authentication, not OAuth, so you generate a personal API token from your own account settings. The MCP inherits whatever permissions your Chatwork account has — if you're a regular member, agents can only see rooms and messages you can see. Admins get no special privileges here; the API key scope is tied to the user who creates it.
Can the MCP send messages or create tasks in Chatwork?
No. The eight tools focus on reading data — fetching rooms, messages, contacts, files, and member lists — plus deleting messages and uploading files. Chatwork's API supports posting messages and tasks, but this MCP doesn't expose those endpoints. If you need agents to send messages, you'll have to call Chatwork's REST API directly or wait for the vendor to add those tools.
How does this compare to using Chatwork's web app or API directly?
The MCP saves you from writing API client code and handling pagination yourself. Agents get structured access to rooms, messages, and files in one step instead of chaining multiple HTTP requests. The trade-off is you're limited to the eight tools the MCP exposes — Chatwork's full API has endpoints for reactions, tasks, and webhooks that aren't available here. Use the MCP for read-heavy workflows; use the raw API for write-heavy automation.
Who on the team should connect the Chatwork MCP?
Whoever owns the Chatwork rooms your agents need to read. Because API keys inherit user permissions, connect the MCP under an account that's a member of all relevant rooms. If you connect it with a limited user, agents won't see private rooms or restricted files. One connection per Switchy workspace is enough — all team members share the same MCP instance and its access scope.