Work Handler

app.work-handlerPublished by work-handler.appOfficial publisherv1.0.1Updated Oct 27, 2026

AI から使えるクラウドグループウェア Work Handler の MCP サーバー。組織・メンバーの参照、出退勤の共有、タイムカード、承認フロー等を本人の権限の範囲で操作できる。

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Work Handler, a cloud groupware, letting an assistant view organizations and members and handle attendance, timecards and approval flows…

What you can do
  • Look up organizations and members
  • Share and check clock-in and clock-out status
  • Handle timecard records
  • Work with approval flows
  • All actions are limited to the permissions of the authenticated user.
When to use it
Useful when an assistant should help with everyday HR and groupware chores in Work Handler: checking who is in which organization, reporting or reviewing attendance, and moving approval requests along without switching apps.
Requirements
A remote MCP endpoint at work-handler.app over streamable HTTP. A Work Handler account and an MCP API key issued by the service, sent as a bearer token in the Authorization header. No local runtime or environment variables are needed.
Before you install
The API key in the Authorization header is a secret and grants access to company data within the user's permissions; keep it private and revocable. Attendance, timecard and approval actions can change records and trigger workflows, so review writes before they happen. Organizational and member data is sent to the remote service.

Installation

In SourceWeft

  1. Open Work Handler in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.work-handler%2Fwork-handler/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "work-handler": {
      "type": "http",
      "url": "https://work-handler.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.0.1LatestSep 26, 2026
  2. v1.0.0Sep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.