Personal tasks, inbox and daily plan
List, board, calendar and priorities without unnecessary process.
Tasks, documents and context — one whole.
Tiski brings project work together: from inbox and lists to board, calendar, team and MCP. Start on your own, invite people without moving anything, and never rebuild context from scratch.
Start alone.
Continue together.
Clients, agreements and deadlines
The task reason, materials, deadlines and history stay in one workspace.
Roles, workload and a shared rhythm
Assignees, watchers, dependencies and work status are visible to everyone.
Three layers of one project
Each layer works on its own. Together they form a working context without manual reconstruction.
Tasks
Lists, board, calendar, priorities, subtasks, dependencies, comments and attachments.
Documentation
Decisions, instructions and agreements stay next to the work instead of getting lost in chat.
MCP servers
Controlled access to current tasks and knowledge for connected work tools.
One body of work.
Five ways to see it.
Inbox
New unfiled tasks remain visible and can be sorted later.
List
Group tasks by client, project, stage or your own rhythm.
Board
Move work through statuses and spot bottlenecks immediately.
Calendar
Deadlines sit on a timeline — month and week views with nothing hidden.
Overview and workload
Progress, overdue work and team distribution make planning realistic.
Every task remembers where it came from.
Every task keeps its reason, participants, links and origin, so context never has to be reconstructed from chat.
Reason
Link a task to a lead, deal, contact, booking, invoice or event.
Team
The assignee, collaborators, watchers and author stay next to the work.
Structure
Types, labels, subtasks, blockers and dependencies hold complex work together.
Origin
Tiski records whether a task was created manually, by a scenario or by a workflow.
Connect context without retelling it.
MCP gives selected tools current tasks, project knowledge, statuses and links. Project-scoped keys and change revisions keep access controlled and work consistent.
Project-scoped access
Read or write
Revision-safe changes
01Request
Show release tasks with unresolved decisions
02Tiski
Tasks, documents and recent changes collected
03Tool
Context received. Work can continue
See today at a glance
Filter the example — the list updates without reloading.
4 tasks
Approve the project structure
Personal project
In progressReview the first build
Product launch
ReviewExpand the project documentation
Working knowledge
In progressConnect the MCP server
Development environment
DoneContext stays intact from the first idea to the result
What needs to be done and by when
Why this particular decision was made
Who is moving the work forward now
What changed and what comes next
Tiski in brief
What is Tiski?
A focused workspace where tasks, project documentation and MCP servers form one current context.
Do I need a team to start?
No. Start in a personal space and invite a team when you need one — task context and links stay intact.
Which views does Tiski offer?
Inbox, lists, board, calendar, overview and team workload all use the same tasks — nothing needs to be moved between views.
What can a task be linked to?
A lead, deal, contact, booking, invoice, event and files. The task stays inside the working context.
How does Tiski work with Codex and Claude?
Tiski connects project tasks and knowledge to compatible tools through MCP. Access is limited to selected projects, while revisions keep changes coordinated.
Is Tiski only for software development?
No. MCP is especially useful in development, but tasks, documents and shared context matter in any individual or team project.
Tiski