Connect Claude

Employee

Your personal key so Claude can work in the system with your permissions, the tools, and what it did lately.

MCP

Claude works in RS4IT Tasks as you

With your personal key, Claude can log your work, update your tasks and generate test evidence — with your permissions and no more. Everything it does is recorded in your name “through Claude” in the audit log.

Server address: https://rs4it-tasks.system2030.com/mcp

My key

Claude on the work laptop

rs4t_live_••••••••••••7c2e
Active
Created
⁦2026-10-02⁩
Last used
Today · ⁦10:20⁩
Expires
⁦2027-04-02⁩

A key is never shown whole after it is created — only its shape.

Earlier keys · 1
  • Claude at homers4t_live_••••••••••••19afRevoked

Connect Claude in three steps

Once per device.

  1. Create your key

    From “New key” above. The key is personal — never share it.

  2. 2

    Add it to Claude

    Paste the command in a terminal — or the config into Claude’s file if you use the desktop app.

    claude mcp add --transport http rs4it-tasks https://rs4it-tasks.system2030.com/mcp --header "Authorization: Bearer rs4t_live_••••••••••••7c2e"
  3. 3

    Try it

    Ask Claude in plain words, as you would ask a colleague:

    “⁦Log 2 hours of development today on TSK-104: payment gateway⁩”

What Claude did lately with my key

As in the audit log

  1. Create test evidence

    Today · ⁦10:20⁩

    ⁦Evidence⁩ “⁦Payments statement export⁩” ⁦with four scenarios⁩

    create_evidence
  2. Log work

    Today · ⁦10:18⁩

    ⁦1 h⁩ “⁦Directing⁩ & ⁦reviewing with Claude⁩” ⁦on TSK-104⁩

    log_work
  3. Mark a note fixed

    Today · ⁦09:50⁩

    ⁦Note⁩ “⁦counter does not update⁩” ⁦on EV-02 fixed⁩

    mark_fixed
  4. Team work

    Yesterday · ⁦21:14⁩

    ⁦Asked for Reem⁩’⁦s team work⁩ — ⁦refused⁩, ⁦no permission⁩

    team_work
  5. My week

    Yesterday · ⁦17:40⁩

    ⁦My week: 30.5 h of 40 by Thursday⁩

    my_week
  6. Upload a step

    ⁦2026-11-16 · 14:26⁩

    ⁦11 step images in⁩ “⁦Barcode check-in⁩”

    upload_step
  7. How to generate test evidence

    ⁦2026-11-16 · 14:18⁩

    ⁦Read how to generate test evidence before starting⁩

    evidence_skill

A skill built into the MCP

Generate test evidence

The method is not a file you copy to every machine: the MCP itself carries it. Any Claude connected to RS4IT Tasks reads it from the “evidence_skill” tool and knows how to build the document — scenarios, and several images per scenario.

Version 1.3 · updated ⁦2026-11-02⁩

What Claude does

  1. 1Understand the featureRead the task, its description and the project; ask the programmer what is unclear before starting.
  2. 2Split it into scenariosOne scenario per path a user takes: the normal one, the error, the edge cases. Each with a title and a one-line goal.
  3. 3Capture every stepRun the app for real and capture each step — several images per scenario — with a short caption of what it shows.
  4. 4Upload the evidenceCreate the document, then add the scenarios and their step images in order, and name the tester.
  5. 5Hand it over for reviewThe programmer passes first, notes and marks fixes; then the tester passes.

The tools it calls, in order

create_evidenceadd_scenarioupload_stepadd_notemark_fixed

Preview: a scenario as it comes out

EV-02

From “Barcode check-in” — scenario 4

The live attendance list

⁦The list updates with every scan⁩

Step 1Attendance counter: 312 of 450
Step 2Attendees ordered by entry time
Step 3Searching a guest by name
Samer Al-HalabiDeveloperLeen Al-AhmadTesterOpen the whole document

What Claude can do with your key

Tools follow your role’s permissions (Employee). What you lack is refused, and the refusal is recorded.

13 of 20 tools available to you

Work3/5

  • Log work

    log_work
    Write

    ⁦A work line: date⁩, ⁦type⁩, ⁦hours⁩, ⁦sentence⁩, ⁦project and optional task⁩

  • Correct work

    correct_work
    Write

    ⁦Edits a line within the allowed backdating days⁩

  • My week

    my_week
    Read

    ⁦My hours this week against the expected⁩

  • Team work

    team_work
    Read

    ⁦The team⁩’⁦s lines for a day or a period⁩

    Needs: See the team’s work

  • Comment on a day

    review_day
    Write

    ⁦A supervisor⁩’⁦s comment on a team member⁩’⁦s day⁩

    Needs: Review sample days and comment

Tasks2/3

  • Create a task

    create_task
    Write

    ⁦A task for myself⁩

  • Set a task’s status

    set_task_status
    Write

    ⁦New⁩ → ⁦in progress⁩ → ⁦done⁩

  • Assign a task

    assign_task
    Write

    ⁦A task for a team member⁩

    Needs: Assign tasks

Test evidence6/6

  • How to generate test evidence

    evidence_skill
    Read

    ⁦The built-in skill: how to split evidence into scenarios and capture the steps⁩

  • Create test evidence

    create_evidence
    Write

    ⁦A new document for a feature⁩, ⁦with its tester⁩

  • Add a scenario

    add_scenario
    Write

    ⁦A scenario with its title and goal⁩

  • Upload a step

    upload_step
    Write

    ⁦A step image with its caption⁩

  • Add a note

    add_note
    Write

    ⁦A programmer⁩’⁦s or tester⁩’⁦s note on a scenario⁩

  • Mark a note fixed

    mark_fixed
    Write

    ⁦For the document⁩’⁦s programmer⁩

Leave1/2

  • Request leave

    request_leave
    Write

    ⁦At least 30 days ahead⁩

  • Decide on leave

    decide_leave
    Write

    ⁦Approve or reject⁩, ⁦with a note⁩

    Needs: Approve leave

Reports0/2

  • Monthly report

    monthly_report
    Read

    ⁦Per person: lines⁩, ⁦hours⁩, ⁦expected⁩, ⁦difference⁩, ⁦leave⁩, ⁦no-log days⁩

    Needs: Team reports

  • Evaluation indicators

    evaluation
    Read

    ⁦Missed and fixed notes and time to fix⁩

    Needs: Evaluation indicators

People1/1

  • List people

    list_people
    Read

    ⁦Within the key owner⁩’⁦s reach⁩

Administration0/1

  • Add an official holiday

    add_holiday
    Write

    ⁦Eid al-Fitr and Eid al-Adha for coming years⁩

    Needs: Official holidays