The whole project.
Not just the next task.

Give your work a shared home: the goal, the people, the next steps, and the decisions that make it all make sense.

On this page
Studio workspace Illustrative example
Projects / Website launch

A thoughtful launch.

One place for the brief, the next steps, and the decisions.

Goal

Launch a clear, useful home for our new product. Keep the first release focused.

Write the project briefDone
Review homepage copyIn progress
Prepare the launch checklistNext up
Launch briefLinked to this project

You set the direction

“Read the launch brief and propose a clearer description for the homepage review task.”
Read and propose access

The agent proposes a task update

Review homepage copy

Check that the headline, next steps, and connection guidance match the launch brief.

Reviewed and approved by youAgent proposal and approval recorded in project history
Illustrative handoff: an agent proposes a task update, and a person reviews it before saving.

Start with the bigger picture.

A useful project has more than a title. Keep its goal, constraints, decisions, and next actions together so a collaborator or connected agent can understand what you are trying to do.

  • Organize projects and tasks with statuses and relationships.
  • See work in a list or board, and follow revision history.
  • Add comments and corrections while preserving the original entries and author attribution.
  • Keep separate workspaces for different groups of people.

Make room for the work that repeats.

Set up recurring tasks with a timezone, selected weekdays, and a time. Pause a schedule when plans change, and keep each occurrence’s completion history separate.

How recurring tasks and reminders work

Reminders go to the schedule owner’s verified email. Scheduled work is processed in the background; it does not wake an external AI agent or send a message into its chat.

Keep the source within reach.

Keep briefs, notes, links, and files attached to the work they support.

Attach the launch brief to your project and the task that needs it. Update the brief in Resources; record decisions in comments.

How resources and connected files work

Use comments for project and task updates, decisions, and history. Write editable library notes for briefs, plans, and reusable references. Keep original attachments and exports as files.

Track a useful link once and attach it to multiple projects or tasks. Keep personal and work accounts distinct, and use explicit sender or thread rules to find related records already tracked in the workspace.

Create plain-text Google Docs, export supported files to PDF, and track chosen Drive files.

Archiving a resource in MCPBinder and moving its original file to Google trash are separate actions. Your workspace should make that distinction clear.

Explore Google Drive

Let agents work with the same context.

Compatible clients connect through a remote MCP endpoint. You choose the workspace, allowed projects, connected accounts, and actions. Agents use the same checked services as the web app.

Choose read and propose permissions when you want a person to review suggestions. Direct editing permissions allow direct changes; review is not automatically required for every action.

A real Claude chat showing the MCPBinder task list for the Website launch project.

Understand agent permissions

Give your work
a place to belong.

Start free with your own workspace. Invite people and connect your agents when you’re ready.

Start free