
Team0 Chief of Staff
io.github.ybentov1Published by GitHub account ybentov1v1.0.0Updated Oct 24, 2026
Your Team0 AI Chief of Staff, reachable from any agent — answers, acts, and coordinates.
The publisher's own server: Team0 Living Understanding
Overview
Connects an assistant to a Team0 AI Chief of Staff that answers questions, takes actions, and coordinates work on your behalf.
- What you can do
- This remote MCP server exposes a Team0 AI Chief of Staff to any connected agent. According to its registry description, it answers, acts, and coordinates, so an assistant can route requests to it for responses and for carrying out or coordinating tasks. The manifest lists no individual tools, so the specific operations available are not documented here.
- When to use it
- Relevant if you already use Team0 and want an assistant to reach your Chief of Staff from other agents. It suits coordinating and delegating work rather than local file, code, or database operations. Skip it if you do not have a Team0 account or do not want a hosted assistant acting on your behalf.
- Requirements
- A remote MCP endpoint at over streamable HTTP. Authentication is required via OAuth, with a bearer credential passed in the Authorization header; the key is created in Team0 under Settings > Agents. No packages, environment variables, or local runtime are declared. Network access to the provider's endpoint is needed.
Installation
In SourceWeft
- Open Team0 Chief of Staff in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ybentov1%2Fchief-of-staff/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"team0-chief-of-staff": {
"type": "http",
"url": "https://api.team0.ai/mcp/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
