Remote MCP
Connect OAuth-capable AI clients to Wyatt.
Wyatt — the AI workspace for team docs, tasks, and data — supports MCP in both directions: approved external agents can operate a Wyatt workspace, and Wyatt can use connected third-party MCP tools and data.

One connected workspace for docs, tasks, chat, and databases — with Wyatt answering from all of it.
Connect OAuth-capable AI clients to Wyatt.
Agents use Wyatt, and Wyatt uses connected tools.
Search, read, write, inspect tasks, and start agent runs.
Approve workspaces and read-only or full access.
Connect Codex, Claude, Cursor, ChatGPT, or another OAuth-capable remote MCP client to Wyatt. The client discovers tools for workspace overview, documents, search, tasks, incremental context, connection information, and background agent runs.

Wyatt discovers authorization dynamically and opens a browser approval flow. Users choose the workspaces a client may reach and select read-only or full access instead of copying a long-lived API key.

Wyatt can also consume third-party MCP servers as integrations. Those connections give Wyatt’s assistant access to approved external tools and data, which is the opposite direction from an external agent operating Wyatt.

The MCP quickstart contains client-specific commands and the canonical remote endpoint. Clients discover the current tool list from the server so integrations do not depend on an outdated copied catalog.

“Ask a question, get an answer grounded in your team's actual work — then turn it into action.”
Yes. OAuth-capable remote MCP clients can connect to Wyatt’s public MCP endpoint and use the tools a user approves.
No. Supported clients discover OAuth metadata and open a browser authorization flow.
Depending on scopes, it can inspect workspaces, search, work with documents and tasks, read incremental context, and start a background Wyatt agent run.
Yes. Wyatt can also consume third-party MCP servers so its assistant can use approved external tools and data.
Keep exploring Wyatt