Integration

Ometria integration

Ometria is a customer data and marketing platform for retailers. Read profiles, contacts, orders, products, saved segments (lists) and their entry and exit changes, custom events and unsubscribes; push contact, order, product and custom event records (up to 100 per call); send transactional emails; manage contact and order custom fields; merge duplicate profiles; file GDPR anonymisation and email or phone erasure requests; and handle email translation requests. Left out on purpose: the line-delimited list export and the HTML translation preview (formats the engine cannot read). Responses withhold dates of birth, postcodes and cities, direct-mail postal addresses, order IP addresses and shipping and billing addresses, every merchant-defined custom properties object, and the raw record of a push error. Rate limits per account: Data API 4 requests per second, push 8 per second, transactional email 30 per second, GDPR anonymisation 6 per minute, profile merge 1 per minute (HTTP 429 beyond). Authentication: an Ometria API key sent in the X-Ometria-Auth header.

Connect Ometria How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ometria.Built from the 37 Ometria tools below, on the connection you add once.

What you can do with Ometria

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 4 operations

get_contactGet contactGETReturns one contact of a collection: email, phone, names, gender, country, opt-in status per channel, store ids and identifiers. Date of birth, postcode, city, the direct-mail postal address and custom properties are withheld.
list_collection_contactsList collection contactsGETLists the contacts of one collection, 10 per call by default (max 250); filter by last update date. Page with offset. Date of birth, postcode, city, the direct-mail postal address and custom properties are withheld.
list_contact_collectionsList contact collectionsGETLists the contact collections (record sources) with the number of contacts in each. Use a collection name with list_collection_contacts.
list_list_profilesList list profilesGETLists the profiles in a saved segment, 10 per call by default (max 250). Page with offset. Dates of birth and custom properties are withheld.

Custom field, 4 operations

create_custom_fieldCreate custom fieldPOSTCreates a custom field for contacts or orders. The date type can only be used with the contact category. Returns the field.
delete_custom_fieldDelete custom fieldDELETEDeletes a custom field.
list_custom_fieldsList custom fieldsGETLists the account's custom fields for contacts and orders (id, category, type, title, status), 50 per page by default (max 200); filter by category, type, status or a search on label or id.
update_custom_fieldUpdate custom fieldPUTRenames a custom field or changes its status (active or archived). id and category identify the field; leave title or status out to keep it. Returns the field.

Custom event, 3 operations

get_custom_eventGet custom eventGETReturns one custom event: id, type, time, profile id and identity email, phone or account id. Its custom properties are withheld.
list_custom_eventsList custom eventsGETLists custom events (id, type, time, profile and identity email, phone or account id), 10 per call by default (max 250). Page with offset. Event custom properties are withheld.
list_custom_events_by_typeList custom events by typeGETLists custom events of one type, 10 per call by default (max 250). The type must be defined in Ometria. Page with offset. Event custom properties are withheld.

Data deletion request, 3 operations

create_data_deletion_requestCreate data deletion requestPOSTFiles a GDPR request that permanently ANONYMISES one person's data in Ometria. Give exactly one identifier. Rate limit 6 per minute. Returns the request id; check it with get_data_deletion_request.
get_data_deletion_requestGet data deletion requestGETReturns one GDPR anonymisation request: status, action, summary, creation and completion times and the hashed identities processed.
list_data_deletion_requestsList data deletion requestsGETLists GDPR anonymisation requests filed for the account, with status, action, summary and the hashed identities processed.

Field forget, 3 operations

create_field_forget_requestCreate field forget requestPOSTErases a profile's email and/or phone in Ometria (the rest of the profile stays). Runs asynchronously: poll get_field_forget_request with the returned id until status is completed, aborted_sole_identifier, not_found or failed.
get_field_forget_requestGet field forget requestGETReturns one field forget request: status (pending, in_progress, or terminal completed, aborted_sole_identifier, not_found, failed), fields and times.
list_field_forget_requestsList field forget requestsGETLists field forget (email or phone erasure) requests, newest first, including those made in the Ometria app, 100 per page by default (max 500). Page with offset while below total_count.

Merge profile, 3 operations

get_merge_jobGet merge jobGETReturns the status of one profile merge job: in_progress, completed or failed.
list_merge_jobsList merge jobsGETLists profile merge jobs and their status (in_progress, completed, failed).
merge_profilesMerge profilesPOSTPermanently merges up to 5 profiles into a survivor profile. Rate limit 1 per minute. Returns a job id: poll get_merge_job until status is completed or failed.

List, 2 operations

get_listGet listGETReturns one saved segment (list): title, description, status, type, size, revenue and order totals and refresh times.
list_listsList listsGETLists saved segments (lists) with size, revenue and order totals; active ones by default.

Order, 2 operations

get_orderGet orderGETReturns one order: totals, currency, status, customer, line items with local and base totals, channel, store, payment and shipping method, coupon. IP and addresses withheld.
list_ordersList ordersGETLists orders, 10 per call by default (max 250); filter by customer id, email, or created, updated or placed date ranges. Page with offset. IP addresses, addresses and custom properties are withheld.

Product, 2 operations

get_productGet productGETReturns one product: title, SKU, price and special price, stock and active flags, URLs, attributes and per-store listings.
list_productsList productsGETLists products (title, SKU, prices, stock, active flag, URLs, attributes, store listings), 10 per call by default (max 250); filter active or inactive and include variants. Page with offset.

Profile, 2 operations

get_profileGet profileGETReturns one customer profile: names, email, phone, country, lifecycle status, opt-in, tags, order stats, key dates, segment memberships and identifiers. Date of birth and custom properties withheld.
list_profilesList profilesGETLists customer profiles, 10 per call by default (max 250); look one up by email, customer ID, phone or profile hash, or filter by created / updated dates. Page with offset. Date of birth withheld.

Request, 2 operations

get_translation_requestGet translation requestGETReturns one translation request: languages, status, tags to translate and the source and target translation maps.
list_translation_requestsList translation requestsGETLists email translation requests (id, source and target language, status pending, cancelled or completed); filter by id, status or created / updated time. Max 50 per call.

Bulk, 1 operation

create_field_forget_requests_bulkCreate field forget requests bulkPOSTFiles up to 100 email / phone erasure requests at once. Always answers 202: read each item's result (accepted, duplicate, rejected), then poll get_field_forget_request with its id.

Change, 1 operation

list_list_changesList list changesGETReturns the `list_enter` and `list_exit` events of a saved segment since a date: profile id, email, customer id, time and event.

Error, 1 operation

list_push_errorsList push errorsGETLists the 100 latest push record errors: request id, record type and id, time and the error message and path. Filter by the request_id returned by push_records.

Push, 1 operation

push_recordsPush recordsPOSTUpserts up to 100 records (contacts, orders, products or custom events) into Ometria; one record type per call. Processed asynchronously: check list_push_errors with the returned request_id.

Send, 1 operation

send_transactional_emailSend transactional emailPOSTSENDS a transactional email to one recipient, from an Ometria template (template_id) or your own content. With sandbox true it is processed but not sent. Rate limit 30 per second.

Submit, 1 operation

submit_translationSubmit translationPOSTSubmits translations for a pending translation request. Returns a confirmation message.

Unsubscribe, 1 operation

list_unsubscribesList unsubscribesGETLists unsubscribe events in a time range: email (preferences centre, app, list or link unsubscribe) and SMS stop words. Unsubscribes made through the API are not included.

Use Ometria from Claude Code, Cursor or Codex

Connect Ometria in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ometria operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ometria

Create your workspace
Sign up free. Nothing to install.
Connect Ometria once
Add your Ometria connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.