MCP implementation to read / write across Google Workspace (and other spaces)

also clickup has one: (https://mcp.clickup.com/mcp). I’d really like to stay with akiflow because I like the interface and tools so much more.

+1 on this — and to answer @Tadej J.'s question about scope beyond Google: absolutely yes.

I'm building an AI agent orchestration system where autonomous agents manage my calendar, tasks, daily briefings, and household coordination. Right now I have 7+ agents that handle things like:

• Grooming my Google Calendar (analyzing conflicts, suggesting changes)

• Sorting undated tasks into time buckets using neuroscience-backed prioritization

• Syncing a shared Google Doc with household staff and having agents append updates to specific tabs

• Generating a daily briefing from calendar + tasks + personal goals

The gap: my agents can't talk to Akiflow. I've had to bolt on Todoist as a workaround — it has an API my agents can write to, and I sync it to Akiflow for scheduling. But this creates constant friction: projects don't align, status changes don't propagate, and I'm maintaining a redundant tool just because Akiflow lacks programmatic access. An Akiflow MCP server would let me drop Todoist entirely and have my agents read/write directly where I actually plan my day.

This directly supports what Johannes described as the "autonomous aggregator" vision. My agents already do the activity scraping he's asking for — they parse calendars, emails, and documents and generate proposed actions. What's missing is the last mile: writing those proposals back into Akiflow.

Specifically, an MCP implementation would need:

• Read tasks/events — so agents can see what's already scheduled and avoid duplicates

• Create tasks with project assignment, labels, and due dates — so agents can propose new work

• Update task status — so when an agent completes something (or detects completion in another tool), Akiflow reflects it instantly

• Read/write labels and projects — so agents can categorize and organize, not just dump into inbox

To Tadej's second question: for me it's not about chatting with a bot — it's about agents autonomously keeping my task board accurate. Johannes's Triage Wizard concept is exactly right: agents propose, I approve/snooze/discard. The MCP is the plumbing that makes that possible.

Right now I'm paying for and maintaining a whole extra tool just to bridge the gap. An MCP would make Akiflow the single control plane for AI-assisted productivity. Happy to share more about how this works in practice if helpful.

Hi Johannes,

Thank you for sharing such a thoughtful and detailed use case! You’ve clearly put a lot of thought into how Aki could become a true central hub for productivity across Google Workspace.

I can see how native read/write capabilities for Gmail, Drive, and Meet would unlock a whole new level of functionality — from email triage and document synthesis to meeting continuity — and how this would save users from constantly switching between apps.

I’ve shared your feedback with our product team so they’re aware of the value and impact this kind of integration could bring. We really appreciate you taking the time to outline these specific scenarios; it helps us understand exactly what power users like you need from Akiflow AI.

Hi @Johannes Staufenberg.

Thank you for your feature request.

I’d love to dig a little deeper into the problem to ensure we approach this the right way.

You mentioned Email triage, Doc synthesis, and Meeting continuity as your key use cases.

1. Are these the main three pain points you face, or do you envision connecting other non-Google tools (e.g. Notion, Linear) via MCP as well?

2. If Akiflow could automatically handle the Meeting continuity (transcripts, summaries & action items) and Email triage natively without you needing to chat with a bot, would that solve your core need? Or is the ability to have a back-and-forth conversation with your data (via an AI chat) the critical part of the request?