Manage content through an agent

LPData exposes its management operations as an MCP server hosted alongside the API, at https://api.lpdata.io/mcp. An agent connected to it creates landing pages, writes the Content Document, uploads files and checks the public read without you assembling HTTP calls by hand. There is nothing to install: you add a URL and your credential to your MCP client. This page is for the developer building the landing page. The tools are the same operations described in Landing Pages and Assets, one tool per operation.

Add the server to your MCP client

The server identifies you by the same account you sign in with, sent in two headers: X-LPData-Email and X-LPData-Password. Store the credential literally, in a configuration file kept outside your repository. In Claude Code:

claude mcp add --transport http lpdata https://api.lpdata.io/mcp \
  -H "X-LPData-Email: <your-email>" -H "X-LPData-Password: <your-password>"

claude mcp get lpdata   # should answer ✔ Connected

That writes to local scope, in ~/.claude.json. In any other client, the equivalent is the same URL with the same two headers:

{
  "mcpServers": {
    "lpdata": {
      "type": "http",
      "url": "https://api.lpdata.io/mcp",
      "headers": {
        "X-LPData-Email": "<your-email>",
        "X-LPData-Password": "<your-password>"
      }
    }
  }
}

That file now holds your password. Keep it outside your repository and do not commit it.

Why not `${LPDATA_EMAIL}` in the configuration

Referencing environment variables from the configuration looks safer, and it does work — as long as the MCP client inherits your shell environment. A client launched from its application icon or from an editor extension does not read your ~/.zshrc: the variable arrives empty and the connection fails. The symptom is treacherous because it depends on how you opened the program: it works when you start from a terminal and fails when you start from the icon, which reads as intermittence with no cause. That is why the literal credential, kept outside the repository, is the recommended route. The credential says who is calling: each person registers their own and sees only their own Landing Pages and Assets. There is no login, logout or refresh tool, and no token is ever handed to the agent. Ask the agent to call check_connection. It answers with the account id and email, which confirms the headers reached the server.

Prepare the shell before uploading files

Uploading Assets does not go through MCP: get_asset_upload_command returns a command the agent runs in its own shell, and that command reads the credential from the environment. It is a channel separate from the configuration above — registering the server with a literal credential fixes the connection, but not the upload. Set the variables in the shell where the agent runs commands:

export LPDATA_EMAIL="owner@example.com"
export LPDATA_PASSWORD="<your-password>"
export LPDATA_URL="https://api.lpdata.io"

LPDATA_URL is optional and falls back to https://api.lpdata.io when unset. Confirm the other two arrived by asking the agent to run:

printenv LPDATA_EMAIL LPDATA_PASSWORD

With the variables empty, the command’s sign_in returns 401, jq turns the response into null, and the second curl goes out with Authorization: Bearer null and takes another 401. None of those messages points at the environment, so check printenv before suspecting the password or the account.

Tools

Tool	What it does
`check_connection`	Returns the authenticated account. Carries the Content Document contract in its description
`create_landing_page`	Creates a Landing Page with `name`, `current_data` and `allowed_hosts`
`list_landing_pages`	Lists the account Landing Pages, without `current_data`
`get_landing_page`	Returns one of your Landing Pages, `current_data` included
`update_landing_page`	Updates `name`, `current_data` or `allowed_hosts`; whatever you omit is left alone
`delete_landing_page`	Removes a Landing Page
`get_public_content`	Reads the Content Document by `public_id`, raw, as the Consuming Application receives it
`list_assets`	Lists the account Assets with their `public_url`
`get_asset_upload_command`	Builds the shell command that uploads a file
`delete_asset`	Removes an Asset

Use id with the management tools and public_id with get_public_content; the two identifiers are not interchangeable.

The Content Document contract

The agent receives this contract in the check_connection description, so it does not need this page to write a valid document. It is here for you to check what the agent produced.

current_data is a non-null JSON value; objects and arrays nest freely and may be empty.
A primitive value may never sit loose inside an object or an array. Every leaf is an Editable Field.
An Editable Field is an object carrying both value and type. Carrying only one of them is invalid.
string, text, url, hosted_file and external_file take a string; number takes a number; boolean takes true or false.
hosted_file and external_file hold the URL itself in value.
Keys beyond value and type are accepted; this is how dashboard_config travels.

{
  "hero": {
    "title": { "value": "Welcome", "type": "string" },
    "cta_url": { "value": "https://example.com", "type": "url" }
  },
  "features": [
    { "name": { "value": "Fast", "type": "string" } }
  ]
}

Sending { "features": ["Fast"] } is refused, because "Fast" is a bare string inside an array:

Current data contains a value outside an editable field at $.features[0]

The MCP server neither validates nor fixes the document: the API is what refuses it, and the agent receives the whole message, field path included.

Upload a file

The server is remote and cannot read your disk, so it does not transfer bytes. get_asset_upload_command returns the command for the agent to run in its own shell:

FILE='/path/to/hero.webp'

TOKEN=$(curl -s -X POST "${LPDATA_URL:-https://api.lpdata.io}/auth/sign_in" \
  -H 'Content-Type: application/json' \
  -d "{\"user\":{\"email\":\"$LPDATA_EMAIL\",\"password\":\"$LPDATA_PASSWORD\"}}" | jq -r .access_token)

curl -s -X POST "${LPDATA_URL:-https://api.lpdata.io}/assets" \
  -H "Authorization: Bearer $TOKEN" -F "asset[file]=@$FILE"

The shell is what expands $LPDATA_EMAIL, $LPDATA_PASSWORD and $TOKEN: the agent writes the command but never sees your password or the token. The command needs jq installed and must be run as it is. If it answers 401, go back to preparing the shell: it is almost always an empty environment variable, not a wrong password. The second curl prints the Asset public_url. Use that URL as the value of a hosted_file Editable Field.

A complete flow

check_connection confirms the account.
create_landing_page creates the page with its initial Content Document and returns the id and the public_id.
get_asset_upload_command builds the command; the agent runs it and gets the image public_url.
update_landing_page writes the document with that public_url in a hosted_file field.
get_public_content reads by public_id and shows exactly what the Consuming Application will receive.

Remember that current_data is always replaced whole: to change one field, the agent sends the complete document with that field changed. LPData keeps no history of the document.

Errors

The server passes the API errors through without reformulating them.

Situation	What the agent receives
Missing or invalid credential	`401 Unauthorized` telling it to check `X-LPData-Email` and `X-LPData-Password`
Document outside the contract	The list of validation messages, each with the field path
Unknown `id` or `public_id`, or a resource owned by another account	`Landing page not found` or `Asset not found`
Public read limit exceeded	`Too many requests`, with the wait time; see Rate limits

Get started

Consume content

Manage content

Agents

Reference

MCP server

Manage content through an agent

Add the server to your MCP client

Why not `${LPDATA_EMAIL}` in the configuration

Prepare the shell before uploading files

Tools

The Content Document contract

Upload a file

A complete flow

Errors

​Manage content through an agent

​Add the server to your MCP client

​Why not ${LPDATA_EMAIL} in the configuration

​Prepare the shell before uploading files

​Tools

​The Content Document contract

​Upload a file

​A complete flow

​Errors

Manage content through an agent

Add the server to your MCP client

Why not `${LPDATA_EMAIL}` in the configuration

Prepare the shell before uploading files

Tools

The Content Document contract

Upload a file

A complete flow

Errors