Connect Claude Code, Cursor, and Codex

Pick the clients you use

From your product repo, initialize only the relevant clients:

wayform init --remote --clients claude,cursor,codex

This creates project-scoped configuration, hooks, and the Wayform skills. Authenticate the MCP connection in each client and run wayform login once per machine for hooks.

Configuration files contain a gateway URL and project name. Credentials belong in the OAuth flow and OS credential store, not in your repository.

Claude Code

Setup writes the remote MCP server to the project’s .mcp.json and installs the supported hooks. Connect and sign in with GitHub in Claude Code. Where supported, you can start authentication from a terminal:

claude mcp login wayform

Open a new session after connecting. Start a build with:

wayform build 12 --client claude

Cursor

Setup writes .cursor/mcp.json. Connect the Wayform server in Cursor and complete GitHub sign-in. For the Cursor CLI:

agent mcp login wayform

Trust the project and approve its Wayform connection in Cursor when prompted. Build with:

wayform build 12 --client cursor

Codex

Setup writes .codex/config.toml for the project. Authenticate from a terminal in that repo:

codex mcp login wayform

Start a new Codex session after login. A session started before authentication may not load the server. Build with:

wayform build 12 --client codex

What the hooks do

Supported client hooks bring context into a session before the agent starts work. The guard checks supported mutating actions against the team’s recorded decisions.

If the guard finds a contradiction, it surfaces the decision for your confirmation. Only an explicit human confirmation should allow an exception. Hook availability and permission UX depend on the client.

Runtime hooks fail open on connection or service errors, so a broken connection doesn’t stop a coding session. That also means quiet operation isn’t proof that context is working. Run wayform doctor and verify the round-trip after setup.

Other MCP clients

The hosted server supports remote MCP over Streamable HTTP and OAuth. Other compatible clients can read and write through the MCP tools, but they don’t automatically gain the startup and guard hooks provided for supported coding clients.

Ask for your gateway URL during setup. The default hosted MCP endpoint is:

https://memorylayer-gateway.memory-layer.workers.dev/mcp

Use the desktop app alongside your editor

The app and your editor read the same remote plans and decisions. Planning chats use the agent selected in app Settings. Your agent still needs its own installation, authentication, and local project access.

The app does not host coding execution for you. The current released build path is through the CLI and your terminal.