Trae
Desktop IDE or Agent window
- Open Settings → MCP.
- In the Agent window, choose the runtime that will use MoraWP: Local or Cloud.
- Choose Add → Create Manually.
- Enter the following JSON and choose Confirm:
{"mcpServers":{"morawp":{"url":"https://api.morawp.com/mcp"}}}
TRAE's Raw Config (JSON) control can merge existing configuration. Project servers use .trae/mcp.json after enabling Project MCP.
Check authentication before use
If your installed version offers OAuth for the custom MoraWP server, complete that browser flow. If it only accepts a static token, use a client with documented remote OAuth, such as Codex or Claude. MoraWP does not issue static Agent keys.
Local and Cloud are separate
A server added to a Local runtime is for local/worktree tasks; a Cloud entry is for cloud tasks. Check the runtime used by the current conversation. Do not assume that configuration or authorization transfers between them.
If it does not work
Record the runtime and exact authentication error. Changing website permissions in MoraWP cannot add an unsupported OAuth flow to the client.
Approve and check access
First connect a WordPress website in MoraWP. When the client opens sign-in, review the Workspace, websites, and Ability access before approving. Read only limits changes; enabled Integrations may still expose private fields. No static Agent key is needed.
In a new session with MoraWP enabled, ask:
Use MoraWP to list the websites this connection can access.
Do not create, edit, delete, or publish anything.
Check: the intended website appears. Then read one page to check WordPress access. A configured server alone is not proof of a working read.
For missing tools, see Missing Abilities. To stop access, disconnect the Agent in MoraWP and remove its local server entry. Local removal alone is not MoraWP revocation.
Official references
Vendor instructions reviewed October 9, 2026. Client interfaces and account policies may change.