Connect Claude Code, Cursor or Codex to ProductEcho over MCP

ProductEcho is an MCP server at https://api.productecho.com/mcp. Add that address to your coding agent once, then sign in to ProductEcho in your browser. From then on the agent can deploy apps, create databases and read logs in your workspace.

The browser page asks you to approve Full-stack read and write access: your apps, your databases and their passwords, and your logs. If you are not logged in to ProductEcho, it asks you to log in first. The agent then acts as you, with your role in the workspace.

Access renews by itself while you use it. If the agent goes 30 days without using ProductEcho, sign in again.

Install the ProductEcho plugin. It adds the MCP server plus the deploy and PostgreSQL skills, which tell Claude Code how to use it. Run these in your terminal:

claude plugin marketplace add productecho/skills
claude plugin install productecho-plugin@productecho

In a Claude Code session that is already open, run /reload-plugins. Then run /mcp and follow the steps in your browser.

To add only the MCP server, without the skills, run this and then /mcp to sign in:

claude mcp add --transport http productecho https://api.productecho.com/mcp

Your first deploy, step by step: Deploy from Claude Code.

Codex keeps its MCP servers in ~/.codex/config.toml. The first command writes the entry, and the second opens the browser to sign you in:

codex mcp add productecho --url https://api.productecho.com/mcp
codex mcp login productecho

To add the ProductEcho skills as well:

npx -y skills add productecho/skills --skill '*' --yes --global --agent codex

Your first deploy, step by step: Deploy from Codex.

On a computer with Cursor installed, select Add ProductEcho to Cursor. To add the server by hand instead, put it in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project:

{
  "mcpServers": {
    "productecho": {
      "url": "https://api.productecho.com/mcp"
    }
  }
}

If ProductEcho does not appear in Cursor's MCP settings, restart Cursor. Cursor then opens a browser window where you sign in.

To add the ProductEcho skills as well:

npx -y skills add productecho/skills --skill '*' --yes --global --agent cursor

Your first deploy, step by step: Deploy from Cursor.

A client that supports remote MCP servers over HTTP takes the address directly:

{
  "mcpServers": {
    "productecho": {
      "type": "http",
      "url": "https://api.productecho.com/mcp"
    }
  }
}

A client that only starts local (stdio) servers can reach ProductEcho through the mcp-remote bridge. You still sign in through the browser:

{
  "mcpServers": {
    "productecho": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.productecho.com/mcp"
      ]
    }
  }
}

A CI job or a script cannot open a browser, so it uses an MCP API key instead. A key has full access to the workspace, so keep keys for automation. How to create, use and revoke one: API keys for CI and scripts.

• Your agent lists productecho as a connected MCP server: /mcp in Claude Code, codex mcp list in Codex, the MCP settings in Cursor.
• Ask it to list your ProductEcho apps. It calls list_applications and answers, even when you have no apps yet.

The server says it needs authentication

The server is added but not signed in. Run the sign-in step again: /mcp in Claude Code, codex mcp login productecho in Codex, or restart Cursor.

The browser page says Permission unavailable

Your role in the workspace is Viewer, and a coding agent asks for read and write access. Ask an owner or admin to make you a Developer or Admin, then sign in again.

It worked, then stopped with a 401 error

The sign-in lapses after 30 days without use, or when your account leaves the workspace. Run the sign-in step again.

A config file is not picked up

Check that the file is valid JSON. A trailing comma is the most common break. Then restart the client fully.