UpMyB

AI chief of staff, built on MCP

One assistant that reads your mail, calendar and notes and does the routine work. For: Founders, consultants and busy teams.

The problem

Founders spend hours on email, scheduling and follow-ups. Each app has its own place to look, and nothing talks to the others.

How it works

Built from: mcp, gmail, gcalendar, notion, claude.

flowchart LR
  C(["Your customer"]) <-->|"asks, pays, gets updates"| APP["Your app<br/>Assistant app: ask in plain words, see what it did"]
  APP --> L{{"Your logic<br/>the rules that are yours"}}
  subgraph EX["Apps that already exist: APIs and MCP servers"]
    A0["MCP servers<br/>The standard way the assistant uses each app as a tool"]
    A1["Gmail<br/>Reads and drafts email"]
    A2["Google Calendar<br/>Finds time and books meetings"]
    A3["Notion<br/>Notes, tasks and project context"]
    A4["Claude (AI)<br/>Understands the request and decides which tool to use"]
  end
  L --> A0
  L --> A1
  L --> A2
  L --> A3
  L --> A4
  L --> DB[("What it keeps<br/>Your connected apps, Action log, Approval rules")]
  L --> OWN["Admin dashboard<br/>Permissions: what it may do alone and what needs approval"]
  classDef yours fill:#1691D6,stroke:#0a5f95,color:#fff
  classDef ext fill:#E6F3FB,stroke:#1691D6,color:#12112E
  class APP,L,DB,OWN yours
  class A0,A1,A2,A3,A4 ext

The logic

  1. When you ask for something: Work out which apps are needed and plan the steps
  2. When the plan involves sending or deleting: Show it to you and wait for approval
  3. When approved: Do it through the app's MCP server and log the action
  4. When each morning: Summarise the day: meetings, mail needing a reply, tasks due
  5. When something fails: Stop, explain what happened and ask what to do
flowchart LR
  subgraph R0["Rule 1"]
    direction TB
    W0{{"When: You ask for something"}} --> T0["Then: Work out which apps are needed and plan the steps"]
  end
  subgraph R1["Rule 2"]
    direction TB
    W1{{"When: The plan involves sending or deleting"}} --> T1["Then: Show it to you and wait for approval"]
  end
  subgraph R2["Rule 3"]
    direction TB
    W2{{"When: Approved"}} --> T2["Then: Do it through the app's MCP server and log the action"]
  end
  subgraph R3["Rule 4"]
    direction TB
    W3{{"When: Each morning"}} --> T3["Then: Summarise the day: meetings, mail needing a reply, tasks due"]
  end
  subgraph R4["Rule 5"]
    direction TB
    W4{{"When: Something fails"}} --> T4["Then: Stop, explain what happened and ask what to do"]
  end
  S(["Start"]) --> R0 --> R1 --> R2 --> R3 --> R4 --> E(["Done and logged"])
  classDef when fill:#E6F3FB,stroke:#1691D6,color:#12112E
  classDef then fill:#1691D6,stroke:#0a5f95,color:#fff
  classDef end1 fill:#12112E,stroke:#12112E,color:#fff
  class W0,W1,W2,W3,W4 when
  class T0,T1,T2,T3,T4 then
  class S,E end1

What can be developed

The money (illustrative example)

The customer pays ₹999 per user, per month. API and hosting costs: AI usage ₹450, Hosting ₹80, together ₹530. Net profit ₹469.

sankey-beta
Customer pays,AI usage,450
Customer pays,Hosting,80
Customer pays,Net profit,469

Watch out for

Build this for me