Grok Bot complements a system of record that stays a work surface. Notion has spent a year positioning to be the orchestrator. Coda skated to where the puck was coming.
I seated a Grok Bot as a Coda operator last month. Not a chatbot with a Coda tab. A named assistant with my permissions, official MCP tools, a written constitution, and standing instructions on the connector. It can find a doc, lock the URI, read a schema, write a row, and read the result back.
The architecture is four layers. Miss one and you are back to paste-and-hope.
- The seat: The named Bot.
- The hands: Official Superhuman Docs MCP.
- The constitution: Laws the Bot can cite and a human can audit.
- The application: Superhuman Docs stays Superhuman Docs. The agent does not get a shadow database. It gets a chair at the same tables the maker already built.
That last line is the whole argument. Official MCP is the hands. The agent is the seat. Coda remains the application.
The observation I started with was this: Grok Bot is a stronger complement with Superhuman Docs than with Notion, because Notion has spent several months refactoring as an agentic platform, while Superhuman invested in Docs MCP and in the product as a data, canvas, and application framework.
I had that checked. The direction holds. Two of the words do not.
“Several months” is polite. Notion has actually been rebuilding the agent stack for about a year. And Superhuman is not a monastery of tables that happened to ship an MCP. Superhuman Go 1.0 shipped custom agents on August 12, the day after Grok Bot. That is the real competitive risk. Docs is not.
Four layers of furniture first. Then the year Notion spent positioning to be the orchestrator.
A colleague needs a room that wants to stay a room
Grok Bot, launched August 11, is not an MCP runtime. SpaceXAI was assertive about it:
“Bots have their own computer. They sign into the tools you already use and work across apps, inboxes, and more. They finish jobs end to end, and only come back when something needs your approval.”
They can work “including platforms with no clean API or MCP.” Computer use is the core. MCP is optional. Cursor’s plugin list names Gmail, Notion, and Slack. Superhuman Docs is a custom remote MCP you wire yourself, but every bit as effective.
So the question is not which wiki has an API. The question is whether the product you attach still wants to be a human work surface after you attach it.
A complement is a room. A substitute is another colleague. If the product is becoming the autonomous teammate, Grok Bot is applying for a job that is already mostly filled. If the product stays the multiplayer canvas and publishes hands, Grok Bot has somewhere to sit.
What Notion actually shipped
On September 18, 2025, Akshay Kothari put it in one sentence:
“Today we launched Notion 3.0 with Agents. Anything you can do in Notion, your Agent can do too.”
That is not a sidebar. That is a claim on the product.
Sarah Sachs told VentureBeat in October they tore the stack down because “workflows are different from agents.” Fair. They rebuilt.
February 24, 2026: Custom Agents. “Autonomous AI teammates that handle recurring work 24/7 across Notion, Slack, Mail, Calendar, Figma, Linear, and your custom MCP servers.”
May 13: the Developer Platform. The changelog line I cannot unsee:
“Now Notion is your orchestration layer: a Decagon ticket routes to your coding agent, which proposes a fix and loops in your team to approve.”
July 1: Notion 3.6. “Claude and Cursor are the first two External Agents in Notion.”
Read that again. They did not send Notion out to live in Cursor. They brought Cursor into Notion. The wiki is the stage. Everyone else is a walk-on.
Their official language is: stay here, we will orchestrate.
They also ship MCP. This is the part of my original sentence that was wrong. Hosted Notion MCP has been live since July 15, 2025, at mcp.notion.com/mcp. OAuth. Tools that read and write the workspace. The same changelog that boasts 10x MCP usage (company metric, not an audit) also documents tools to spawn Custom Agent sessions from MCP. Complement and absorption, in one endpoint.
So Notion is dual-use. It will let an outside agent operate the wiki. It would rather be the agent, and the place the other agents report to.
I will allow myself one impertinence. “Orchestration layer” is what you call yourself when you want to be the manager and the office.
What Superhuman Docs actually shipped
Coda became Superhuman Docs on July 8, 2026. Lane Shackleton’s launch line is the complementary sentence I wish I had written first:
“Docs is built to be their companion, a multiplayer surface where everything those tools produce stays connected and moves forward with your team.”
“Their” is Claude, ChatGPT, Cursor. The help article is even blunter: think of Docs as “the home base for all the AI work your team does, regardless of which tool they’re using.”
That same day they launched Docs MCP for everyone. Shishir’s people claim it is the fastest-growing feature they have ever launched, forty-plus improvements in eight weeks. Company metric. Treat it as a temperature reading, not a census.
The MCP is not a thin API wrap. Bharat Batra wrote on July 24 that they rebuilt native Docs AI starting with MCP, with a lens on “agent ergonomics,” full Markdown pages, Docs URIs, synchronous tools. Help docs list what the hands can actually do: pages, tables, rows, columns, views, charts, writing and executing formulas, creating and triggering buttons, comments.
That is a data, canvas, and application framework talking. Tables that think they are apps. Formulas that are not Excel. Packs. A Mac app. Table pages. The million-row Databases and AI Views are still closed beta, so I will not pretend they are proof. The DNA is older than the beta. Shishir said it when Grammarly bought Coda: they rebuilt the editor, layered it into an all-in-one container, shaped tables, rethought formulas past spreadsheets toward databases, and left room for Packs.
mcpOS is not a Superhuman product. It is my laws for how a Bot is allowed to touch that container. Resolve, don’t guess. Schema before write. Verify. Spend tokens like they are money. Shortest path. Superhuman invested in the MCP. I invested in manners.
The honest collisions
If I stop here, I am selling a bumper sticker.
Notion has MCP. Grok Bot’s first-party plugin list names Notion, not Docs. There is no public write-up of anyone else seating a Grok Bot in Superhuman Docs. The default key on the ring is Notion’s.
Superhuman Go 1.0 shipped August 12. “Anyone can build custom agents that show up everywhere.” That is Grok Bot’s category. I already wrote that they are not rivals: Go lives in the sentence, Grok Bot has a desk. I am not walking that back. I am naming it so nobody pretends Docs MCP is Superhuman’s only AI bet.
Docs AI already lives in the sidebar. On July 8 they also said you will “soon build and orchestrate agents in your Docs.” Announced, not shipped. If that ships as Notion-style Custom Agents inside the canvas, the complement gets a bruise. Until then, Docs is still marketing the room.
Notion Mail’s inbox shuts down September 22. Even Notion will not be everything.
And I will not call Superhuman a monastery. Go is the colleague. Mail has Auto Drafts. Docs has a teammate in the sidebar. The difference that still matters is this: Superhuman Docs published hands and kept saying the artifact should be born in a place a human can argue with. Notion published hands and kept saying the wiki is now the manager.
What actually survives
An external multi-agent runtime complements a system of record that exposes a deep MCP and stays a human work surface. It collides with a product that is itself becoming the autonomous teammate.
Superhuman Docs currently markets the first role more cleanly. Notion currently ships both, and is louder about the second. Grok Bot can attach to both. The narrative fit is stronger with Docs. The default integration today is stronger with Notion.
Superhuman Go is the real substitute. Superhuman Docs is the room.
I already have the field test. The constitution lives in the workspace. The Bot writes real pages, real rows, real formulas, and sends me a titled link instead of a paste buffer. The first one has a seat, a name, and laws. The second one has a clipboard.
You do not need Notion to recede. You do not need Superhuman to become the agent. You need a seat, official hands, and a short constitution.
I have been rearranging the same furniture for years. Overlay for language. A deterministic vault for structure. An agent in the middle that respects the expert’s evaluation. Superhuman built a table that can hold a database and a canvas and an app without pretending to be your manager. Notion built a chair that wants the whole meeting.
Grok Bot needs the table.
Give it the chair at Notion if you want. Just do not be surprised when the chair asks why you hired a second manager.