Skip to content
Hussh
Connect MCP

Agents agreeing on a time β€” the most-asked use case

How 🀫 Private Agent One settles a meeting time across several people by having agents negotiate over MCP, without anyone handing over their calendar.

Concept

TL;DR: Instead of one person publishing their calendar and everyone else replying, each person's agent negotiates with the others over MCP and returns a time that suits all of them β€” revealing only free or not free, never what the meeting is.

Status as of 2026-07-28: see body.

The problem, stated properly

Getting six people into a room is not hard because calendars are hard. It is hard because it takes eleven messages, and one person always answers last.

Why the usual fix is not a fix

The standard answer is a scheduling link: hand somebody your calendar, let them pick a slot. That solves the problem for exactly one person β€” the one who sent the link.

Everyone else still has to open it, compare it against their own week, and reply. And the sender has published their entire week to whoever holds the link. The work did not disappear; it moved downstream and multiplied by the number of participants.

Scheduling links also degrade badly past two people. With five participants you are back to messages.

What should happen instead

Each person has their own agent. The agents talk to each other.

  1. Your agent knows what you are free for, because it is your agent running on your machine with your calendar.
  2. It asks the other agents the only question that matters β€” is this window free β€” and answers the same question in return.
  3. What crosses the wire is free or not free. Never what the meeting is, never who it is with, never the title, never the location.
  4. The agents converge on the times that suit everybody and come back with one.

Nobody sent a message. Nobody published their week to anyone. The work happened on the side of the line where it belongs β€” with the agents, not the humans.

Why this is the mission in miniature

It is the clearest example of what "interposed, not a destination" means. A scheduling link is a destination: somewhere you go and operate. An agent negotiating on your behalf is delegation β€” it does the work for you, from your side.

It also shows the disclosure rule doing real work. An agent that answers "free or not free" reveals nothing about the person; a calendar link reveals everything. Same outcome for the participants, a categorically different amount of exposure.

Open by design

Calendars are shared agent-to-agent over MCP, an open standard anyone can implement.

That matters for two reasons. It works with the calendar someone already uses rather than requiring a migration. And it works with other companies' agents β€” the person on the other end does not have to use ours for this to work. A scheduling protocol that only functions inside one vendor's product has rebuilt the problem it claims to solve.

Status

Being built. This page describes the design, not a shipped feature β€” and the distinction is kept deliberately visible on the public roadmap rather than blurred.

Sources