An AI client that asks the app instead of guessing
Yuteki exposes its data over MCP, an open standard supported by Claude Code, Claude Desktop and other AI clients. Your assistant can read tasks with their comments and attachments and check logged time, and it can create a task from a conversation or log hours just as a person does in the form. Everything goes through the same services, rules and permissions as the web app.
A token with a scope, not a master key
You issue the token yourself in Settings - AI access: a name, the workspaces, the scopes and an optional expiry date. The token never gives more than your own account can do - a scope only narrows it - and taking away your access to a workspace takes it away from the token at once. Tools outside the granted scopes are not even shown to the AI client. The list of tokens shows their scopes and last use, and each can be revoked with one click.
Writes go the same way as in the app
A task created or changed by an AI client sends the same notifications and lands in the same activity log as one changed by hand, and a comment is signed with the name of the token owner. The team sees who did what, whether the work was done in the browser or by an assistant.