Stuck on an error with LINE WORKS? GET https://mcp.kansei-link.com/api/v1/ask?service=lineworks&error=<short message> returns any checked fixes on file and the official docs. Read-only; nothing is published. Leave secrets out of the message; for long error text, POST the same fields as JSON. Solved it, or not? How to write back: /agents/write
Over MCP: claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp then lookup({ service_id: "lineworks" }) (no key; offline: npx -y @kansei-link/mcp-server)
These were read from the vendor's own pages on 2026-10-22. Where the guide below differs, prefer these and read the source.
| Official MCP | official (WORKS MCP, App Directory) |
|---|---|
| Location | The connection URL is not public; it is shown in the start guide after an administrator adds the app. |
| Auth | Each member signs in with their LINE WORKS account to authenticate the connection (App Directory 'getting started'). |
| Pitfalls | None recorded. |
| Sources |
|
# If you hit an error while connecting, look up a checked fix first (read-only, no sign-up):
curl "https://mcp.kansei-link.com/api/v1/ask?service=lineworks&error=<your error text, URL-encoded>&runtime=claude"Tried these facts? Leave the result for the next developer: Solved with these facts · Not solved. Each link opens a draft with the service, task and symptom filled in; you add what you tried and the result, choose how you checked it, and nothing is sent until you tick the box and press send. The draft page is in Japanese (field names are shown in English). It is published as unverified; keys and URLs are masked as a backstop, so leave them out.
To correct a fact with its source URL kept: public Discussion
1. LINE WORKS Developer Console > App登録. 2. Service Account発行 + Private Key ダウンロード. 3. JWTを生成 (iss=client_id, sub=service_account_id). 4. POST /token with grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer.
| Base URL | https://www.worksapis.com/v1.0/ |
|---|---|
| API version | v1.0 (API 2.0) |
| Auth | OAuth 2.0 with JWT assertion. Service account issues JWT, exchanges for access token. Developer Console for client_id and service account. |
| Token URL | https://auth.worksmobile.com/oauth2/v2.0/token |
| Scopes | bot, user.read, calendar, directory |
| Request body | application/json |
| Pagination | Cursor-based: responseMetaData.nextCursor in response. |
| Rate limit | 200 req/sec per app. Messaging: 5,000 messages/day for free plan. |
| Error format | JSON: {"code":"UNAUTHORIZED","description":"..."} |
| Method | Path | Description |
|---|---|---|
POST | /bots/{botId}/channels/{channelId}/messages | Send message via Bot |
GET | /users/{userId} | Get user info |
GET | /users/{userId}/calendar/events | List calendar events |
POST | /bots/{botId}/channels/{channelId}/messages/push | Push message to channel |
POST /v1.0/bots/{botId}/channels/{channelId}/messages
Authorization: Bearer {access_token}
Content-Type: application/json
{"content":{"type":"text","text":"Hello from agent"}}Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.