Website: https://www.watolabs.com

TL;DR: Wato is a shared AI workspace for teams. It helps companies keep their AI workflows, company knowledge, integrations, agent sessions, and agent-generated work inside the organization instead of scattered across individual chats, local files, or personal AI accounts. All of this is done via one, unified MCP.

Ask: If your team is using AI agents for engineering, ops, sales, research, finance, support, or internal workflows, we’d love to see how we can help. We’re especially interested in teams setting up MCP/tools, sharing prompts or workflows internally, launching cloud agents, or trying to preserve useful agent context across the company.

The problem: Teams are already using AI for real company workflows: debugging production issues, preparing sales calls, analyzing customer data, updating models, drafting client deliverables, and searching across internal systems.

But the work usually disappears into individual tools and accounts. The context, prompts, decisions, files, and tool setups that made the output useful are hard for the next teammate to find, trust, or reuse.

What Wato does: Wato gives each team a shared, permissioned AI workspace.

Teams can connect approved integrations and MCP tools, build shared memory, publish reusable skills, run collaborative cloud agent sessions, host live artifacts and dashboards, and trace tool calls across the organization.

The goal is simple: when one person or agent learns something useful, builds a workflow, or creates an artifact, that knowledge should stay with the company and become available to the right people.

What’s included:

- Team memory for durable company knowledge agents can reuse

- Approved MCP tools and integrations with org, team, per-user, and tool-level permissions

- Reusable skills and workflows library so teams don’t prompt from scratch every time

- Cloud agent sessions that teammates can view, continue, and collaborate on, with access to a desktop, computer use, filesystem, and environment set up.

- Automations that can be created from connector triggers or run on a specific cadence.

- Live artifacts and dashboards that can use approved company data

- Tool-call tracing and audit logs so teams can see what agents accessed and produced

Wato also works with the AI tools teams already use, including Codex, Claude Desktop, Cursor, Claude Code, and other MCP-compatible environments. You add the Wato MCP once, authenticate with your company account, and your agent gets access to the right team memory, skills, and approved tools.

Backstory: We started working on Wato after seeing the same problem across institutions adopting these tools like Claude or Codex. A super user would figure out a great workflow, debugging process, research method, client-prep flow, or tool setup, but the useful part would end up stuck in a chat thread, local file, or personal account. Then the next person would start over.

At the same time, companies didn’t want every employee independently managing MCP configs, tool permissions, prompts, and scattered agent instructions. They needed a shared layer between the company and the AI tools its people use to normalize AI use.

That became Wato.

We’d love to talk to teams who are:

- using agents across engineering, ops, sales, research, finance, support, or internal workflows

- setting up MCP servers or internal tools for agent use

- trying to share prompts, skills, playbooks, or workflows across a team

- creating AI-generated dashboards, docs, reports, or artifacts that need to be shared securely

- worried about company knowledge disappearing into personal AI accounts

- thinking about permissions, review, tracing, or governance for agent work

If this sounds familiar, and I’m guessing it does for a lot of you, we’d love to show you Wato and get feedback.

Website: https://www.watolabs.com

Twitter/X: https://www.x.com/watolabs