Connect an AI IDE or agent

livemy.app runs a remote MCP (Model Context Protocol) server, so you can connect your AI editor or coding agent — Cursor, Claude Code, Windsurf, Claude Desktop, ChatGPT, or any other MCP client — to your livemy.app account and work with it from inside the tool. MCP is an open standard that lets AI tools talk to external services; once connected, your agent acts on your account with the same permissions you have in the dashboard.

Where to find it

Open the account menu and choose Developer console, or go to Settings → Developer console. Both open the MCP Integration page, where you manage access and copy ready-made setup snippets.

Connecting an MCP client requires a paid plan. Any signed-in account can open the page, but if your plan doesn’t include MCP you’ll see an upgrade prompt in place of the connection tools — see the Billing page in your dashboard for what your plan includes.

There are two ways to connect:

A personal access token — create a token and paste a config snippet into your client. This is how you connect code editors like Cursor, Claude Code, and Windsurf, and it works for any MCP client.
Signing in — add livemy.app as a connector in Claude or ChatGPT and authorize by signing in, with no token to manage.

Get your Server URL

Both methods use one address — your Server URL. The MCP Integration page shows it with a Copy button. On production it is:

https://my.livemy.app/api/mcp/messages

Copy the value shown on your page rather than typing it — it’s the same address for every method and every client.

Connect with a personal access token

Best for code editors and any other MCP client. You create a token, then paste a ready-made config snippet into your client.

Create a token

On the MCP Integration page, under Active tokens, select New token (or Create your first token if you don’t have any yet).
Give it a name you’ll recognize later, for example “Cursor on my laptop”.
Choose when it expires — 30 days, 90 days (recommended), 1 year, or never. A shorter lifetime is safer, and you can always create a new one.
Select Generate token.

Your token is shown once, in a highlighted card. Copy it immediately and store it somewhere safe — livemy.app never shows it again. If you lose it, revoke it and create a new one.

Add it to your client

After you create a token, the Connect a client section pre-fills its snippets with your new token. Pick your client’s tab, copy the snippet, and paste it into the client’s config file. If you come back later, the snippets show a <YOUR_TOKEN> placeholder instead — replace it with your token.

Config file: .mcp.json in your project root (recommended), or ~/.claude.json to make it available in every project.

{
  "mcpServers": {
    "livemy": {
      "type": "http",
      "url": "https://my.livemy.app/api/mcp/messages",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Add the livemy entry, keeping any other servers you already have. Run claude from that folder and check the connection with the /mcp command.

Config file: ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

{
  "mcpServers": {
    "livemy": {
      "type": "http",
      "url": "https://my.livemy.app/api/mcp/messages",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Open Settings → MCP and add a new server, or edit the file directly. Restart Cursor, then confirm livemy appears under your MCP servers.

Config file: ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "livemy": {
      "type": "http",
      "url": "https://my.livemy.app/api/mcp/messages",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Open or create the file, paste the entry, then reload Windsurf. Open the Cascade panel and confirm the livemy tools are available.

Claude Desktop can’t reach a remote MCP server directly, so its setup runs through the mcp-remote bridge instead of the plain url form used by the other clients.

Config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

{
  "mcpServers": {
    "livemy": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://my.livemy.app/api/mcp/messages", "--header", "Authorization:${LIVEMY_AUTH}"],
      "env": {
        "LIVEMY_AUTH": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

A few things to get right:

Copy Authorization:${LIVEMY_AUTH} exactly — no space after the colon. The token goes only in env.LIVEMY_AUTH, never inline in the argument.
Install the bridge first so startup is fast: npm i -g mcp-remote (this needs Node.js). A first-run download can otherwise stall Claude Desktop while it opens.
Quit and fully reopen Claude Desktop, then check livemy in its MCP servers list.

Prefer not to manage a token? Claude Desktop can also connect by signing in instead.

Any client that speaks MCP over HTTP works. Point it at your Server URL and send Authorization: Bearer <YOUR_TOKEN> with every request. You can verify your token and endpoint from a terminal:

curl -X POST 'https://my.livemy.app/api/mcp/messages' \
  -H 'Authorization: Bearer <YOUR_TOKEN>' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}},"id":1}'

A successful response means your token and endpoint are working.

Let your AI agent set it up

If you use an agentic editor like Claude Code, Cursor, or Windsurf, you can skip the manual steps. After you create a token, copy the agent prompt from the page and paste it into your editor’s chat. The agent detects which client you’re using, writes the config file for you, and tells you the next step. It writes the token straight into the config and won’t repeat it back in the chat.

Connect by signing in

Claude and ChatGPT can connect without a token. You add livemy.app as a custom connector and authorize by signing in.

In Claude (claude.ai or Claude Desktop) or ChatGPT, open Settings → Connectors and add a custom connector.
Paste your Server URL as the connector’s address.
Select Connect. livemy.app opens a sign-in page.
Sign in with your livemy.app account — or Continue as your signed-in account — to authorize access. Signing in is the approval; there’s no separate consent step.

Once connected, the app shows up under Active connections on the MCP Integration page, where you can disconnect it at any time.

Manage tokens and connections

The MCP Integration page keeps two separate lists.

Active tokens — your personal access tokens. Each shows its name, a short prefix (never the full token), when it expires, and when it was last used. To remove one, select the delete icon and confirm. Revoking is permanent and immediately cuts off any client using that token. You can hold a limited number of active tokens at once; the page shows your current count.
Active connections — apps you connected by signing in. Each shows the app and when it connected. Select Disconnect to revoke its access immediately; the app has to reconnect to regain it. This list appears once you have at least one such connection.

What your agent can do

Once connected, your AI tool works through the same permissions you have in the dashboard. It can browse your projects, read their deploy reports and AI Assist history, and — depending on your plan — make changes such as deploying and redeploying projects, managing custom domains, chatting with AI Assist, and running commands or editing files on a project’s container. Which actions are available follows your plan; see the Billing page in your dashboard for what’s included.

Troubleshooting

Lost your token? You can’t view it again. Revoke it and create a new one.
Client can’t authenticate? Check that the token was copied in full and hasn’t expired, and that you’re using the Server URL shown on your page.
“livemy” doesn’t show up in your client? Restart or reload the client after editing its config — many clients only read MCP settings at startup.
Claude Desktop won’t start or hangs? Pre-install the bridge (npm i -g mcp-remote) and make sure Node.js is on your PATH. Use the bridge snippet — the plain url form doesn’t work in Claude Desktop.

SSH access — open a shell on your project (Pro plan).
Using AI Assist — make changes by chatting with the agent in the dashboard.