Qwen Code

CLI setup

Run in the environment where you use Qwen Code:

qwen mcp add --transport http morawp https://api.morawp.com/mcp

Qwen Code saves user configuration by default; check the add command's scope options if you intend a project-only server.

For manual configuration, merge this into the applicable .qwen/settings.json:

{"mcpServers":{"morawp":{"httpUrl":"https://api.morawp.com/mcp"}}}

Use httpUrl for Streamable HTTP. Qwen's url setting is for the legacy SSE transport.

Authorize in the terminal interface

Start Qwen Code, open /mcp, and use its authentication control for MoraWP. Complete browser OAuth, then inspect the server's status and available tools.

IDE use

If you launch Qwen Code from an IDE, check the working directory and machine used by that session. Use the same Qwen server manager there to verify the server. An IDE's own generic MCP settings are not automatically Qwen's settings.

If it does not work

Check for an HTTP/SSE field mix-up first. If OAuth is still required, start a fresh authorization from the active Qwen session. A server listed in another project's configuration does not establish access here.

Disconnect its Agent in MoraWP and remove the local server entry when access should end.

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

Qwen Code MCP setup · Qwen remote transport and authentication

Vendor instructions reviewed October 9, 2026. Client interfaces and account policies may change.