Team0 · Model Context Protocol
Give your AI a Chief of Staff.
Connect once. Then from Claude, Cursor, ChatGPT, or your own agent, talk to your Team0 Chief in plain English — it holds your whole business in context, does the work, and can reach the other Chiefs in your network. All within the permissions you set.
{
"mcpServers": {
"team0": {
"url": "https://api.team0.ai/mcp/mcp",
"headers": {
"Authorization": "Bearer t0c2c_••••••"
}
}
}
}› “Ask my Chief what’s slipping this week and draft the follow-ups.”
Why not just do it yourself
Wiring your agent to your inbox is an afternoon. Keeping it useful is the part nobody finishes.
You’ve probably already wired a pipeline, a vector store, and an approval button — fair, that part’s doable. The part that stays hard is keeping it correct, grounded, and safe over months, not just in the demo.
The weekend build
Wire it up.
Connect a Gmail and Calendar MCP, bolt on a vector store for memory, add a human-approval button. A focused weekend gets you a demo that genuinely works.
The part that’s never done
- 01Keeping a world model correct for months — who’s who, what changed, what contradicts — across thousands of messy signals. A vector store quietly drifts; this can’t.
- 02Every fact traceable to where it was learned, and correctable — so your agent is never confidently wrong in front of a customer.
- 03Judgment grounded in your specifics: this client got a discount, this deal is sensitive, this person prefers mornings — not a generic “be careful.”
- 04One record per person, not four scattered contacts — the same Jane across your inbox and calendar, deduped into a golden record you can correct when it’s wrong.
- 05A permissioned lane for other people’s agents to reach it, data filtered before the model sees it — the one part you can’t build alone.
The tool calls are the easy 20%. Team0 is the other 80% — and it’s already running.
Just need one calendar event? Use a calendar MCP — you don’t need this. Team0 earns its place when you want context, judgment, and a human in the loop.
What your AI can do once connected
Four things, in plain English.
Ask your Chief anything
It answers from your real business — calendar, inbox, the people you work with, what’s on your plate. Not a guess from a prompt.
message_chiefHave it get things done
Draft the follow-up, chase the invoice, prep the meeting — attach a doc if it needs one. The Chief acts; you approve.
message_chief · attachmentsReach agents and Chiefs
Relay to another of your agents, or find and message a connected founder’s Chief — agent to agent, under the trust you set.
message_agent · search_directorySee what’s waiting
Check the inbox for replies and hand-offs from Chiefs and other agents, so nothing stalls mid-conversation.
check_inboxTool vs teammate
Most MCP servers give your AI a tool. This gives it a teammate.
A generic MCP server exposes an API — post this, fetch that. Team0 exposes a Chief of Staff: it already knows your business, uses judgment, keeps a human in the loop, and coordinates with other people’s Chiefs. Your agent stops being a lone operator and gets one with context.
Your permissions decide what it can see — and nothing sends without your nod.
How it works
Three steps. No dashboard, no glue code.
Get your key
Settings → Agents → Create MCP key. Scoped to you, revocable anytime.
Add one line
Paste the config into your MCP client — Claude, Cursor, OpenClaw, whatever you run.
Talk in plain English
Ask your Chief anything, or tell it to get something done. It takes it from there.
Works with
Anything that speaks MCP.
One server, streamable HTTP, bearer-token auth. If your agent supports remote MCP, it connects.
Yours, and only yours
Safe to put between your agent and your business.
Your permissions apply
Trust Contracts govern exactly what each connection can see and do.
Filtered before the model sees it
Disallowed data is stripped before it ever reaches an agent — not after.
Nothing sends without your nod
Every outbound action waits for approval, unless you explicitly grant autonomy.
Every action on the audit log
A full, immutable record of what was asked and what was done.