Cursor
Desktop editor
Open Cursor's Customize page and manage its MCP servers. Add a remote server called morawp using https://api.morawp.com/mcp, then authenticate when prompted.
For file-based setup, merge this into .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects:
{"mcpServers":{"morawp":{"url":"https://api.morawp.com/mcp"}}}
Keep existing servers in the file. No command, environment variable, or static bearer token is needed for MoraWP.
Use the connected server
Open an Agent conversation and check that MoraWP is enabled in the available tools. Review Cursor's tool-call confirmation before allowing a change. Editor approval and MoraWP's website/Ability policy both apply.
Web and remote sessions
Cursor supports other Agent surfaces, but a local editor configuration does not establish that a hosted Agent has the same server and OAuth session. Configure and authenticate the environment that actually runs the task.
If it does not work
Check whether you edited the project or global configuration, and whether your organization's policy allows this MCP server. Reconnect through the displayed authentication control if its credentials expired.
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.