Docs · Connect your tools

Set up Echo in Cursor

Cursor connects to Echo as an MCP server. Its agent then reads your Echo data and, with the Design website right, changes your website's code, all on your Cursor subscription. Cursor has no key of its own to bring into Echo: for that, see the end of this page.

Use Echo inside Cursor

The address is:

https://echo-aeo.com/mcp
  1. Required. In Cursor, open the MCP settings (Cursor Settings → Tools & MCP, called MCP in older versions) and add a new MCP server with the address above. Or add it to the file ~/.cursor/mcp.json (for every project) or .cursor/mcp.json (for one project):
{ "mcpServers": { "echo": { "url": "https://echo-aeo.com/mcp" } } }
  1. Required. Cursor opens Echo in your browser: sign in the way you always do (Google or an email link).
  2. Required. On Echo's page, pick the right workspace in the Workspace list, or All my workspaces if you manage several, then click Allow. The list only shows when you're in more than one workspace.
  3. Required. Back in Cursor, Echo shows as connected with its tools. Ask the agent, for example: "Which pages should we fix first for AI answers?"
  4. Optional. On a Cursor team with an MCP allowlist, an admin adds https://echo-aeo.com/mcp in Team Settings → MCP Configuration first.

One workspace or all of them

When you're in more than one Echo workspace, Echo's page asks which Workspace the app may read:

  • Pick one workspace to keep the connection to that one.
  • Pick All my workspaces (the last item) if you manage several. Cursor can then work in each of them: name the company or workspace in your question, and it says which workspace it used. The workspace open in Echo is the default.

To change it later, disconnect and connect again:

  1. In Echo, open Settings → Connections → Claude and ChatGPT and click Disconnect next to your Cursor connection.
  2. In Cursor, ask the agent something about Echo, or switch the Echo server off and on in the MCP settings: Cursor asks you to sign in again.
  3. On Echo's page, pick the other workspace or All my workspaces, and click Allow.

Change and publish your website

On a site on the Allsite CMS, ask Cursor for the change in plain words ("make the hero button orange"). It changes the text or the code and then asks once whether to publish: staging and live, staging only, or not yet (just "publish now?" when your site has one link). Say yes and reload your site a minute or two later; you never have to open Echo. To skip the question, say it up front: "… and publish it right away". Publishing needs the Publish website right. See Website changes.

Let Cursor open your website

Cursor's agent opens public web pages with its web tools, and there's no list of allowed domains to set for one person. Reading your Echo data through the connector needs no web access at all.

  1. Optional. If the agent doesn't open your site, give it the full address (for example https://yourbrand.com/pricing) and ask it to fetch the page.
  2. Optional. On a Cursor team where an admin limits network access, ask them to allow echo-aeo.com and your website's domain.

Your own AI key in Echo

Cursor has no API key that Echo can use. Echo takes two kinds of key, both in Settings → AI (workspace owner only):

You don't need either to use Echo in Cursor: the connector does the AI work on your Cursor subscription and uses no Echo credits.

If something doesn't work

  • Echo shows as disconnected in Cursor. Switch the Echo server off and on in the MCP settings, and sign in again.
  • Cursor reads the wrong workspace. Disconnect in Echo and sign in again, and pick the other workspace (see above).
  • Changing your site's code doesn't work. It needs a site on the Allsite CMS and the Design website right. See Website changes at once.

What Cursor reads and can propose: Claude, ChatGPT and Cursor.

Something wrong or out of date? Write to hello@echo-aeo.com and we'll fix it.