What is MCP?
Understand Model Context Protocol and connect Wyatt to Codex, Claude Code, Cursor, OpenClaw, or another client.
Model Context Protocol (MCP) is an open standard that lets an AI application discover and call tools from another service. Wyatt acts as an MCP server; your agent or editor acts as the MCP client.
Instead of copying workspace content into a chat, the client can ask Wyatt to search, read documents, manage tasks, inspect workspace context, and use other approved tools when they are relevant to your request.
When to Use MCP
Use MCP when you want an AI agent to:
- choose the appropriate Wyatt tool from a natural-language request;
- combine several Wyatt actions into one workflow;
- work with current workspace content without copying it into the prompt; or
- use Wyatt alongside tools from other connected systems.
The Wyatt CLI is not currently distributed publicly. Use MCP for supported external agent access today.
Endpoint and Requirements
Connect an OAuth-capable remote MCP client to:
https://www.wyattworks.ai/api/mcp-server
The client must support remote Streamable HTTP and MCP OAuth. Wyatt discovers authorization dynamically, so you do not create or paste a static bearer token or API key.
Configure a Client
Codex
Claude Code
Run /mcp inside Claude Code to authorize or inspect the connection.
Cursor
Add the following to ~/.cursor/mcp.json globally or .cursor/mcp.json in one
project:
Then open Cursor Settings > Tools & MCP, enable Wyatt, and complete OAuth. Cursor Agent users can verify the connection with:
OpenClaw
Save Wyatt as an OAuth-enabled Streamable HTTP server, authorize it, and probe the live tool list:
OpenClaw may print an authorization URL and ask you to finish with
openclaw mcp login wyatt --code <code> after approval.
Equivalent OpenClaw configuration:
ChatGPT
In ChatGPT, enable developer mode under Settings > Apps > Advanced settings,
then choose Apps > Create. Name the app Wyatt, enter the endpoint above,
select OAuth, scan the tools, and complete sign-in. Workspace administrators
control whether custom apps can be created or published.
Other MCP Clients
Choose Streamable HTTP or Remote HTTP, enter the Wyatt endpoint, and start the connection. The client should discover OAuth metadata and open the approval flow. A client that requires a pasted API key cannot use Wyatt's interactive MCP authorization.
Authorization and Safety
During OAuth approval, choose read-only or full access and the workspaces the client may reach. Each tool call remains limited to that grant and current workspace membership.
An inactive MCP refresh grant expires after seven days. Reconnect the client when its grant expires. Remove or log out the Wyatt server in your MCP client to clear its stored authorization.
Verify the Connection
Ask the client:
If authorization succeeds but no workspace appears, confirm that you approved at least one workspace and still belong to it.