Skip to content
$ claude mcp add --transport http it4s https://mcp.it4s.at/mcp > search_issues project: SHOP status: open SHOP-87 Apple Pay payment fails ● In Progress > transition_issue SHOP-87 → in_review > create_issues parent: SHOP-80 (12 stories) ✓ SHOP-101 … SHOP-112 created > log_work SHOP-87 1h 30m "Apple Pay fix" ✓ logged · via Claude
BBuild agent · AI agentPR #212 opened · SHOP-87 → In Review
To Do
SHOP-91
OPS-14
APP-34
In Progress
SHOP-87
SHOP-83
In Review
APP-31
SHOP-80
Done
SHOP-60
APP-22
IT4S Issue Tracking
FeaturesAI & MCPPricingHelpAbout us
DeutschEnglish
Start free trial
FeaturesAI & MCPPricingHelpAbout usStart free trial
← User guide

Getting started

Getting startedTime zone of a workspaceTrial, limit warnings and inactive workspaces

Issues, board & releases

IssuesBoard, releases and documentationProject briefingTime tracking

AI agents & MCP

Working with AI agents and other appsAgents: personas for connected appsAI agents and your customers

Administration & billing

AdministrationRoles and customersPlan & BillingUpgrade to Team and billingArchive or delete a projectSilvertip support access

Moving over & integrations

Moving from Jira
Help › User guide › Agents: personas for connected apps

Agents: personas for connected apps

Updated: 2026-11-06

A coding agent you connect (Claude Code, Cursor …) can work as a named team member, for example Homer for Cursor on your laptop, instead of showing up as "you via Cursor".

What an agent is

  • An agent has a name, a picture and a short description. You own it.
  • Everything the app does through its connection shows the agent: new issues (as reporter), comments, worklogs, files, the history, and live updates. Its picture is a rounded square with a small sparkle badge, and its name has an AI pill. People stay round.
  • An agent never has more rights than you: it works with your project roles and the scopes of its connection. Where you are a viewer, so is your agent.
  • Agents do not sign in, get no emails and are no project members.

Set up an agent

  • When you connect an app: the consent screen asks Name this agent (optional). Choose No agent (the app acts as you), one of your agents, or New agent… with a name.
  • Later: My Profile › Agents › Add Agent, or on Connected Apps (admins) the row menu of your own connection: Set Up Agent.
  • The dialog: name (unique among people and agents), description, which of your app connections act as this agent (several may share one, for example your two Cursor installations), a picture once it is saved, and Remove Agent. Edit Agent opens it again.
  • Remove: the connections act as you again; the agent keeps its name in the history. Adding an agent with the same name brings it back.
  • If you disconnect an agent's last app, the agent becomes inactive. Reconnecting the same app keeps its agent.

Work with agents

  • Assign and mention: agents appear in the assignee and reporter fields and in the people filters, after the people (grouped People · Agents). Mention them with @Homer.
  • Emails for you: when someone assigns your agent, mentions it, or comments on an issue it watches, you get the email ("assigned WEB-42 to your agent Homer"), following your own email choices. You get none for what the agent or you did yourself.
  • Filters: the Assignee chip on Issues and the Board starts with All people and All agents; My agents shows the issues of your agents.
  • My Work: the tile My agents counts the open issues assigned to your agents and opens them.
  • Time Report: Agents: On their own shows an agent's worklogs under its name; With their owner adds them to yours.
  • Users (admins): Show: Agents lists all agents with their owner, description and apps.
  • Customers and viewers see the person behind the agent (see AI agents and your customers).

For agents (MCP)

whoami tells the agent who it acts as. In an agent's session, "me" means the agent and "my_owner" means you, for example assignee: "my_owner" to hand an issue back to you.

Not yet

  • Editing your agent's comments or worklogs from your browser: the agent edits its own through its connection; you are a different person in the browser.
  • Starting an agent run when an issue is assigned to it.
IT4S Issue Tracking

Pronounced “IT Force”. Issue tracking by Silvertip IT-Solutions from Innsbruck, Austria.

Product

FeaturesAI & MCPPricingCompared to Jira

Help

DocumentationFAQAPI referenceRelease notes

Company

About usContactLegal noticePrivacyTerms & DPACookiesSub-processors
© 2026 Silvertip IT-Solutions GmbH · Hosted in the EU