AcrossAI

AcrossAI

Get Started

← All documentation

Documentation

Missing something? Ask support and we will write it up.

Connect Cursor: editor, Cloud agents, config file, and what to do when it fails

Three ways to add your WordPress site to Cursor — in the editor, in Cursor Cloud, or via mcp.json — plus the plan limit and failures people hit.

· · ·

Custom MCP connectors on Cursor require a paid plan — Pro, Pro+, Ultra, Teams or Enterprise. The free Hobby plan does not support MCP servers, skills or hooks. If the MCP options are missing entirely, that is almost always why.

There are three places to add the server: the Cursor editor, cursor.com/agents (Cloud / Background Agents), or a JSON config file.

You will find your MCP URL on MCP → your server → How would you like to connect? → Connectors/Integrations/Plugins → Cursor. It looks like https://example.com/wp-json/acrossai/mcp.

Cursor editor (in-app)

  1. Open Cursor and press ⌘/Ctrl + , to open Cursor Settings.
  2. In the sidebar go to Features → MCP, then click + Add New MCP Server.
  3. Fill the dialog: a Name, a Transport Type suitable for remote servers, and your MCP URL.
  4. Save. A green dot next to the server name means it connected. Cursor opens the browser OAuth flow — approve the consent screen on your WordPress site.

Cursor Cloud / Background Agents

  1. Sign in at cursor.com/agents with a paid account — free Hobby users will not see the MCP options.
  2. Open your Agent, or create one, then go to its MCP Servers section and click Add MCP Server.
  3. Fill in the Name, Transport and URL. Leave headers and auth empty — the OAuth handshake happens on first use.
  4. Save. The first task that uses the server triggers the consent screen on your WordPress site.

Teams can promote a server with Add to Team Marketplace, making it available to every teammate’s Agent, IDE and CLI at once.

JSON config file

  1. Open or create ~/.cursor/mcp.json for every project on your machine, or .cursor/mcp.json for the current project only.
  2. Merge the entry shown on the Cursor tab into the mcpServers block — or paste it whole if the file is empty.
  3. Save. Cursor picks up the new entry on the next window; if not, reload with ⌘/Ctrl + Shift + P → Reload Window.
  4. Open Cursor Settings → Features → MCP, click the row, and approve the consent screen.

Troubleshooting

There is no MCP section in Settings

The free Hobby plan does not include MCP. Upgrading to any paid tier reveals the options.

The dot next to the server stays red

Check the transport first — a remote server needs the HTTP transport, not a local command. Then check the URL loads in a browser. If you are on a local development site, Cursor Cloud agents run on Cursor’s infrastructure and cannot reach it; the desktop editor can, because it runs on your machine.

The editor works but a Cloud agent does not

That is the difference above. The editor connects from your machine; Cloud agents connect from Cursor’s servers and need a publicly reachable https:// address.

Edits to mcp.json do nothing

Cursor reads the file when a window opens. Reload the window, and check you edited the right file — ~/.cursor/mcp.json is global, .cursor/mcp.json applies to one project. Invalid JSON is ignored silently, so validate the file if nothing appears.

It connects, but there are no tools

Connecting and exposing are separate. Check the server’s Tools and Abilities tabs, and Access Control — a user who is not allowed on this server receives an access-denied response even with a valid connection.

Was this page helpful?

Yes
No

Previous

Next