About DOT: Digital Chief of Staff

A personal AI agent for the everyday admin overhead.

DOT: Digital Chief of Staff (referred to throughout this page as “DOT”) is a personal AI agent that takes routine administrative work off your plate. It drafts emails, creates calendar entries, produces documents, sends reminders, and handles the booking and follow-up correspondence around recurring appointments — by integrating with the apps and tools you already use.

The product is designed for one user at a time: a single person delegating their own everyday tasks to an agent operating on their own connected accounts. It is not a multi-tenant SaaS, not a data-aggregation product, and not a marketing tool.

What DOT actually does

A few examples of the work DOT is built to take off your week:

• Sending the weekly status email to your team, with progress pulled from your calendar and project documents.
• Drafting a proposal in Drive from a template you provided and emailing it to the client.
• Finding a calendar slot for a recurring meeting and scheduling it with the right invitees, location, and video link.
• Booking the next quarterly dentist or physio appointment by email, watching for the confirmation, and adding the confirmed date to your calendar.
• Pulling Strava activity data each Sunday and emailing a training summary to your coach.
• Generating a weekly health and recovery digest as a new Drive document for your records.

In each case the agent reads the necessary context from your connected services, drafts the artefact, and either delivers it on your behalf or queues it for your one-tap approval.

How DOT works

DOT pairs a current language model with a set of skills. Each skill is backed by a small server that speaks the Model Context Protocol (MCP) — an open protocol for connecting AI agents to real-world tools and services. The Workspace MCP server gives the agent the ability to read and create Gmail messages, Calendar events, and Drive documents. Equivalent servers cover Strava activity data, health and fitness platforms, and additional services added over time.

This architecture bounds what the agent can do per connection. Each MCP server is isolated; data fetched through the Workspace server is never visible to the Strava server. Each server requests only the OAuth scopes its declared operations require — calendar read for “find me a slot”, calendar write for “schedule it”. There is no superset of permissions held “just in case”.

The agent also defaults to drafting rather than sending. For any action with external visibility — email, calendar invites to other people, document shares — the default behaviour is to produce the artefact and queue it for your review. Autonomous send is opt-in per workflow.

Why DOT exists

DOT began as a personal experiment to find out how much weekly admin work could be safely delegated to a language model with the right tool access. It became clear quickly that the limit was not the model — modern language models are easily capable of drafting a competent status update, a coherent proposal, or a sensible meeting agenda. The limit was integration.

A chatbot can write a perfect message but cannot send it. It can describe an ideal calendar entry but cannot create it. It can describe the right document but cannot put it in Drive. The Model Context Protocol closes that gap, and DOT is the result of pairing it with a single user's everyday workflow. The subdomain this site is hosted on — mcp.hyani.net — reflects that origin: DOT was built on, and around, MCP.

Operating principles

• Acts only when asked. The agent does not initiate work unprompted. Every action is traceable to an explicit one-off instruction or a recurring rule that you set up.
• Drafts first, sends second. External-visibility actions are queued for your review by default. Autonomous send is opt-in per workflow.
• Minimum scopes. Each integration asks for the narrowest OAuth scopes that perform its declared operations.
• Server isolation. Each MCP server runs in its own process boundary with access only to the credentials and scopes for its own service.
• No retention of substantive data. Content fetched from connected services is processed transiently and not stored beyond what is required to return the response to you.
• You stay in control. Every connected service can be disconnected from its own native settings page at any time. Revocation is immediate.

Status and availability

DOT is currently operated as a personal-use application by its developer. It is not distributed as a public SaaS or a downloadable product. Access is granted per user account through the standard OAuth consent flow of each connected service. The website at mcp.hyani.net hosts the product page, this About page, the Privacy Policy, and Terms & Conditions. The application itself is a desktop tool that runs on the user's own machine.

Data handling, in one sentence

DOT: Digital Chief of Staff's use and transfer to any other application of information received from Google APIs adheres to Google's API Services User Data Policy, including the Limited Use requirements. The Privacy Policy sets out the detail.

Contact

DOT is operated by an individual developer. Questions, feedback, or data requests can be sent to: roryhw [at] gmail [dot] com.