We made a deliberate choice not to be a catch-all, do-anything MCP connector.
There are already tools for that. Claude has them. ChatGPT does too. Cursor, Grok, every serious agent ships with a growing ecosystem of integrations it can call. We don't want to recreate that ecosystem.
What we connect to is the hard part. The graph of your prior work, your customers' specific situations, the design decisions that got you here, the relationships between projects and people. That's what myai is. Plug it in via MCP and your agent of choice gets memory, judgment, and a working knowledge of how you work.
myai is the context. Your agent is the hands.
A real example: a Kinaxis rollout
A consulting firm in our customer base was rolling out Kinaxis Maestro for a manufacturing client. Anyone who has done a Kinaxis implementation knows the shape: a planning layer pulling from ERP, demand, and supply data; deep customer-by-customer nuance; stakeholders across S&OP, procurement, plant operations, and finance; tribal knowledge nobody has written down (we always expedite for customer X, lot-sizing exceptions, allocation logic). Full rollouts run twelve to twenty-four months. The user stories alone are a multi-week effort.
myai built the user stories. It already knew the relationships: the supply-chain platform context, prior projects in the customer's portfolio, the design decisions already made. It knew which stakeholder to ping when a story needed clarification, because the project-to-people relationships were already in the graph.
Each story came out grounded. Which prior project it drew from. Which design decision it implemented. Which stakeholder owned the underlying answer. When two stories conflicted because they pulled from different prior decisions, myai surfaced the conflict in the same draft.
The last mile was Claude Code. Manicured Excel templates the consultants had standardized on. Pixel-perfect requirements documents. The executive summary PowerPoint. Data flowed out of myai-via-MCP into Claude Code, which did what Claude Code is great at: shipped a polished artifact a consultant could put in front of a client.
myai didn't try to be Excel. myai didn't try to be PowerPoint. myai was the brain. The agent was the hands. That's the default.
We dogfood this every day
We use this internally, constantly. Our knowledge base lives in myai (what we call the "hive mind"). When Mark or I are debugging a piece of myai itself, writing content for the platform, or trying to remember what we decided three weeks ago and why, we connect to our own myai-via-MCP from any agent of choice. The agent gets our actual context. Eat your own cooking.
Concretely: when we're scoping the next dimension and need to know which artifacts already exist in that workstream. When a customer asks why we made a particular design decision and the answer is sitting in a work order from three months ago. When we're writing a blog post and want to know what we've already published on the topic so we don't repeat ourselves. The graph holds it. The agent retrieves it. We don't have to context-switch into a knowledge-base UI to go look.
The proof that it works is that we'd be slower without it.
Why we built it this way
Four points worth being explicit about:
-
Every serious agent already has (or will soon have) a long list of MCP integrations. We don't have to build that list, and you don't have to wait for us. If your team lives in Notion, Linear, Slack, GitHub, Snowflake, or any of the other things Claude or ChatGPT can already reach, the integration is already there.
-
What no agent has out of the box is you. Your prior work, your customers' specific situations, your team, the decisions that got the platform to its current state. Memory and judgment. A structured model of how you actually operate, which no connector ships with.
-
A context spine that any agent can plug into is more valuable than a closed agent that owns its own integrations. Specialization beats duplication. We get better at being the context layer; you get to keep the agent you already love.
-
The same myai instance is available to Claude on Monday, ChatGPT on Tuesday, and whatever wins the next round on Wednesday. Your context survives the agent churn. The model layer is going to keep moving fast. Your knowledge layer shouldn't have to move with it.
Try it
If you want myai-as-context plugged into the agent you already use, the endpoint pattern is https://api-[instance].makeyourself.ai/api/mcp (replace [instance] with your tenant subdomain). The Connect via MCP docs page walks through plugging it into Claude, ChatGPT, and Cursor in a few lines of config. The platform page covers what's in the graph.