Connect Claude
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.
My key
Claude on the work laptop
rs4t_live_••••••••••••7c2e- 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.
Create your key
From “New key” above. The key is personal — never share it.
- 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
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
Create test evidence
Today · 10:20Evidence “Payments statement export” with four scenarios
create_evidenceLog work
Today · 10:181 h “Directing & reviewing with Claude” on TSK-104
log_workMark a note fixed
Today · 09:50Note “counter does not update” on EV-02 fixed
mark_fixedTeam work
Yesterday · 21:14Asked for Reem’s team work — refused, no permission
team_workMy week
Yesterday · 17:40My week: 30.5 h of 40 by Thursday
my_weekUpload a step
2026-11-16 · 14:2611 step images in “Barcode check-in”
upload_stepHow to generate test evidence
2026-11-16 · 14:18Read 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
- 1Understand the featureRead the task, its description and the project; ask the programmer what is unclear before starting.
- 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.
- 3Capture every stepRun the app for real and capture each step — several images per scenario — with a short caption of what it shows.
- 4Upload the evidenceCreate the document, then add the scenarios and their step images in order, and name the tester.
- 5Hand it over for reviewThe programmer passes first, notes and marks fixes; then the tester passes.
The tools it calls, in order
Preview: a scenario as it comes out
EV-02From “Barcode check-in” — scenario 4
The live attendance list
The list updates with every scan
What Claude can do with your key
Tools follow your role’s permissions (Employee). What you lack is refused, and the refusal is recorded.
Work3/5
- Write
Log work
log_workA work line: date, type, hours, sentence, project and optional task
- Write
Correct work
correct_workEdits a line within the allowed backdating days
- Read
My week
my_weekMy hours this week against the expected
- Read
Team work
team_workThe team’s lines for a day or a period
Needs: See the team’s work
- Write
Comment on a day
review_dayA supervisor’s comment on a team member’s day
Needs: Review sample days and comment
Tasks2/3
- Write
Create a task
create_taskA task for myself
- Write
Set a task’s status
set_task_statusNew → in progress → done
- Write
Assign a task
assign_taskA task for a team member
Needs: Assign tasks
Test evidence6/6
- Read
How to generate test evidence
evidence_skillThe built-in skill: how to split evidence into scenarios and capture the steps
- Write
Create test evidence
create_evidenceA new document for a feature, with its tester
- Write
Add a scenario
add_scenarioA scenario with its title and goal
- Write
Upload a step
upload_stepA step image with its caption
- Write
Add a note
add_noteA programmer’s or tester’s note on a scenario
- Write
Mark a note fixed
mark_fixedFor the document’s programmer
Leave1/2
- Write
Request leave
request_leaveAt least 30 days ahead
- Write
Decide on leave
decide_leaveApprove or reject, with a note
Needs: Approve leave
Reports0/2
- Read
Monthly report
monthly_reportPer person: lines, hours, expected, difference, leave, no-log days
Needs: Team reports
- Read
Evaluation indicators
evaluationMissed and fixed notes and time to fix
Needs: Evaluation indicators
People1/1
- Read
List people
list_peopleWithin the key owner’s reach
Administration0/1
- Write
Add an official holiday
add_holidayEid al-Fitr and Eid al-Adha for coming years
Needs: Official holidays