CTAS Work

vn.ctasPublished by ctas.vnOfficial publisherv1.0.0Updated Nov 4, 2026

Attendance, shifts, leave, payroll and team tools for CTAS Work organizations.

The publisher's own server: CTAS Life

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for CTAS Work organizations, giving an assistant tools for attendance, shifts, leave, payroll and team data.

What you can do
  • Work with attendance records for the organization
  • Manage shifts and scheduling
  • Handle leave requests and balances
  • Access payroll information
  • Work with team and staff data
When to use it
Useful when an assistant should answer questions or take actions about staff attendance, shift scheduling, leave or payroll inside a CTAS Work organization, instead of switching to the CTAS Work interface.
Requirements
A remote endpoint at api.ctas.vn over streamable HTTP. OAuth authentication is required, so the user needs a CTAS Work organization account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server handles HR data such as attendance, leave, payroll and team records, which is sensitive personal and salary information. OAuth grants the assistant access to that organization data, and the tools may change records; review what the connected account is allowed to do before authorizing.

Installation

In SourceWeft

  1. Open CTAS Work in the dashboard and add it to a workspace.
  2. Connect the required 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/vn.ctas%2Fwork/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ctas-work": {
      "type": "http",
      "url": "https://api.ctas.vn/mcp/work"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

83% 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
  • Documentation15 pts
  • 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.

Other Ctas integrations