Features

Everything for the daily work – from the first issue to the whole team.

Issues, board, releases, time and docs – for your team and your AI agents like Claude. Fast, clear and the same in every project.

AI & MCP · built for AI

Your AI agents work like your team – Claude, Cursor or an agent of your own.

The MCP server runs on the same layer as the web app and the REST API. An assistant sees what you see, may change what you may change, and leaves the same history. Open MCP with OAuth – Claude is our reference, every MCP-capable agent is welcome.

  • Your permissions, nothing more. The assistant acts as the signed-in user. Each app asks for consent and gets only the scopes you grant (read, write, admin). Revoke it any time under Connected Apps.
  • Every change is traceable and can be undone. History reads “Chris via Claude changed Status from To Do to In Progress”. Deletes through MCP go to the trash and come back with one call.
  • Made for language models. Tools take issue keys like WEB-42 and people by name or email, never internal IDs. Results come back as short Markdown plus structured JSON, paged, so answers stay fast and cheap in tokens.
  • Bulk work in one step. Turn a spec into an epic with 30 stories, or close every reviewed bug in a release: up to 50 issues per call, with a result for each one.
  • Agents with their own role. Give each coding agent and script its own persona with a name and permissions. Your customers see the person responsible, not the AI.
Example, schematic: Claude files a bug with a screenshot in IT4S and the history shows “via Claude”.

Connected in a minute

With any MCP-capable agent: in claude.ai or Claude Desktop as a connector, in Claude Code with one command, in Cursor with an entry in mcp.json, in any other MCP client with the address.

In claude.ai or Claude Desktop, add IT4S in the settings under connectors as a custom connector with this address. You sign in once and confirm the scopes.

https://mcp.it4s.at/mcp

Built-in AI features such as summaries, project briefings and release scope suggestions are optional, off by default, and run with your workspace’s own Anthropic key.

Every agent with a name and permissions

Under Connected Apps admins see every connection: which app, which agent, who owns it, what it may do and when it last worked. One click revokes access. Your customers see the person responsible, not the AI.

Connected Apps page of a demo workspace: three apps with their agents, owners, permissions and last use.

Your team just got more members – each with its own permissions.

People and agents work on one board at the same time. Every agent has its own persona with a name and permissions – what it may not do, IT4S refuses. Every change is in the history, with the person and the way.

A board with three people at work at once: Anna moves SHOP-87 to In review, the build agent via Claude Code comments on SHOP-83 and logs 1h 30m, the review bot via Cursor may only read – its move of APP-31 is refused.

50+ tools, covering everything a team member does

Every tool, with the same validation and permissions as the web app.

Issues13

search_issues · get_issue · create_issue · create_issues · update_issue …

  • search_issues
  • get_issue
  • create_issue
  • create_issues
  • update_issue
  • bulk_update_issues
  • transition_issue
  • link_issues
  • unlink_issues
  • check_item
  • watch_issue
  • delete_issue
  • restore_issue

Board & releases10

my_work · my_dashboard · get_board · move_issue · list_releases …

  • my_work
  • my_dashboard
  • get_board
  • move_issue
  • list_releases
  • create_release
  • update_release
  • set_release_issues
  • release_candidates
  • suggest_release_scope

Projects & people18

whoami · list_projects · get_project · create_project · update_project …

  • whoami
  • list_projects
  • get_project
  • create_project
  • update_project
  • list_users
  • set_project_member
  • remove_project_member
  • list_components
  • list_project_groups
  • list_tags
  • get_settings_status
  • list_webhooks
  • create_webhook
  • update_webhook
  • delete_webhook
  • list_webhook_deliveries
  • test_webhook

Docs7

list_docs · get_doc · search_docs · create_doc · update_doc …

  • list_docs
  • get_doc
  • search_docs
  • create_doc
  • update_doc
  • delete_doc
  • restore_doc

Comments, files & code11

add_comment · list_comments · update_comment · delete_comment · create_upload_link …

  • add_comment
  • list_comments
  • update_comment
  • delete_comment
  • create_upload_link
  • upload_attachment
  • get_attachment
  • add_design
  • remove_design
  • link_code
  • unlink_code

Time & reports4

log_work · get_time_report · get_estimate_report · activity_feed

  • log_work
  • get_time_report
  • get_estimate_report
  • activity_feed

Ready-made flows – one sentence is enough

/plan_epic

Plan WEB-80 from this spec. The agent breaks the epic into stories and sub-tasks with estimates and creates them in one go once you agree.

/triage_bugs

Triage the new bugs in WEB. The agent lists bugs without priority or assignee, proposes values for each, and updates them after you confirm.

/implement_issue

Implement WEB-87. The agent reads the issue, its plan and comments, works in the code and reports progress on the issue.

/log_my_day

Log my day. The agent puts together what you worked on today and logs the time on the right issues.

/standup

What happened since yesterday? A short stand-up summary: done, in progress, blocked.

/release_notes

Write the release notes for 2.6. Release notes from the release’s issues, for you to check and save.

Issues

Clear hierarchy. Clear pages.

Epics hold stories, tasks and bugs; those hold sub-tasks. Every issue page starts with an overview: what changed since your last visit and what is waiting for you.

  • Keys like WEB-87, Markdown, tags, priorities and due dates
  • Story points or time estimates – chosen per project
  • Mark comments as a decision, question, blocker or action item; open questions stay visible
  • Parent issues close by themselves once all children are done
  • Components with their own releases, project groups for shared reports
  • History with person and channel, a trash for deleted items
  • On your phone too: its own layout with bottom navigation, cards instead of tables and time in three taps
Overview tab of a sample issue: what is waiting for you, an open question, key facts.

Board

One board for all projects.

Drag cards between Backlog, To Do, In Progress, In Review and Done. Filter by project, release or person. Everyone sees changes right away.

Example board, schematic: issues from three projects in the columns Backlog, To Do, In Progress, In Review and Done.

New in 2.8 · Project briefing

Understand a project in two minutes.

The briefing sums up what a project is about, where it stands and what comes next – with links to every issue it mentions. The same for everyone or “For me”, for a period you choose.

  • Notices when the briefing is out of date
  • Only from data you may see
  • Optional, with your workspace’s own Anthropic key
Project briefing of a sample project.

Releases

Releases that close cleanly.

Plan a version, see what is open, release. IT4S points out unfinished issues instead of moving them quietly – and drafts the release notes.

Release 3.4 with 14 done, 3 in progress and 3 open issues and the warning about unfinished issues.

Time & estimates

From estimate to quote.

Log work as “1h 30m”, keep remaining estimates up to date. The estimate report calculates with an hourly rate and a buffer – as the basis for your quote.

Estimate report of an epic with hours, buffer, hourly rate and total.

Time tracking with jidAI: export in Clockify’s format, an API to reconcile without double entries, and webhooks for every worklog.

Documentation & collaboration

The docs sit next to the work.

Markdown pages per project or release, nested. Issue keys become links, every issue lists the pages that mention it. Your customers see public pages too.

  • See who has an issue or page open or is editing it
  • Drafts are saved automatically, nothing gets lost
  • Confluence spaces move over as docs
Docs page of a demo project with a table of contents, text, linked issue keys and the issues it mentions.

Customers & roles

Your customers on board.

The Customer role only sees the projects you invite them to, and only public comments and docs. Viewers read along for free. What customers and members may do, you decide under Permissions.

May …AdminMemberCustomerViewer
Read issues✓✓✓ in their projects✓
Create issues & comment✓✓Bugs and stories, adjustable–
Log time✓✓adjustable–
Manage projects & people✓–––
CostUserUserUserfree

Integrations

Fits into your toolbox.

GitHub

Pull requests, branches and commits on the issue. A PR sets the status. Links to GitLab and Bitbucket are recognised.

Webhooks New

Signed, with filters by tag and issue type – and manageable through MCP.

REST API

OpenAPI documentation and personal access tokens.

Jira & Confluence New

Import with keys – also into an existing project with rewritten keys.

jidAI & Clockify format

Export time and reconcile without double entries.

Daily digest New

One email in the morning instead of one per change.

Security & data

Your workspace, your data.

EU hosting

Google Cloud in Frankfurt, run by Silvertip in Austria. Workspaces are kept apart in the database.

Secure sign-in

Two-factor codes or Google, can be enforced. Verify your domain and let colleagues join without an invitation.

Backups & export

Nightly backups with one-click restore, full export any time.

Your own address

yourcompany.it4s.at, light and dark, English and German.

All features on every plan.

On the free plan too: MCP, Jira import and everything on this page.