Integration

Stripo integration

Stripo is an email template builder. With its email generation API an agent can list, read and delete emails and templates, get their raw HTML and CSS, export them as HTML (or AMP HTML) files, create emails and templates from MJML markup, generate an email from a template's generation area filled with external data (raw JSON or a URL) through saved modules, manage SRT transformer rules, create translation versions and apply translation JSON files, list folders and saved modules, export an email to a connected eSputnik account, and read the organization's export, email and timer limits. Compiling MJML to HTML without saving (it answers raw HTML) and downloading translation JSON files (their answer shape is undocumented) are not exposed. Authentication is a Stripo API JWT token sent in the Stripo-Api-Auth header; validate_token checks it.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Stripo

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.

Email, 5 operations

  • delete_emailDelete emailDELETEDeletes one email from the project. This cannot be undone.
  • export_email_to_html_fileExport email to html fileGETExports one email as a file for sending elsewhere: an HTML file, or a zip archive when includeTranslationVersions is true. Returns the stored file.
  • generate_emailGenerate emailPOSTGenerates an email from a template whose generation area is filled with data (raw JSON or a URL) laid out by saved modules, optionally through SRT transformers. Returns the new email's ID and URLs.
  • get_emailGet emailGETReturns one email by its ID with its details, HTML and CSS code, translated versions and UTM values.
  • list_emailsList emailsGETLists the emails of the project, a page at a time (10 by default), with search, folder filter and sorting. Each item has emailId, name, folderId, editor and preview URLs, title, preheader and dates.

Template, 4 operations

  • delete_templateDelete templateDELETEDeletes one template from the project. This cannot be undone.
  • export_template_to_html_fileExport template to html fileGETExports one template as a file: an HTML file, or a zip archive when includeTranslationVersions is true. Returns the stored file.
  • get_templateGet templateGETReturns one template by its ID with its details, HTML and CSS code and translated versions.
  • list_templatesList templatesGETLists the templates of the project, a page at a time (10 by default), with search, folder filter and sorting. Each item has templateId, name, folderId, editor and preview URLs and dates.

Srt, 3 operations

  • delete_srt_configDelete srt configDELETEDeletes one saved SRT transformer rule by name. This cannot be undone.
  • get_srt_configGet srt configGETReturns one saved SRT transformer rule (its name and its start, repeatable and tail sections) by name.
  • save_srt_configSave srt configPOSTSaves a new named SRT transformer rule (which modules lay out the data at the start, in the repeating part and at the tail) for reuse by generate_email.

Apply, 2 operations

  • apply_email_translation_jsonApply email translation jsonPOSTUploads a JSON file of translations and applies it to an existing email for the given target languages. Answers with no content on success.
  • apply_template_translation_jsonApply template translation jsonPOSTUploads a JSON file of translations and applies it to an existing template for the given target languages. Answers with no content on success.

Mjml, 2 operations

  • import_email_from_mjmlImport email from mjmlPOSTCreates an email in the project from MJML markup, compiled to Stripo-editable HTML. Refused when the plan's email limit is reached. Returns emailId and editor and preview URLs.
  • import_template_from_mjmlImport template from mjmlPOSTCreates a template in the project from MJML markup, compiled to Stripo-editable HTML. Refused when the plan's template limit is reached. Returns templateId and editor and preview URLs.

Translation version, 2 operations

  • create_email_translation_versionsCreate email translation versionsPOSTCreates translation versions of an existing email for the given languages. Returns one item per version with its locale and id.
  • create_template_translation_versionsCreate template translation versionsPOSTCreates translation versions of an existing template for the given languages. Returns one item per version with its locale and id.

Esputnik, 1 operation

  • export_email_to_esputnikExport email to esputnikPOSTExports one email of the project to an eSputnik account as a template (named after the subject). The eSputnik account must already be connected to the Stripo project. Returns the exported emailId.

Folder, 1 operation

  • list_foldersList foldersGETLists the folders of the project, either email folders or template folders, with id, name and type. Use a folder id as folderId elsewhere.

Module, 1 operation

  • list_modulesList modulesGETLists the modules saved in the project's library (or the public pre-built ones), a page at a time, with name, tag, category and block type filters. Each item has its id, name, markup and css.

Organization limit, 1 operation

  • get_organization_limitsGet organization limitsGETReturns the organization's quotas: exports, emails and templates, and timers, each with the count used, the limit, the renewal time and the extra (purchased) count and limit.

Raw email, 1 operation

  • get_raw_emailGet raw emailGETReturns only the HTML and CSS code (and tags) of one email.

Raw template, 1 operation

  • get_raw_templateGet raw templateGETReturns only the HTML and CSS code (and tags) of one template.

Srtname, 1 operation

  • list_srt_config_namesList srt config namesGETLists the names of the SRT transformer rules saved in the project; pass a name to get_srt_config or to a generate_email transformer.

Validate, 1 operation

  • validate_tokenValidate tokenGETChecks the API token: valid is true when it can be used, with the API service version and protocol version. Answers HTTP 401 for an invalid token.

Use Stripo from Claude Code, Cursor or Codex

Connect Stripo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Stripo 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 Stripo

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Stripo once

    Add your Stripo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Stripo integration FAQ

What can you do with the Stripo integration?

LiveContext exposes 26 operations on Stripo, covering email, template, srt and apply.

Popular integrations

Browse the whole catalog