Spool is one workspace for a software team’s day-to-day work. Your meetings, docs, files, work items and sprints live side by side, so the decision from Tuesday’s call and the item that came out of it stay connected.
Who it’s for
Spool is built for teams that ship software, especially teams that work with clients or vendors. Each group gets its own team with its own people, projects and statuses, and private teams stay hidden from everyone else.
It also suits teams that use coding agents. Agents connect to Spool over MCP and act as the person who connected them, with that person’s permissions.
What you can do in Spool
- Meetings: record a call with the Chrome extension or upload a recording. Spool writes a transcript and notes, and you can file the meeting under a project.
- Docs: write project docs with a draft you edit together and a published version you can share with people outside your team.
- Artifacts: keep a project’s files and links in folders, like a shared drive.
- Work items: track epics, stories, tasks and bugs on a list or a board, with keys like
ACM-42. - Sprints: plan items into time-boxed sprints and follow progress while the sprint runs.
- Inbox: see assignments, mentions, replies and updates on items you follow, in one place.
- Coding agents: connect Claude, Cursor or any MCP client so it can read and update your work.
How Spool is organised
Everything sits inside a workspace. A workspace has teams, each team has projects, and a project holds its items, sprints, meetings, docs and artifacts. Read Key concepts for the full picture.
Start here
Quickstart
Key concepts
Finding your way
Meetings
Docs
Artifacts
Work items
Sprints
Inbox
Coding agents
Workspace